# Agents

Each tool runs headlessly as a long-lived hidden process, started by the first task that needs it and shared by all of that tool's sessions. Nothing runs in a terminal, and prompts go over stdin, never on a command line.

| Agent | Program Hover runs | How |
| --- | --- | --- |
| Codex | `codex-acp` | The `@agentclientprotocol/codex-acp` adapter |
| Cursor | `cursor-agent` | `cursor-agent acp` |
| OpenCode | `opencode` | `opencode serve` on 127.0.0.1 only, with a password made for each start |
| Claude Code | `claude` | Its Agent SDK mode: streamed JSON over stdio, so every permission comes to Hover |
| Kiro | `kiro-cli` | `kiro-cli acp` (Agent Client Protocol) |

Install and sign in with each tool's own CLI. Hover checks both with the tool's status command; a tool that fails is greyed in the office with what to do.

Coming soon: Gemini CLI, GitHub Copilot, Goose, Qwen Code, Cline, Amp and Junie.

## Set up on a Mac

On a Mac each agent's page in Settings has a **Set up** row that installs what is missing with the maker's own installer and opens its sign-in. Hover never sees the credentials.

## Idle time

After 5 or 15 idle minutes (per tool, in Settings) the process stops. Your next reply starts it again and loads the conversation back.

## Kiro

An MCP server that fails to start no longer ends the task. The chat says which one didn't come up and the agent carries on.

Under **Settings → Kiro**, **Continue when high usage encountered** (off by default) makes Hover send "continue" when Kiro stops because too many people are using the model. It keeps doing so until it works or you press Stop.

## Kiro Web

A Kiro task can run in Kiro Web, in Kiro's cloud, instead of on this computer. Use the cloud button in the new-task box, or say it in [voice](https://tryhover.co/docs/voice.md). It is for Kiro only, on Windows and Linux.

- **The repository.** The task clones the folder's own GitHub repository, another repository you have connected, or none. The repository menu has a search box.
- **Access.** Every Kiro Web task has full access, so there is no access pick for it.
- **Replies** reach the same session, also after a restart. The chat's cloud chip opens it in Kiro Web.
- **Pictures** you paste into a Kiro Web task are sent with the prompt.
- **Closing Hover or losing the connection.** Hover no longer tells Kiro to stop the task when it quits, and it saves the task's id as soon as Kiro gives it. The task carries on and picks up again when Hover is back. The project has checked this with its session tests, not yet with a live Kiro Web task.
- **The chat** has a limited [desk card](https://tryhover.co/docs/desk-card.md): Pull request and Diff work, Terminal and Files are off.
- **Sessions started elsewhere** are listed in [history](https://tryhover.co/docs/history.md).

## OpenCode

OpenCode keeps its own providers: API keys, sign-ins, local models. Every call names the session's folder, so that folder's OpenCode config, agents, skills and MCP servers apply. It takes 30–40 s to start cold.

---

Part of the [Hover docs](https://tryhover.co/docs.md) (Configure). HTML version: https://tryhover.co/docs/agents. Index for agents: https://tryhover.co/llms.txt