Documentation / MCP and ACP
Kiro, Codex and Antigravity
Yuli as both an ACP client and an MCP server, so you can work with your own Kiro, Codex or Antigravity inside the IDE.
Besides Claude Code, Yuli works with Kiro, Codex and Antigravity, each with your own account. For them, Yuli is an ACP client (Agent Client Protocol), just like other IDEs, and at the same time their MCP server.
| Channel | What for |
|---|---|
| ACP | Yuli sends your requests and receives the live response, the reasoning, the permissions and the plan. |
| MCP | The agent uses the yuli_* tools: build, tests, verification, quality, database, Web Studio… |
Each agent has its own conversation, mission and changes window. Switching agents never mixes states.
Choose the agent
In the Who do you work with? picker above the chat, under the “Your subscription · your account” group:
| Agent | Account |
|---|---|
| Claude Code | Your Claude account (Pro, Max or Console). See Claude Code. |
| Kiro | Your AWS Builder ID, Google or GitHub. |
| Codex | Your ChatGPT account. |
| Antigravity | Your Google account. |
Yuli never downloads or redistributes these agents: it detects the one you installed.
Kiro
| Step | Details |
|---|---|
| Install | If it's missing, you'll see “Install Kiro CLI to use it here” with the link to kiro.dev/cli and the official command. Requires version 1.28.2 or later. |
| Notice | “Before you start with Kiro”: Kiro uses your account and your credits, and the code it reads travels to AWS under your terms. |
| Sign in | Sign in opens kiro-cli login in a Yuli terminal. For remote machines, Use a device code. |
| Rules | In .kiro/steering/yuli.md and procedure files, or with the first request if the configuration lives outside the project. |
Yuli starts Kiro with kiro-cli acp and authentication through the CLI itself. The token stays in Kiro.
Codex
| Step | Details |
|---|---|
| Install | npm install -g @openai/codex @agentclientprotocol/codex-acp. Yuli uses the official codex-acp ACP adapter; if it only finds codex, it tells you the adapter is missing. |
| Notice | “Before starting with Codex”. |
| Sign in | codex login in a Yuli terminal, or with a device code. |
| Rules | In a managed block of AGENTS.md, or with the first request if the configuration lives outside the project. |
Antigravity
| Step | Details |
|---|---|
| Install | Download the Antigravity ACP server published by Google and unzip it into ~/.antigravity/acp/. |
| Notice | “Before starting with Antigravity”. |
| Sign in | There's no login CLI: the server opens Google's page in your browser and the session starts on its own. |
| Rules | In .agent/rules/yuli.md, or with the first request if the configuration lives outside the project. |
Google states that accessing Antigravity with unofficial tools may violate its terms. Yuli shows this in the preliminary notice. Review them before using it.
Working with an ACP agent
- Conversation with Yuli's design: the response as it's written, collapsible reasoning, tools as a timeline, the plan, the changed files and the verification.
- Text box:
Entersends,Shift+Enteradds a line,@mentions files and/shows the commands the agent advertises. - Queue: if the agent is working, whatever you send is queued. Stop (or
Esc) cancels the turn. - Model, effort and mode: from the lists the agent itself advertises.
- History: open a previous session or start a new one.
- Permissions: each request appears in a Yuli card with exactly the agent's options. Yuli never invents an option or answers on your behalf.
Definition of done
These agents don't have a hook that blocks the end of the turn, so Yuli enforces it as the client: if the turn changed code and verification or measurement isn't green, it sends a brief automatic follow-up listing what's missing.
- It shows in the conversation as a message from Yuli.
- It has a limit (3 by default) and you can turn it off with Automatic follow-ups, since it uses your credits.
- If the connection to the agent drops, Yuli never resends anything on its own.
The same rules
Git, CI and DevOps only if you ask; branches only if you ask; protected secrets; structure and names checked; project hooks. The same as with Claude Code.
Other agents: exported rules only
Gemini CLI, Cursor and GitHub Copilot don't run inside Yuli. What you can do is give them the same project rules: in the Governance Center, Agents → Context, export to GEMINI.md, .cursor/rules/yuli.mdc and .github/copilot-instructions.md. See Gate and Governance Center.