Distribute macOS Kiro CLI as `.tar.gz`/`.zip` archive (`.dmg` not supported by ACP registry)

[timorunge]

Kiro Product

CLI

Feature Description

Situation: The Agent Client Protocol (ACP) is a new open standard for how editors communicate with AI coding agents. Its registry allows editors like JetBrains IDEs and Zed to automatically discover, download, and launch agents - no manual setup needed. I've opened agentclientprotocol/registry#208 to add Kiro, but it's Linux-only because macOS Kiro CLI is currently only distributed as .dmg, which the registry rejects. The registry needs archives it can extract and run programmatically without user interaction.

Task: We need macOS Kiro CLI distributed as a .tar.gz or .zip archive (containing the kiro-cli binary) so we can add macOS platform entries to the registry.

Action: The Linux kirocli-{arch}-linux.tar.gz archives work perfectly - we're using those in the PR already. A matching kirocli-{arch}-darwin.tar.gz (or .zip) would let us complete cross-platform support.

Result: Kiro would appear as an available agent for macOS developers across all editors that integrate the ACP registry for agent discovery and launch.

Use Case

• Editor integrations (JetBrains, Zed) use the ACP registry to discover and launch agents. Without macOS archives, Kiro won't appear for the majority of developer workstations.
• The existing .dmg contains the binary at Contents/MacOS/kiro-cli - repackaging it as a .tar.gz or .zip alongside the existing Linux archives would be sufficient.

Additional Context

• PR adding Kiro (Linux-only): Add Kiro to ACP registry agentclientprotocol/registry#208
• Supported archive formats: .zip, .tar.gz, .tgz, .tar.bz2, .tbz2
• Rejected formats: .dmg, .pkg, .deb, .rpm, .msi, .appimage
• Windows CLI archives would also be welcome if/when available

[github-actions]

Thanks for opening this issue and for the thorough write-up! 🎉 The idea of distributing the macOS Kiro CLI as a .tar.gz or .zip archive to enable cross-platform support in the ACP registry is a great one, and we appreciate you already laying the groundwork with your registry PR. A maintainer will take a look at this soon — thanks for helping make Kiro more accessible to developers across editors and platforms!