Skip to content

Kiro

Kiro CLI has a first-party Chorus integration with tools, workflow skills, agents, and hooks. Kiro is also a supported Chorus daemon backend.

Before installation, install Kiro CLI v2 and create an agent key by following Prepare agent access.

Install the Chorus integration with the chorus CLI:

Terminal window
npm install --global @chorus-aidlc/chorus
chorus agents add --agents kiro

Enter the Chorus URL and agent key when prompted. chorus agents add downloads the Kiro integration files from your connected Chorus instance into ~/.kiro (skills, reviewer agents, and hooks) and merges the Chorus MCP server into ~/.kiro/settings/mcp.json. Set KIRO_DIR before running to install into a different Kiro directory. Restart Kiro after installation.

Skip this section if you only use Chorus from an interactive Kiro session. Otherwise, follow Connect an agent runtime and select kiro as the backend. Verify the connection in the foreground before using Daemon operations to keep it online.

Run kiro-cli --agent chorus, then ask Kiro to check in to chorus. Confirm that the response shows the expected agent identity and permissions. Run /chorus-idea to confirm that Chorus skills are available.

For daemon mode, open Settings → Agents in Chorus and confirm that the expected host and working directory are online.

  • The integration provides Chorus MCP tools, workflow skills, reviewer agents, and hooks.
  • Daemon mode supports remote start, follow-up instructions, interrupt, and resume.
  • Workspace configuration takes precedence over user-wide Kiro configuration.
  • Remote work inherits the local user’s access. Register only trusted working directories.

Use Remote control and Session recovery for shared operating procedures.

To take over a live conversation from your own terminal, copy its session id from the chat UI (Copy session ID in the transcript header) and run, from the conversation’s working directory:

Terminal window
kiro-cli chat --resume-id <sessionId>

The copied id is the same id Chorus passes to Kiro CLI when it resumes a session. See Interrupt and resume a session for the full flow.

  • Kiro CLI is not found: install Kiro CLI v2 and re-run chorus agents add.
  • Skills are missing: check whether a workspace installation is overriding the user-wide installation, then restart Kiro.
  • Check-in is unauthorized: re-run chorus agents add so mcp.json and the credential are refreshed; for daemon mode the daemon supplies the key per wake.
  • Daemon is offline: run chorus daemon status, then see Troubleshooting.