Skip to content
Cogno v0.4.0

Coding Agents

When you run AI coding agents in several terminals, Cogno shows the state of each one — in the terminal’s tab and in a side panel. You see immediately which agent is still working, which one is waiting for your answer, and which one has finished.

Open the panel with Ctrl+Alt+R (Command+Control+R on macOS) or the open_coding_agents action.

AgentCogno’s hook is written to
Claude Code~/.claude/settings.json
Codex~/.codex/hooks.json (and features.hooks = true in ~/.codex/config.toml)
Gemini CLI~/.gemini/settings.json
Kimi CLI~/.kimi/config.toml
Antigravity~/.gemini/config/hooks.json

Cogno learns an agent’s state through a hook: a small command in the agent’s own configuration that tells Cogno when the state changes.

On startup Cogno looks for supported agents. For each one it finds without a hook, it offers once to install it. Accept, and you are done — start the agent in a Cogno terminal and it appears in the panel.

If you declined, or want to change it later, use the list of detected agents (see below).

The hook only reports when the agent runs inside a Cogno terminal. Anywhere else it does nothing and never makes the agent fail. It talks to Cogno’s local HTTP server, which only listens on your own machine.

Each terminal running an agent gets a card:

FieldShows
StatusWorking, Ready, Waiting for input or Error
Activitywhat the agent did last — a command, a file, a search pattern
Working directorythe terminal’s current directory
Providerwhich agent it is

Click a card to jump to its terminal. The card of the focused terminal is highlighted. A card disappears when the agent exits or the terminal closes.

The gear button in the panel header lists every supported agent found on your system and shows whether its hook is installed.

ButtonEffect
PlusInstall the hook
Trash, then the check markRemove the hook (the cross cancels)
Detect AgentsScan your system again

Removing only takes out Cogno’s own entries; your other hooks stay untouched. Cogno does not offer a removed hook again — bring it back with the plus button.

A state change can raise a notification, for example when an agent needs your input while you work in another tab. The bell button in the panel header sets which changes notify you and through which channel.

To set the defaults in your config:

feature.coding_agents.notifications.question.enabled = true
feature.coding_agents.notifications.error.enabled = true