Shell, editor and terminal configuration, and the tools that go with them https://git.soarez.net/sz/dot.git/atom?h=master 2026-10-05T10:53:09+00:00 2026-10-05T10:53:09+00:00 Igor Soarez igor@soarez.org 2026-10-05T10:53:09+00:00 urn:sha1:611dfd90d4e523984a78728ebfee033e4c16b37d ~/.pi/agent/extensions was a link to the repo's directory, so anything that installs a pi extension wrote into this checkout -- herdr's pi integration did, on one machine. It is now a real directory with the repo's tracked extensions linked in one by one, and a file a machine adds there stays that machine's. pi follows the links, and skips a dangling one silently, so an extension deleted from the repo leaves a harmless stale link. The old directory link is removed first: linking into it would write through to the repo and turn its files into links to themselves. Only tracked files are linked, so a machine's leftovers in the repo's directory are not linked back. The filed version put this loop in link.sh; it lives in link/pi.sh, since link.sh holds one-line links only and a part also obeys ~/.config/dot/skip. From change request 3f6b05. 2026-10-05T06:40:20+00:00 Igor Soarez igor@soarez.org 2026-10-05T06:40:20+00:00 urn:sha1:8c1724fc6af8a223666eecd4687c29f1371d6ddd pi-compact-tools draws each tool call as a short, expandable row; Ctrl+O shows the whole result. Every built-in and every custom tool, MCP ones included, is compacted and starts as a 3-line preview -- previewLines only applies to rows that do not start hidden, so nothing does. Pinned to the v0.14.0 commit, byte-identical to the npm tarball: the package had 32 releases in its first three weeks, and unpinned that would be new code across the fleet nearly every day. The config is linked rather than generated so it is the same everywhere, and /compact-tools saves through the link by design. AGENTS.md now says which linked files their tools rewrite, and that such a change is not an agent's to commit or revert. From change request 4d685a. 2026-09-25T08:30:38+00:00 Igor Soarez igor@soarez.org 2026-09-25T08:30:38+00:00 urn:sha1:57e49ddde1dffb17043cd4b065c2907fbe5a863d models.json was a plain symlink to the tracked file, which left a machine whose models are served from somewhere other than a vendor's own API with nowhere to say so. pi reads providers from exactly one path -- join(getAgentDir(), "models.json") -- and a `providers` block in a settings fragment is inert, because the settings schema has no such key. So on such a machine pi cannot be used at all, and the endpoint is not something this repo may name. link/pi.sh now generates models.json the way it already generates settings.json: the repo's file, then every ~/.config/pi/models.d/*.json. No three-way merge here -- pi never writes this file, keeping runtime state in the sibling models-store.json -- so a hand-edit of ~/.pi/agent/models.json no longer survives a relink. Put it in a fragment. It reports which provider came from which fragment, added or replaced, so a local file shadowing a provider the repo ships cannot do it quietly. Proposed as a change request from the machine that needs it; verified here against pi 0.84.2 before applying. 2026-09-21T11:09:58+00:00 Igor Soarez igor@soarez.org 2026-09-21T11:09:58+00:00 urn:sha1:dec2702337924b9a004acf2afa7574f95d349077 A machine may need one of the parts left out: on a laptop it does not own, ~/.claude/settings.json is the owner's, holding their environment and plugins, and linking this account's over it is wrong in both directions -- theirs is lost, and anything of theirs worth keeping would have to be carried here, in the repo every machine shares. The file is hand-written and in no repo, like ~/.localenv, so the exception stays on the machine that needs it. The check is in link/lib.sh, as each part starts, rather than in link.sh's loop, so `link/claude.sh yes` obeys it too; link.sh and other repos' link.sh source that file as well, and sit outside link/, so their names can never be read as a part's. 2026-09-17T18:45:23+00:00 Igor Soarez igor@soarez.org 2026-09-17T18:45:23+00:00 urn:sha1:13cc065ec014b86369dfe4ad60d1a43fa06fd251 Shell, editor and terminal configuration, the tools that go with them, and szecret, an age-based secret manager whose store lives elsewhere. History restarts here. What came before was not written to be read by anyone else, and carried machine names, addresses and an encrypted secret store; it is kept privately instead. What is left is meant to be safe on any machine, including one whose owner is not me: see CLAUDE.md for the rule it is written to.