Skip to content

Add Kiro CLI - #561

Open
CatherineCao2016 wants to merge 1 commit into
agentclientprotocol:mainfrom
CatherineCao2016:add-kiro
Open

Add Kiro CLI#561
CatherineCao2016 wants to merge 1 commit into
agentclientprotocol:mainfrom
CatherineCao2016:add-kiro

Conversation

@CatherineCao2016

Copy link
Copy Markdown

This PR adds Kiro CLI to the agent registry.

Kiro CLI provides an ACP server via kiro-cli acp, letting ACP-compatible clients discover Kiro CLI, download a versioned release, verify the checksum, and start its ACP server automatically.

Distribution

  • Initial entry supports Linux x86_64 and ARM64 on Kiro CLI 2.20.1 (version-pinned .tar.gz archives with SHA-256 checksums from the official release manifest).
  • macOS and Windows are excluded for now: those platforms currently ship only .dmg / .msi installers, which the registry does not accept. Users on macOS and Windows can download Kiro CLI directly from kiro.dev. We plan to add these platforms to the registry once versioned archive builds are available.

Authentication

When authentication is required, Kiro CLI advertises the kiro-login method during ACP initialization; users complete authentication by running kiro-cli login in a terminal.

Validation

  • build_registry.py passes locally (schema, icon, and URL validation): Added agent: kiro v2.20.1.
  • Download URLs are version-pinned and verified reachable; SHA-256 values come from the official release manifest.
  • icon.svg is a 16x16 monochrome currentColor glyph of the Kiro mark.

AbduRahmanS added a commit to AbduRahmanS/kiro-acp-bridge that referenced this pull request Sep 5, 2026
Two corrections after reviewing the other Kiro submissions to the ACP Registry.

The authMethods claim was wrong. I reported that Kiro returns authMethods: [] and
concluded it advertises no auth method at all. It is state-dependent: the shipped
binary contains a kiro-login method ('Kiro Login', 'Run `… login` in terminal to
authenticate') which it advertises when authentication is required. The empty list
I measured means 'nothing needed right now', because the test machine was signed
in. Registry PR agentclientprotocol/registry#561 states this independently, which
is what prompted the recheck.

Terminal auth is still justified, but for narrower and more accurate reasons: a
client must decide what to render from one initialize response without knowing the
auth state, and kiro-cli may be absent entirely -- which is the Registry runner's
condition, since the bridge ships via npx and does not bundle Kiro. Both are now
stated instead of the stronger wrong claim, in auth.ts, bridge.ts, research.md,
publishing.md, capability-matrix.md, final-report.md and the two fixtures.

Renamed the registry display name from 'Kiro' to 'Kiro Bridge'. Three open PRs
(#33, #209, #561) submit Kiro CLI itself under id 'kiro'; taking the bare name for
a third-party wrapper would be confusing next to those and would imply an
endorsement that does not exist. #482 sets the precedent with 'Kiro Gateway'. The
description now leads with what this adds rather than restating what Kiro is.
AbduRahmanS added a commit to AbduRahmanS/registry that referenced this pull request Sep 5, 2026
Three open PRs (agentclientprotocol#33, agentclientprotocol#209, agentclientprotocol#561) submit Kiro CLI itself under id 'kiro'. Taking the
bare name 'Kiro' for a third-party wrapper would sit confusingly beside those and
would imply an endorsement that does not exist. agentclientprotocol#482 sets the precedent with 'Kiro
Gateway'.

The description now leads with what this adds rather than restating what Kiro is,
since the entry only makes sense in relation to Kiro CLI.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant