I'm siGit, running on siGit Code & Deploy platform, browsing siGit Code coding agent repo.

1 # ACP support
2
3 Zed or another ACP-compatible editor starts siGit Code over stdio with the `--acp` argument.
4 Every ACP client must pass `--acp`. It takes no other arguments, and it is what
5 tells the binary to speak the Agent Client Protocol instead of opening the
6 terminal UI. See [editor setup](editors.md) for client configuration.
7
8 | Platform | ACP mode | Terminal mode |
9 |----------|----------|---------------|
10 | macOS | ✓ | ✓ |
11 | Linux | ✓ | ✓ |
12 | Windows | ✓ | not yet |
13
14 siGit Code speaks [Agent Client Protocol](https://agentclientprotocol.com) v1 over stdio.
15 As of 1.7.0 it implements the whole stable v1 surface an agent can offer:
16
17 | Area | What is supported |
18 |------|-------------------|
19 | Sessions | `session/new`, `load`, `resume`, `fork`, `list` (paged, with a `cwd` filter), `close`, `delete`, and multi-root projects through `additionalDirectories` |
20 | Prompts | Text, images, audio, embedded resources and resource links. Stop reasons `end_turn`, `max_tokens`, `max_turn_requests`, `refusal` and `cancelled` |
21 | Updates | Message and thought chunks with a `messageId`, tool calls with diffs, locations and embedded terminals, plans, `usage_update`, `session_info_update`, slash commands |
22 | Cancellation | `session/cancel`, and `$/cancel_request` for a prompt or a sign-in |
23 | Permissions | `session/request_permission` with allow or deny, once or for the session. Manual, Auto and Plan as config options and as session modes |
24 | Client features | `fs/read_text_file` and `fs/write_text_file`, `terminal/*`, URL-mode elicitation and boolean config options, each used only when the client advertises it |
25 | MCP | stdio and Streamable HTTP servers passed in `mcpServers` |
26 | Auth | `authenticate` (browser sign-in) and `logout` |
27
28 `session/fork` is still marked unstable in the protocol. Draft v2 is not enabled.