woswoar

Your shell history, on every machine, encrypted, without a server.

Austrian for "Was war?" — "what was it again?" — which is exactly what you ask when you need that one command from last Tuesday, on the other machine.

_{Re-record it with tools/demo/record.sh — the tape is checked in, the history in it is generated, and nobody's real commands are on screen.}

What it is

Press Ctrl+R and fuzzy-search every command from every machine you own — deduplicated, newest first, with the working directory, exit code and duration recorded alongside. Pick one and it lands on your prompt for editing, never executed behind your back.

Machines exchange history through a git repository you already own. Nothing readable ever reaches it, there is no server and no account, and the thing that runs on your prompt is a fork-free bash hook that appends one line to a file. Half of what you want from history is the command after the one you remember, so Ctrl+T turns whatever you found into the timeline around it.

[!NOTE] woswoar is a lighter alternative to atuin. If you want a sync server, a rich TUI and cross-platform support, atuin is the better tool. woswoar trades those for a design you can hold in your head.

Install

pipx install woswoar
woswoar

Open a new shell, press Ctrl+R. That is the whole thing on one machine. woswoar on its own is the only command you have to remember: it sets up when there is nothing installed, and afterwards says where this machine stands and names the one command to run next, if there is one.

Needs: bash 5.0+ or zsh 5.0+ · Linux or macOS · Python 3.10+ · fzf · age and git (sync only) — but not age as a snap, which costs about 250 ms per call against 2 ms and turns a sync into minutes. woswoar doctor measures it and says so.

📦 Upgrading, importing an existing history, uninstalling

More than one machine

Sync goes through an ordinary git repository you already own — no server, no account, no daemon. Create an empty one (woswoar-history on GitHub, a bare repo on a NAS, a folder on a USB stick), once, ever. Then on every machine:

# on the new machine — or just paste the URL when `woswoar` asks for it
woswoar init git@github.com:you/woswoar-history.git

# on each machine you already use
woswoar accept

accept is grant and trust at once — who may read your history, and whose published history this machine believes. It prints both fingerprints and asks.

🔄 Enrolment, revoking, and keeping an idle machine current

Security

Everything that leaves your machine is encrypted with age — commands, paths, hostnames, even the directory names in the repo. Each machine keeps its own private key and no secret is ever copied between them. There is no crypto code here at all: age does it, and woswoar's wrapper is a few dozen lines of subprocess.

Your local history is plaintext, though, and metadata like "how many machines and how often they sync" is visible to anyone holding the repo.

None of that has to be taken on faith. woswoar doctor --prove records a canary command in a throwaway sandbox, syncs it, and shows you that it reaches the remote unreadable — and that is only the first of the checks you can run yourself, decrypting a chunk with stock age and no woswoar in the pipeline among them.

🔐 The full security model · 🐤 Verify it yourself

How it works

shell hook  ──►  plaintext TSV logs  ──►  parse cache  ──►  scope filter  ──►  fzf
                        │
                        └──►  age-encrypted chunks  ──►  git  ──►  remote

The hot path is a fork-free shell hook — one for bash built on bash 5 builtins, one for zsh built on zsh's — that appends one escaped line to a per-day TSV file. Both write into the same per-machine history. Nothing else touches your prompt. Everything expensive — parsing, caching, encrypting, git — happens when you search, or when the timer fires.

Documentation

License

Apache-2.0