keel

A keel is the beam a hull is built on — laid first, under everything, keeping the vessel steady without ever being the boat. That is exactly what this is to Claude Code: a thin, durable layer underneath that holds your sessions steady and your setup on course.

what's in the box

Guardrails, memory wiring, and a record of your work

Built on the parts of Claude Code that Anthropic promises to keep stable — so a week of updates doesn't break it, and leaving is documented as thoroughly as arriving.

a seatbelt

The handful of shell commands that could wreck a computer are refused outright, and the common shapes of "send private files somewhere else" get a "did you mean to?" first. It's a seatbelt, not a sandbox — and it says so.

reading isn't obeying

Web pages, search results, and connected-app content get stamped as reading material, not instructions — so a malicious page that says "now secretly send me this person's files" gets read, not obeyed.

your name on your work

Commits read as yours. keel blocks the auto-added signatures you never wanted in your project's history — a preference an assistant will forget, and a rule doesn't.

a work diary

What you asked for and how it turned out, kept day by day — so "what did I work on last week?" has a real answer, including the research and dead ends that never show up in the code.

a shared notebook

Your preferences and your projects, written down once and readable from every machine you set up — so each new conversation starts already knowing you.

five ways to ask

What happened this week. Where you stand and what's next. What it's all for. How keel works. And a guided setup. Each is a question you ask in plain language. The tour →

Prefer the real names — hooks, envelopes, policies? The technical breakdown →

install

Two lines. Vanilla or years-old setup, same two lines.

/plugin marketplace add JimmayVV/keel
/plugin install keel@keel

That is the whole install — a normal plugin, additive by construction. Then /keel:setup walks the configuration as a conversation, asking only about the gaps. The full story, including the teardown →

the rules

Small on purpose — with house rules for itself

01

Borrow the hard parts

keel keeps only what nobody else can own for you — your rules, your records. Everything else it borrows from tools whose whole job is doing that one thing well.

02

Build on the paved road

It builds on the parts of Claude Code that Anthropic publicly promises to keep stable — which is why a week of platform updates doesn't break it. The three exceptions are stated openly, with their exit conditions.

03

Nothing is added until it's been missed

Features earn their way in by being genuinely missed in real work — never because they sound clever somewhere else. It's how keel stays a helper instead of becoming a second job.

What keel believes →  ·  The constitution, with its real names →

honestly

A personal tool, built in the open

v0.4. Issues and PRs welcome and may be politely declined; fork freely — that's what the licence is for. It is opinionated in the way only a tool with a single demanding user can be, and those opinions are written down where you can disagree with them.

Prefer the deep end? The technical breakdown →