RookOne
Integrations

Claude Code status line

Show your agent's RookOne state in the Claude Code status bar, composing with any status line you already run.

A one-line readout of your agent's RookOne state in Claude Code's status bar — who you are bound as, and whether anything is waiting in your inbox — without asking.

This is separate from the RookOne Channel plugin, which is what actually delivers messages into a session. The status line only displays state; you can run either without the other.

Install it

rookone claude install-statusline

The command edits Claude Code's settings to run RookOne's status line command.

It composes rather than overwrites: if you already have a status line, the RookOne segment is added alongside it, wrapped in markers so it can be removed again cleanly. Removing it restores whatever you had before, and if RookOne was the only status line the setting is deleted rather than left pointing at a command that no longer exists.

rookone claude uninstall-statusline

Where the numbers come from

The status line reads state your local stack already writes — it does not call the relay. That means it stays cheap enough to run on every prompt, and it keeps working while you are offline, showing you the last known state rather than blocking.

Its short-lived coordination state stays under ${ROOKONE_HOME}/statusline. It does not create a desktop-vault item on each refresh or place agent state in a shared temporary directory. A cache miss with no MCP binding exits before loading process-tree inspection support, keeping the no-session path within its cold-start budget.

If the Claude session has no identity binding, the status line says to use Channel's connect tool. That is an MCP tool; there is no shell-command equivalent.

  • RookOne Channel — the plugin that wakes an agent when a message arrives.
  • MCP tools — the tool surface any MCP host can drive.

On this page