Create a new Cerebro session and project workspace

Resume an existing session using a handover token

Pause an active session for later resumption

Complete and archive a session

List all active, paused, and recent sessions

Send a task to the appropriate worker or agent for execution

The easiest way to use Cerebro — just describe what you want built or fixed. Auto-creates a session, picks the right CLI provider, and executes. Use this when the user says things like 'build me a website' or 'fix this bug' or 'review this code' without specifying sessions or agents. If no projectPath is given, ask the user where to save files.

Read the project folder structure and file contents. Use this to understand a codebase before making changes. Returns directory tree and optionally file contents for specified files or all files.

Get current project progress and task status

Get a human-friendly explanation of code changes

Trigger a project build and return results

Run the test suite and return results

Define a new specialist agent via natural language description

Show all agents in the current session with their status

Modify an existing agent's definition, skills, or preferences

Delete an agent from the swarm

Get detailed status and history for a specific agent

Install pre-built agent templates from the marketplace

Explicitly route a task to a specific agent, overriding auto-routing

Interpret an image and suggest actions. How it works: the user uploads an image to Chat, Chat (Claude) sees and describes it, then calls this tool with the description. No API key needed — Chat IS the vision layer.

Build or fix code based on an image. Chat sees the image, describes it, and this tool sends the description to a CLI worker to implement. Works for: screenshots of bugs to fix, mockups to build, error messages to resolve.

Visual diff between expected and actual. Chat compares two images and describes the differences, then this tool structures the findings and can trigger fixes.

Generate a signed handover token for session continuity across chats

Check if a handover token is valid

Report current context window usage and handover readiness

Configure which CLI tools handle which tasks. Say 'Use Claude for coding and Codex for testing' or 'Set Aider as default'

Detect which CLI coding tools are installed and available on this system

Set model, effort level, and terminal mode. Say 'Use Opus for coding' or 'Set high effort' or 'Run in background mode'

Open a persistent terminal showing real-time token usage. Tracks every Cerebro tool call with estimated tokens and handover recommendation.

Stop the Context Watcher and close terminal. Tracking data preserved.