Start here
Connecting tools
Which coding tools Agentower works with today, and what each one supports.
Each developer connects their own machine once. A small hook is added to each tool; it tells Agentower when an agent starts, works, needs someone, finishes or fails. By default it sends status, usage and counts of what each agent did — never code or file contents, and never your prompts unless a project's Work details is switched on (see Privacy).
#What each tool supports
| Claude Code | Codex | Cursor | |
|---|---|---|---|
| Status on the board (starting, working, idle, failed, done) | Yes | Yes | Yes |
| Shows Needs you (waiting for a person) | Yes | Yes | No — Cursor doesn't tell hooks when it's waiting |
| Allow or deny from Agentower | Yes | Yes | No |
| Reply to it or message it from Agentower | Yes | No, not yet | No |
| Pauses at a guardrail | Yes | Yes | Yes, but only time limits can be reached (no token data) |
| Tokens and ≈ cost | Yes (telemetry) | Tokens only (telemetry) | No |
| Which model it uses | Yes | Yes, when Codex reports it | Yes, when Cursor reports it |
| Subagents shown inside their agent | Yes | Yes | No |
Answering from Agentower is off until an owner switches on Agent chats for the workspace and whoever runs the agent allows it on their computer (AGENTOWER_REMOTE, off unless they change it) — see Answer agents from Agentower.
#Pick your tool
- Connect Claude Code — the most complete connection. Start here.
- Connect Codex — the Codex CLI, the ChatGPT desktop app and the IDE extensions.
- Connect Cursor — Cursor's agent: status only.
- Other tools and scripts — anything else, through the REST API or the MCP server.
#One key per machine
All three tools use the same ingest key and the same settings file on a machine (~/.agentower/claude-code.env). Create one key per computer on Keys & connections; the agents it reports are shown as yours. On Windows, install Git for Windows and paste the commands into Git Bash — the tools run hooks with it.