@sigitcode-old / sigit
Fork 1

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

Code Commits Issues 15 Pulls 1 Cloud Agent CICD
main
claude/github-issue-40-0au5ua claude/sigit-acp-local-chat-cx6380 claude/zen-feynman-0u78dk development feature/account-commands-system-status feature/skill-slash-commands feature/tui-slash-autocomplete feature/xcode-mcp-server fix/zed-commands-after-session-response main
md 116 lines 3.29 KB
Rendered Raw
1 # Editor setup
2
3 siGit Code runs inside any [ACP](acp.md) editor. Every client must pass `--acp`. Guides for Zed, Xcode, VS Code, the JetBrains IDEs and Android Studio follow, and any other client is covered at the end.
4
5 ## Zed setup
6
7 Add this to `~/.config/zed/settings.json`:
8
9 ```json
10 {
11 "agent_servers": {
12 "siGit Code": {
13 "type": "custom",
14 "command": "/absolute/path/to/sigit",
15 "args": ["--acp"]
16 }
17 }
18 }
19 ```
20
21 Use the full absolute path. `~` does not expand here.
22
23 ## Xcode custom agent
24
25 In Xcode, open **Settings > Intelligence > Agents**, add a custom agent, and set:
26
27 - **Executable:** the absolute path to `sigit`
28 - **Arguments:** `--acp`
29
30 In Xcode the `--acp` mode also loads the selected on-device model on the first
31 prompt, so you do not need to send `/load` from the Xcode chat.
32
33 To let siGit use Xcode's build, test, and project tools, enable **Allow external
34 agents to use Xcode tools** in Xcode's Intelligence settings, keep the project
35 open, and add this to `~/.config/sigit/mcp.toml`:
36
37 ```toml
38 [[server]]
39 name = "xcode"
40 command = "xcrun"
41 args = ["mcpbridge"]
42 ```
43
44 ## VS Code
45
46 ### With siGit Code Extension
47
48 Install from the [Visual Studio Code Marketplace](https://marketplace.visualstudio.com/items?itemName=getsigit.sigit-code).
49
50 ```jsonc
51 {
52 "sigit.agents": {
53 "sigit": {
54 "name": "siGit (on-device)",
55 "command": "sigit",
56 "args": ["--acp"],
57 "env": {}
58 },
59 },
60 "sigit.agent.default": "sigit"
61 }
62 ```
63
64 ### With ACP Client
65
66 Install [ACP Client](https://marketplace.visualstudio.com/items?itemName=formulahendry.acp-client), then add:
67
68 ```json
69 {
70 "acp.agents": {
71 "siGit Code": {
72 "command": "sigit",
73 "args": ["--acp"],
74 "env": {}
75 }
76 }
77 }
78 ```
79
80 ## JetBrains IDEs
81
82 The JetBrains IDEs run ACP agents through AI Assistant. We tested siGit Code in RustRover and
83 RubyMine. In the **AI Chat** window, choose **Add Custom Agent**. That opens
84 `~/.jetbrains/acp.json`. Add:
85
86 ```json
87 {
88 "agent_servers": {
89 "siGit Code": {
90 "command": "/absolute/path/to/sigit",
91 "args": ["--acp"],
92 "env": {}
93 }
94 }
95 }
96 ```
97
98 Use the full path to `sigit` as `command`. See JetBrains' [ACP documentation](https://www.jetbrains.com/help/ai-assistant/acp.html).
99
100 ## Android Studio
101
102 Android Studio can connect ACP agents through Bring Your Own Agent (BYOA). It is a preview in the
103 Canary channel, starting with Android Studio Rabbit 2, so you need the latest Canary build. See the
104 Android Developers Blog post
105 [Build your way: Use any AI agent of your choice in Android Studio](https://android-developers.googleblog.com/2026/09/build-your-way-use-any-ai-agent-in-android-studio.html).
106
107 siGit Code is in the agent registry, which you find under **Settings > Tools > AI > Agents**
108 (**Android Studio > Settings** on macOS). Install **siGit Code** there and sign in. The registry
109 entry launches siGit through `npx`. We tested siGit Code in Android Studio this way. The
110 `~/.jetbrains/acp.json` file from the JetBrains section is not part of this setup.
111
112 ## Other editors
113
114 Any other client that speaks ACP works the same way: run `sigit` with `--acp`. The protocol site
115 keeps a list of [ACP clients](https://agentclientprotocol.com/get-started/clients), including
116 Emacs, Neovim, Sublime Text, [marimo](https://github.com/marimo-team/marimo) and VS Code compatible IDEs such as Cursor and Windsurf.