Use Cully in T3 Code

T3 Code is an optional window for running several coding agents without a terminal per agent. Cully works with it, and works the same without it. Use T3 Code if you switch between agents. If you use one agent, you don't need it.

Why it works

T3 Code starts the agent CLIs already installed on your machine. Those CLIs read the same configuration that cully setup writes, so the Cully MCP tools, skill and hooks load in every agent T3 Code starts. Cully does not depend on T3 Code and changes none of its settings.

Set up

1. Install and sign in to each agent you want, as T3 Code asks.

2. Run Cully setup for each agent:

   $ cully setup --agent codex --mcp-url http://127.0.0.1:8080/mcp

3. Restart T3 Code, or start a new session in it, so each agent loads the configuration.

When t3 is on your PATH, cully setup prints a reminder of this page.

What you get

• Memory, tasks and handoffs are shared by every agent that connects to the same Cully server. An agent can pick up what another one logged.
• Each session records its own agent session id, so you can tell which agent did what and resume it.
• In a team workspace, agents in T3 Code claim and hand off tasks like any other client.

Act on advisor suggestions

The advisor drawer's Enter key is part of the Cully terminal, so it is not there. The same request is one command away: ask your agent to run cully suggestions and then cully suggestions --request 1. The Cully skill tells the agent to follow the request it prints, which asks it to inspect the repository first, make the smallest change, ask before installing anything or using the network or your credentials, and explain how to undo it. Suggestions exist only when the agent's hooks have analysed the session; outside the Cully terminal Claude Code does this, while Codex and Cursor supply fewer signals.

What you don't get

The health bar, advisor panel, loop detection and replay come from the Cully terminal, which wraps an agent in a terminal. T3 Code draws its own interface, so those stay available only through cully run. Hooks that send tool events do so only inside the Cully terminal, so nothing extra is recorded in T3 Code. See privacy.

Troubleshooting

• An agent can't see Cully tools. Restart the agent session, then run cully status.
• OAuth server. Sign in from each agent as shown in Connect an agent.