Kiro

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 integration

For a user-wide installation:

export CHORUS_URL="https://chorus.example.com"
export CHORUS_API_KEY="cho_REDACTED"
curl -fsSL "$CHORUS_URL/install-kiro.sh" | bash

To install only for the current workspace:

curl -fsSL "$CHORUS_URL/install-kiro.sh" | bash -s -- --workspace

Restart Kiro after installation.

Enable remote start

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.

Verify the connection

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.

Capabilities and limits

• 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.

Resume from the terminal

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:

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.

Common issues

• Kiro CLI is not found: install Kiro CLI v2 and rerun the installer.
• Skills are missing: check whether a workspace installation is overriding the user-wide installation, then restart Kiro.
• Check-in is unauthorized: ensure the agent key is available to the shell that starts Kiro, or run chorus login again for daemon mode.
• Daemon is offline: run chorus daemon status, then see Troubleshooting.