siGit Code

siGit Code is a local coding agent. It runs on your machine, not someone else's. No API keys, no cloud round-trips, no subscription.

Its home is code.sigit.si. You can run it yourself, as below, or use the hosted version (siGit Code Cloud) there if you would rather not run a model locally. sigit.si is Git hosting built for AI workflows.

It works in any codebase. In smbCloud repos it is more useful out of the box because it already understands the Rust workspace layout, deploy flows, auth boundaries, and GresIQ.

You can use it in two ways:

ACP mode: Zed or another ACP-compatible editor starts it over stdio
Terminal mode: run sigit for the interactive chat UI

Platform	ACP mode	Terminal mode
macOS	✓	✓
Linux	✓	✓
Windows	✓	not yet

Install

cargo install sigit

Method	Command
Homebrew	`brew tap getsigit/tap && brew trust --tap getsigit/tap && brew install sigit`
pip	`pip install sigit-code`
uv	`uvx --from sigit-code sigit`
npm	`npm install -g @getsigit/sigit`
NuGet	`dotnet tool install --global SiGit.Code`
winget	`winget install smbCloud.siGitCode`
Scoop	`scoop bucket add getsigit https://github.com/getsigit/scoop-bucket && scoop install sigit`
AUR	`yay -S sigit-bin`
Debian/Ubuntu	download the `.deb` from releases, then `sudo dpkg -i sigit_*.deb`
Fedora/RHEL	download the `.rpm` from releases, then `sudo rpm -i sigit-*.rpm`

First run

The first launch downloads a GGUF model from Hugging Face. Expect roughly 1 to 2 GB, depending on the model. After that, loads come from disk and are much faster.

On macOS, siGit Code shares its model cache with the desktop app through an App Group container. If the desktop app already downloaded the model, the CLI reuses it.

Zed setup

Add this to ~/.config/zed/settings.json:

{
  "agent_servers": {
    "siGit Code": {
      "type": "custom",
      "command": "/absolute/path/to/sigit"
    }
  }
}

Use the full absolute path. ~ does not expand here.

Xcode custom agent

In Xcode, open Settings > Intelligence > Agents, add a custom agent, and set:

Executable: the absolute path to sigit
Arguments: --acp

The explicit --acp mode is designed for Xcode: it loads the selected on-device model on the first prompt, so you do not need to send /load from the Xcode chat.

To let siGit use Xcode's build, test, and project tools, enable Allow external agents to use Xcode tools in Xcode's Intelligence settings, keep the project open, and add this to ~/.config/sigit/mcp.toml:

[[server]]
name = "xcode"
command = "xcrun"
args = ["mcpbridge"]

VS Code

With siGit Code Extension

Install from the Visual Studio Code Marketplace.

{
  "sigit.agents": {
    "sigit": {
      "name": "siGit (on-device)",
      "command": "sigit",
      "args": [],
      "env": {}
    },
  },
  "sigit.agent.default": "sigit"
}

With ACP Client

Install ACP Client, then add:

{
  "acp.agents": {
    "siGit Code": {
      "command": "sigit",
      "args": [],
      "env": {}
    }
  }
}

Terminal mode

Run sigit in a terminal and you get the same model and system prompt as the editor integration, just in a full-screen chat UI.

Terminal mode currently needs Unix terminal behavior, so it works on macOS and Linux only.

Platform support

Platform	Architecture
macOS	arm64, x64
Linux (glibc)	arm64, x64
Windows	arm64, x64

siGit