siGit is a coding agent that runs on your machine. No API keys. No cloud round-trips.
It works in any codebase, but it's particularly at home in smbCloud repos. It knows the shape of the platform: Rust workspaces, Rails services, deploy flows, auth boundaries, GresIQ. That means less back-and-forth and fewer generic answers when you're working on smbCloud stuff.
Two modes:
- ACP mode — Zed or another ACP-compatible editor starts it over stdio
- Terminal mode — run
sigitdirectly for an interactive chat
| Platform | ACP mode | Terminal mode |
|---|---|---|
| macOS | ✓ | ✓ |
| Linux | ✓ | ✓ |
| Windows | ✓ | not yet |
When siGit is in an smbCloud repo, it uses platform context instead of giving generic cloud-app advice:
- platform user flows vs. tenant app auth flows are different things
Projectis the umbrella workspace;FrontendApp,AuthApp, and GresIQ are separate deployable units- Next.js SSR deploys aren't the same as the git-push path
- existing workspace patterns and crate boundaries over new abstractions
Outside smbCloud repos it stays general. No platform-specific advice where it doesn't belong.
cargo install sigit| Method | Command |
|---|---|
| Homebrew | brew tap getsigit/tap && brew install sigit |
| pip | pip install sigit-code |
| uv | uvx --from sigit-code sigit |
| npm | npm install -g @smbcloud/sigit |
On first launch siGit downloads a GGUF model from Hugging Face, usually 1–2 GB. After that it loads from disk in a few seconds.
On macOS, the model cache is shared with the siGit desktop app through an App Group container. If the desktop app already has the model, the CLI reuses it.
Add to ~/.config/zed/settings.json:
{
"agent_servers": {
"siGit Code": {
"type": "custom",
"command": "/absolute/path/to/sigit"
}
}
}Use the full absolute path. ~ doesn't expand here.
Install ACP client:
{
"acp.agents": {
"siGit Code": {
"command": "sigit",
"args": [],
"env": {}
}
}
}Run sigit in a terminal and you get an interactive chat UI. Same model and system prompt as the editor integration, just without opening Zed.
Terminal mode needs Unix terminal behavior, so macOS and Linux only. Windows gets ACP mode for now.
| Platform | Architecture |
|---|---|
| macOS | arm64, x64 |
| Linux (glibc) | arm64, x64 |
| Windows | arm64, x64 |
© 2026 smbCloud (Splitfire AB).