aniketpant / tooling

Dev tooling

The agent, the phone and the shell, each built so it outlasts the thing it runs on.

01botfiles

Intent
Agent tooling should not belong to one harness. Every harness has its own plugin API, and configuration written against one of them is lost when the next one arrives.
Now
Extensions, skills, prompts and themes are written once and mount in both pi and OpenCode V2. Where the two harnesses are not equivalent, the capability table records it, so a gap is a documented no-op instead of a fork.
surfacepiopencode v2
ctx.uistatus bar, notifyabsent, no-ops
flagspi.getFlagBOTFILES_* env
transcriptsfilesystem walkobserved sessions
Three surfaces cannot be shared, so they degrade instead of forking the extension: a missing one becomes a no-op, an env fallback, or a smaller set of sessions.

The adapter absorbs the difference

pi runs one extension per session; OpenCode loads one plugin and calls the factory per session, keeping a map from session to instance. Tools and commands register once and carry their own session id, so the extension code never learns which harness it is in.

Skills move with their extension

Skills every session needs live in skills/. A skill that only applies to one extension lives in that extension’s folder, so installing or removing the extension moves the skill with it instead of leaving a dead entry behind.

02droidfiles

Intent
A phone should be rebuildable from a bare Termux, not remembered. Every change that matters lives in the repository, so a reinstall is a command and not an afternoon.
Now
bootstrap.sh installs the package list and calls install.sh, which relinks the dotfiles; both also run alone. Shell tests run in a temporary home, so a restore is checked before it touches mine.
yesnoinstall.shreal file differs?~/.droidfiles-backup/$HOME
A symlink, or a file that already matches the repository copy, is replaced with no backup. Only a real file that differs is kept.

Symlinks, except where Android refuses them

Termux:Widget and Termux:Boot resolve symlinks and refuse a script whose real path is outside their folders. Executables stay in home/bin, and install.sh writes the two wrappers as real files instead of links.

A hand-kept package list

pkg has no installed-on-purpose flag, so packages.txt is maintained by hand and lists what I chose to install, never dependencies. An upgrade that pulls something in does not enter the file, so a restore brings back the system I asked for, not the last one.

03dotfiles

Intent
Muscle memory should move between machines: the same shell, terminal and key map wherever I sit down.
Now
One palette across the shell and the TUI, a Cmd layer on Linux with per-app masks, and stow folders that mirror their home paths, so a new machine takes the same make install.

one palette

ghostty · pi · opencode

Ghostty, pi and opencode read one theme, so a colour means the same thing in the terminal, the prompt and the agent.
zsh/ ghostty/ keyd/make install$HOME
Each folder mirrors its path in the home directory, so stow resolves the target without a mapping file. make clean is a separate target that unstows them.

Cmd on Linux, and what breaks

A keyd layer maps Cmd to Ctrl globally, with a per-app mask so the terminal keeps its own shortcuts. Redefining Super replaces GNOME’s chords, and the README lists the bindings that do not fire rather than pretending the layer is complete.

Deferred until first use

Plugins load through zinit in turbo mode and are deferred until first use. A plugin that cannot be deferred is removed rather than paid for in every shell.

The repositories are private; each section is its public summary.