@vizuh/sabi 0.1.1 → 0.1.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +13 -0
- package/mod/sabi.mjs +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -8,6 +8,19 @@ round 2 on, a read round goes cheap, edits and tests go mid, and a failing tool
|
|
|
8
8
|
This package is the **mod only**. The local proxy (BYOK, for any harness that accepts a `baseURL`)
|
|
9
9
|
lives in the [repository](https://github.com/vizuh/sabi).
|
|
10
10
|
|
|
11
|
+
The two paths are independent:
|
|
12
|
+
|
|
13
|
+
- **Command Code mod:** no Sabi provider key and no proxy; it routes the subscription already
|
|
14
|
+
available to Command Code.
|
|
15
|
+
- **Local proxy:** works with OpenCode, Hermes, Kilo and other OpenAI-compatible clients, using
|
|
16
|
+
OpenRouter, Ollama or another configured upstream.
|
|
17
|
+
|
|
18
|
+
For the proxy, Sabi loads only the credential names referenced by `sabi.config.json`. Existing
|
|
19
|
+
environment variables win, followed by `SABI_SECRETS_FILE`, the nearest workspace `secrets/.env`,
|
|
20
|
+
and `~/.config/sabi/secrets.env` or `~/.config/sabi/.env`. It never copies secret values into a
|
|
21
|
+
harness config, terminal, worktree, log or Git. Users who do not use Jev can set `judge.enabled` to
|
|
22
|
+
`false`; users without a central secrets file can keep exporting provider variables normally.
|
|
23
|
+
|
|
11
24
|
## Install
|
|
12
25
|
|
|
13
26
|
```bash
|
package/mod/sabi.mjs
CHANGED
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
// @vizuh/sabi 0.1.
|
|
1
|
+
// @vizuh/sabi 0.1.2 — generated by pack.mjs from packages/adapters/command-code/mod/sabi.ts.
|
|
2
2
|
// Source and docs: https://github.com/vizuh/sabi
|
|
3
3
|
|
|
4
4
|
// packages/core/src/state.ts
|
package/package.json
CHANGED