tackle ↑ subaud

Small workshop tools for your terminal

tackle

Small command-line tools for your terminal.

tackle is a set of terminal tools in one Go monorepo. Each is an independent binary you install on its own: proj, an agent-aware tmux session picker; scratch, a session-scoped scratchpad; creel, masked capture of a secret into a local .env; sift, audits of the instruction files your coding agents read; and imprint, an npm guide for coding agents.

what it's for

What tackle is.

tackle is a collection of small terminal tools. Each runs on your machine, keeps its state on your disk, and sends no telemetry. It belongs to the .tools family, alongside single-purpose products like a coordination bus, a review tool, and a setup engine.

the tools

What ships today.

Four tools ship from this site, each installed on its own, and casebook has its own site at casebook.tools.

proj →

the agent-aware session picker

proj lists your live tmux sessions — the agent running in each, its state, and any muster attention flag — with a preview pane, per-project servers, and a configurable sidebar.

scratch →

the session-scoped scratchpad

scratch opens a scratchpad scoped to your session. It autosaves to your config directory, not the repo, and an agent can append to the same pad from the command line.

creel →

masked secret capture into a local .env

creel prompts for a secret in a masked field and writes it to a local .env. The value never enters the agent's context — the agent that opened creel gets back only a status token. Run it yourself, or let a harness pass the name and destination.

sift →

audits of the instruction files your agents read

sift reads the files that tell coding agents how to work, such as a repo's AGENTS.md, and finds what is too big, duplicated, stale, dead or misplaced. An agent recommends a revision of each file, you decide each one on a local page, and what you approve becomes one pull request per repo.

imprint →

an npm guide for coding agents

imprint gives a coding agent the npm steps a package owner takes: logging in, publishing, setting a trusted publisher, deprecating and confirming a CI release. It opens each npm approval in your browser and calls a step done only when the registry shows it.

install

Install a tool, run it.

One command downloads the tools, verifies each checksum, and puts them on your PATH (~/.local/bin). It runs on macOS and Linux, Apple silicon and x86-64. Name tools to install only those; with none it installs all of them.

$ curl -fsSL https://tackle.tools/install.sh | sh