Agent tabs
An agent tab is a real terminal running a real agent CLI. This is what running agents in parallel actually means in Hoook today.
What an agent tab is
Each agent tab spawns a genuine terminal session (a PTY) and runs an agent CLI inside it, with full interactivity: colours, prompts, and keyboard input all work as they would in your own terminal. Open several tabs and the agents run at the same time, independently.
Hoook launches the CLI in your workspace folder and extends PATH to include the
usual Homebrew locations, so tools installed with brew are found.
Install the CLI first
Hoook does not bundle any agent. It runs what you already have. If the binary is not on your
PATH, the tab opens and immediately fails with a "command not found" error.
Settings has a tool detector that shows what Hoook can see.
Available agents
| Agent | Command it runs |
|---|---|
| Claude Code | claude |
| Codex | codex |
| Gemini | gemini |
| Cursor | cursor-agent |
| Ollama | ollama run llama3.1:latest |
The Ollama tab is pinned to llama3.1:latest and is not configurable from the
picker yet. If you want a different local model, use a chat instead,
which lists every model Ollama reports.
What this is not
Because a tab is just a terminal, Hoook does not read, parse, or coordinate what the agent does inside it. Agents do not share state through Hoook, cannot hand work to each other, and are not sandboxed from one another beyond running in their own process. "In parallel" means they run at the same time, not that they cooperate.
If two agents work in the same folder, they can overwrite each other's changes. Give long-running agents separate projects.