grix-connector 4.7.2 → 4.9.1

package/README.md

@@ -33,8 +33,27 @@ Set `client_type` in your config to one of the values below. Each `client_type`
 | `openhuman` | OpenHuman | openhuman | `openhuman-core` |
 | `agy` | Agy (Antigravity) | agy | `agy` |
 | `hermes` | [Hermes](https://github.com/askie/grix-hermes-python) | external | `hermes` |
+| `acp` | Any Agent Client Protocol CLI | acp | your own (`command`) |
 
-The ACP adapter (Agent Client Protocol over JSON-RPC) backs Gemini, Qwen, Copilot, Kiro and Reasonix. Hermes is an external agent maintained in a separate project — see [grix-hermes-python](https://github.com/askie/grix-hermes-python) for setup.
+The ACP adapter (Agent Client Protocol over JSON-RPC) backs Gemini, Qwen, Copilot, Kiro, Kimi and Reasonix. Hermes is an external agent maintained in a separate project — see [grix-hermes-python](https://github.com/askie/grix-hermes-python) for setup.
+
+`client_type: "acp"` is the generic entry: if your CLI speaks the Agent Client Protocol over stdio JSON-RPC, connect it with configuration only — no code change, no new release. Give it the executable in `command`, and put the CLI's own ACP subcommand or flag in `args` (nothing is injected for you):
+
+```json
+{
+  "name": "my-acp-agent",
+  "ws_url": "wss://ws.grix.im/v1/agent-api/ws",
+  "agent_id": "your-agent-id",
+  "api_key": "your-grix-api-key",
+  "client_type": "acp",
+  "command": "my-cli",
+  "args": ["acp"]
+}
+```
+
+The generic entry ships the shared ACP surface (session binding, permission prompts, model/mode switching, file browsing). Per-agent extras — an installation guide, a dedicated toolbar, session usage parsing — still require a registered `client_type`.
+
+Two limits of the generic entry are deliberate and will not be changed. Skill discovery for `client_type: "acp"` falls back to the Gemini layout, so it reads `~/.gemini/skills` and shares that directory with a real Gemini agent on the same machine. `get_session_usage` is not declared for it, because there is no parser for an unknown CLI's usage output. A CLI that needs its own skill directory or usage parsing must be registered as its own `client_type`.
 
 For DeepSeek Harness, install the official CLI and complete its login/profile setup before starting the connector:
 
@@ -242,8 +261,10 @@ Each agent entry uses one flat structure:
 | `pool.maxSize` | no | Max adapter pool size (default 20) |
 | `pool.idleTimeoutMs` | no | Idle adapter eviction timeout (default 300000 = 5 min) |
 | `codex_config_overrides` | no | Codex-only app-server config overrides. The connector serializes this JSON object into validated `-c` flags. |
+| `command` | `acp` only | Executable to spawn for `client_type: "acp"`. Required for that type, ignored by every other type (their command is built in). |
+| `args` | no | Extra CLI arguments appended to the adapter's built-in ones. For `client_type: "acp"` these are the only arguments passed. |
 
-Adapter command/args/options are built in and resolved from `client_type`. To connect a different agent, simply change `client_type` — no other config changes needed.
+Adapter command/args/options are built in and resolved from `client_type`. To connect a different agent, simply change `client_type` — no other config changes needed. The one exception is `client_type: "acp"`, where the command comes from your config.
 
 For Codex context trimming, disable plugin suggestions without changing the user's own Codex CLI profile: