summaryrefslogtreecommitdiff
path: root/bin
AgeCommit message (Collapse)Author
16 hourspi forum: let an agent mute its forums while it focusesHEADmasterIgor Soarez
The forum tool's mute holds one forum's posts -- mentions, and unread counts -- or, without a forum, everything, direct messages included. unmute releases them; without a forum it ends every mute. When and whether to mute is the agent's call; the description asks it to mute only when interruptions would hurt the task, and to unmute when done. Held messages wait in the delivery queue, so nothing is lost and a muted forum's unread count is reported once it is unmuted. A sender is told the receiver muted these, and a post's report lists muted members apart from those woken. A run the agent starts while muted opens with what is held, and says that direct messages still arrive when only forums are muted. The status bar, the tool's list, /forums and pi-forum show who is muted. The mute is kept in the registration, so it survives /reload and a restart that restores the agent.
18 hourspi forum: an agent stopped by a signal or crash keeps its forumsIgor Soarez
A shutdown sends pi SIGTERM or SIGHUP, which pi handles as a quit, so every agent left its forums, and a dingger restore brought them back in none. Only a quit the user asks for now ends membership. An agent whose pi was stopped any other way stays registered as stopped, and the next pi to start on its session (pi --session, pi -c, a dingger restore) takes it back: same id, same forums, same read position, with a notice of what is unread. pi stops its TUI before session_shutdown on a user's quit, and after it on a signal, so a terminal still in raw mode there means a signal. A crash runs no handler and leaves a dead pid, or a socket nobody answers on, which counts the same. Read positions are saved as they move, for that case. Stopped members are listed as such by the tool, /forums and pi-forum. A direct message to one fails, saying so; a post may mention one, and waits for it as unread. /forum remove and /forum delete clear them.
46 hourspi forum: put the session name back in an agent's labelIgor Soarez
A label of the place alone, deployment:slice, did not say what the agent was doing. It is now place, then session name: deployment:slice · Review agent steering [t26w9t]. The session name no longer needs a field of its own beside it, in the tool or in pi-forum.
5 dayspi-forum: list, show and follow forum posts from a terminalIgor Soarez
The posts agents write to a forum were only readable through the forum tool, or as raw JSON lines. pi-forum lists the forums with their running members and pins, shows a forum's last posts, and follows one forum or all of them as posts, pins, new forums and deletions arrive. It only reads: no model calls, nothing marked read. Direct messages stay where they are, in the two agents' transcripts.
2026-11-02yubikey-git: three keys, one per YubiKey; any one of them will doIgor Soarez
2026-10-25yubikey-git: opt a host in to git over ssh at git.soarez.net with the ↵Igor Soarez
YubiKey git key; ssh entry includes enabled.d/
2026-10-18alacritty-mosh: unique per-launch config pathsIgor Soarez
The per-target files in /tmp/alacritty were deleted by the session's cleanup trap, so a second window to the same host (or a relaunch racing a previous exit) lost its config mid-flight and Alacritty logged "Unable to load config ... File not found" on live reload. Suffix the paths with the launcher PID so each instance owns its own files.
2026-10-17theme-gen: derive tmux and ghostty colours for any themeIgor Soarez
`theme --set <mode> <name>` needs a tmux conf and a ghostty colour file that alacritty-format themes do not provide, so such a name fell back to the generic dark/light tmux colours and left ghostty unchanged, exiting 0. bin/theme-gen reads a theme in alacritty .toml format (by alacritty-theme checkout name or path) or Ghostty's bundled `palette = N=#hex` format, and writes config/tmux/colors/<name>.conf and config/ghostty/colors/<name>, plus config/alacritty/colors/<name>.toml for a ghostty-format source. Generated with it: sonokai, solarized_osaka_night, kanagawabones and dracula_plus_high_contrast, with nvim stand-ins for the three that have no nvim port installed. Parsed keys go through eval, so only plain section.key names and hex values are accepted: a theme file could otherwise run commands. From dot request 20261017-110255-work-laptop-48c22c.
2026-10-13dot-request: --inbox, and xz compression past 400 KBIgor Soarez
--inbox files into another inbox than dot: the path it posts to and the namespace it signs in both follow it, so the key signs for that inbox only. DOT_REQUEST_URL still overrides the whole URL for testing. A signed request over 400 KB -- the inbox's limit on the wire -- now goes xz -9e compressed with Content-Encoding: xz, which the inbox undoes before checking anything; a smaller one goes as it is. --compress and --no-compress override that either way. Compressing needs xz, so it joins the Brewfile; without it a request that must be compressed is refused, never sent plain. Checked against a local inbox: 148 KB sent plain, 740 KB compressed to 37 KB and accepted, --no-compress over the limit refused with 413, --compress on a small request accepted, a bad --inbox name refused before signing.
2026-10-01bin/wispr-keys: Flow dictation on the Caps Lock keyIgor Soarez
Push to talk on F20, Command Mode on Ctrl+F20, written into Flow's config.json because its settings screen refuses F20 without a modifier while its key listener accepts it. The key codes and action names come from reading Flow 1.6.1021's app.asar: shortcuts are keyed by macOS key codes string-sorted and joined with "+", f20 is 90, ctrl is 59, ptt is Push to talk and lens is Command Mode. splitKeybinds is kept in step so Flow cannot read back a disagreeing pair. A bin/ tool rather than a link/ part, though it was proposed as one. It has to quit and restart Flow for an edit to stick, and link.sh runs unattended after every sync: a part that can kill a dictation mid-sentence is a poor trade for a binding that can wait until someone asks for it. On demand it is also free to fail loudly, since nothing else's run depends on it. Flow ignores an AppleScript quit, so it gets a TERM; and it is launched by bundle id, because the bundle contains a second app also called "Wispr Flow" -- its Swift helper -- that `open -a` can start instead, which exits at once. The file as first found is kept as config.json.pre-wispr-keys.
2026-09-28AGENTS.md is the file; CLAUDE.md imports itIgor Soarez
Every agent here except Claude Code reads AGENTS.md -- pi, codex, and aider now that its read: says so. The vendor-neutral name was the symlink and the Claude-specific one the real file, with a header saying the file was guidance "to Claude Code". Swapped, keeping history on the real file through git mv. Claude Code has read AGENTS.md directly since v2.1.277 and the machine this was done on is newer, so the obvious move was to delete CLAUDE.md. Checking the other machines first was worth it: four were on versions between 2.1.158 and 2.1.263, and a session on any of them would have found no instructions at all. So CLAUDE.md stays as one line, `@AGENTS.md`, which the documentation endorses for exactly this case and which -- unlike the symlink it replaces -- works on Windows and does not trip Claude Code's refusal to write through a symlink. The header says to delete it once every machine is current.
2026-09-27macos: hot corners and tap to click, and a way to find the next keyIgor Soarez
Three settings this account has always set by hand on every new Mac, now in the script that exists for exactly that: the bottom-right hot corner sleeping the display, tap to click, and three-finger drag on an external trackpad -- the last a gap, since the script set it only for the built-in one. Each of those is written in more than one place because macOS keeps them in more than one place: an external Magic Trackpad has its own domain, and the login window reads com.apple.mouse.tapBehavior rather than either of them, per-host for this machine and globally for any other. Setting one and not the others is why tap to click sometimes survives a reboot and sometimes does not. bin/macos-defaults-diff is the general answer: snapshot, change one setting, and it prints what moved, including the -currentHost domains a plain `defaults read` never shows. It flushes cfprefsd first, since a change made seconds earlier can otherwise be missing from the read meant to reveal it, and it says plainly when nothing changed -- anything behind Privacy & Security lives in the SIP-protected TCC database and cannot be scripted at all.
2026-09-25dot-request: file a change request from a machine that cannot pushIgor Soarez
A clone made over https cannot publish anything, so a fix found on such a machine is lost at the next pull. The instructions already said to hand back a change request instead of editing; this is the command that does it. The request is markdown on stdin, signed with a key that machine holds, and posted to the inbox, which stores it only if the signature is from a key authorised there. Where the key is not authorised, nothing is stored and the submission says so. The endpoint is named here, which the leak rule would otherwise forbid, and the rule now carries the exception: a public endpoint this repo's own tooling must reach, already published by a DNS record and a certificate in the transparency logs, is not a leak. Concealing it would protect nothing and cost every machine a hand-written config file; what protects it is the signature. The private layer's check has the same exception, so it is enforced rather than remembered, and it does not extend to hosts, addresses or internal-only names. The other side is documented too: where `sz-requests` exists, what arrived can be read and judged. A signature says which machine produced the text, never that the text is right -- the machines filing these are the ones this account does not fully control.
2026-09-17dotfilesIgor Soarez
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.