3 files changed
+12
-12
Cargo.lock
+1
-1
@@ -5271,7 +5271,7 @@ checksum = "0fda2ff0d084019ba4d7c6f371c95d8fd75ce3524c3cb8fb653a3023f6323e64"
5271
5272
[[package]]
5273
name = "sigit"
5274
-version = "1.0.0"
5274
+version = "1.0.2"
5275
dependencies = [
5276
"agent-client-protocol",
5277
"anyhow",
Cargo.toml
+1
-1
@@ -1,6 +1,6 @@
1
[package]
2
name = "sigit"
3
-version = "1.0.0"
3
+version = "1.0.2"
4
edition = "2024"
5
description = "siGit Code — ACP-compatible AI coding agent for smbCloud platform."
6
documentation = "https://github.com/getsigit/sigit"
README.md
+10
-10
@@ -8,14 +8,14 @@
8
<a href="https://github.com/getsigit/sigit/blob/main/LICENSE"><img src="https://img.shields.io/badge/license-Apache--2.0-235843?style=flat-square&labelColor=17211D" alt="License"></a>
9
</p>
10
11
-siGit is a coding agent that runs on your machine. No API keys. No cloud round-trips.
11
+siGit is a coding agent that runs on your machine. No API keys, no cloud round-trips, no subscription.
12
13
-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.
13
+It works with any codebase. It knows smbCloud repos a bit better — the Rust workspace layout, deploy flows, auth boundaries, GresIQ — so you spend less time explaining the setup.
14
15
Two modes:
16
17
- **ACP mode** — Zed or another ACP-compatible editor starts it over stdio
18
-- **Terminal mode** — run `sigit` directly for an interactive chat
18
+- **Terminal mode** — run `sigit` for an interactive chat UI
19
20
| Platform | ACP mode | Terminal mode |
21
|----------|----------|---------------|
@@ -25,14 +25,14 @@ Two modes:
25
26
## smbCloud context
27
28
-When siGit is in an smbCloud repo, it uses platform context instead of giving generic cloud-app advice:
28
+In an smbCloud repo, siGit knows the terrain:
29
30
-- platform user flows vs. tenant app auth flows are different things
30
+- platform user flows and tenant app auth flows are different things
31
- `Project` is the umbrella workspace; `FrontendApp`, `AuthApp`, and GresIQ are separate deployable units
32
- Next.js SSR deploys aren't the same as the git-push path
33
- existing workspace patterns and crate boundaries over new abstractions
34
35
-Outside smbCloud repos it stays general. No platform-specific advice where it doesn't belong.
35
+In other repos it stays general and doesn't pretend otherwise.
36
37
## Install
38
@@ -51,7 +51,7 @@ cargo install sigit
51
52
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.
53
54
-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.
54
+On macOS, the model cache is shared with the siGit desktop app via an App Group container. If the desktop app already pulled the model, the CLI reuses it.
55
56
## Zed setup
57
@@ -88,9 +88,9 @@ Install [ACP client](https://marketplace.visualstudio.com/items?itemName=formula
88
89
## Terminal mode
90
91
-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.
91
+Run `sigit` in a terminal and you get an interactive chat UI. Same model and system prompt as the editor integration, just without Zed.
92
93
-Terminal mode needs Unix terminal behavior, so macOS and Linux only. Windows gets ACP mode for now.
93
+Terminal mode needs Unix terminal behavior, so macOS and Linux only for now.
94
95
## Platform support
96
@@ -106,4 +106,4 @@ Terminal mode needs Unix terminal behavior, so macOS and Linux only. Windows get
106
107
## Copyright
108
109
-© 2026 [smbCloud](https://smbcloud.xyz/) (Splitfire AB).
\ No newline at end of file
109
+© 2026 [smbCloud](https://smbcloud.xyz/) (Splitfire AB).