swagLGBT monorepo
- Nix 94.1%
- TypeScript 5.6%
- Go Template 0.3%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
Cass Fridkin
9572c6fc20
supi-web 8.x (the bump from 4.7.0) grew a `web_search` tool that spawns `bx` (brave-search-cli) and only carries weight with a Brave API key — cass has none, and the Context7 docs tools (web_docs_*, keyed via extraApiKeys) usually suffice. Disable it via the SuPi global config: with webSearchEnabled false, supi-web never registers the tool (no dead tool for the model to trip over, no bx to ship on the PATH suffix). web_fetch_md / web_docs_* are unaffected. New mk.nix `supiConfig` knob renders the JSON (~/.pi/agent/supi/config.json); both consumers materialize it as a regular writable file (0600) rather than an agentContent.files symlink, because /supi-settings persists through that path (writeSupiConfig -> writeFileSync) — a read-only store symlink would fail every settings save. Same split as pi-plan-mode.json: the HM consumer via home.activation (piHomeModule), the portable bootstrap per launch. Empty attrset (the default) materializes no file. To re-enable: drop the supiConfig line, put brave-search-cli on the PATH suffix (extraPackages), and give `bx` a key out-of-band (`bx config set-key`) — never via pi settings. Verified: .#pi builds with no brave on the PATH suffix and settings.json byte-identical (no re-fetched FODs); the portable bootstrap under a scratch HOME materializes supi/config.json as a real 0600 JSON file; keroppi evals home.activation.piSupiSettings installing the same store JSON — no consumer drift. Assisted-by: Pi (z-ai/glm-5.3) |
||
| modules | ||
| runbooks | ||
| secrets | ||
| .envrc | ||
| .gitignore | ||
| .sops.yaml | ||
| AGENTS.md | ||
| flake.lock | ||
| flake.nix | ||