Agents
CLI Agents
Run any CLI coding agent in Alera, with live status for the ones that ship integrations.
On This Page
Alera does not invent an agent protocol. If a tool runs in a terminal, it runs in Alera.
First-Class Today#
These agents ship with icons, launch adapters, and status integrations in the workbench:
- Claude Code
- Codex
- Amp
- Antigravity
- OpenCode (v1 and OpenCode 2)
- Cursor
- GitHub Copilot
- Pi
- Grok Build
- fx
Their integrations report whether each agent is working, waiting for you, blocked, or done, so the sidebar, the tab strip, and the paired phone can tell you who needs attention. That glanceable state is the point of running several agents at once.
Turning On Status Hooks#
Live status comes from hooks Alera installs into each agent’s own user configuration (for example ~/.claude/settings.json or ~/.codex/hooks.json). Every switch is off by default. Turn on the agents you use under Settings → Agents → Status Hooks, or with alera runtime agents from the CLI.
Enabling a switch writes Alera-scoped entries only; disabling it removes exactly those entries and leaves the rest of your configuration alone. fx is the exception: it reports through its built-in Herdr integration, on macOS and Linux, and needs no hook file.
Everything Else#
Any other CLI gets the full workbench as a normal terminal process: worktree isolation, persistent sessions, resource tracking. Launch it in a workspace tab the way you would in any shell.
Gemini CLI, Goose, Aider, Kimi, Crush, Continue, or an in-house script nobody else has heard of: if your terminal can run it, so can Alera. Status tracking rolls out per agent; the PTY does not wait on that list.
How To Launch#
- Open a workspace.
- Add a terminal tab, or pick an agent profile from the Add Tab menu; a profile appears there once its Show In New Tab Menu switch is on.
- Run the agent CLI, or let the profile start it with an optional starting prompt.
New Workspace can also do all of it at once: choose From Prompt, pick an agent profile, and Alera creates the workspace, names it, and starts the agent with your prompt.
Profiles are yours: each one records how to launch an agent, and you approve the launch command. Manage them under Settings → Agent Profiles or with alera agent-profile.
Resuming A Conversation#
When a supported agent reports its native conversation id, Alera remembers it on that tab. If the terminal restarts later, the agent resumes the same conversation instead of starting over, and the original prompt is not sent again.
Orchestration Adapters#
If you coordinate agents through orchestration, profiles bind to a built-in adapter registry (codex, claude, copilot, cursor, agy, opencode, pi, amp, grok, fx, and related defaults). The adapter decides how the host detects readiness and delivers the starting prompt. It is not a second product; it is how a coordinator launches the same CLIs you already use.