[Proposals] - Add CLI Command & Implementation Metadata to ACP Registry

[jbpin]

Hi,

While working on ACP, I found it useful to associate the official CLI command with each agent in the registry. This makes it easier to detect which agents are installed on a host and to automatically determine how ACP should be configured.

For example, something like the following mapping works well:

claude-acp -> claude
codex-acp -> codex
opencode -> opencode
mistral-vibe -> vibe
gemini -> gemini
github-copilot-cli -> copilot
pi-acp -> pi
goose -> goose
qwen-code -> qwen

Using the registry, ACP can check whether the corresponding CLI is available on the system and infer the setup automatically.

Two related improvements might make this more robust:

1. OS / distribution information
   The current registry seems to lack clear information about supported platforms (Windows, macOS, Linux distributions, etc.). It might be useful to introduce something closer the distribution section so ACP can determine how an agent is installed or discovered depending on the OS.

2. ACP implementation type
   It could also be helpful to specify whether the ACP support is:

   • native (the agent implements ACP directly), or
   • adapter-based (ACP is supported through an adapter layer).

Both pieces of metadata would help ACP:

• detect installed agents more reliably,
• determine the correct setup path,
• and avoid hardcoding per-agent logic.

Curious to hear what others think about this approach.