Jubileus, part 3: the night the second brain learned to code
Five days after the hub existed, I asked an obvious question: if this cockpit can already read my vault, my projects, and my todos, why am I alt-tabbing to a terminal to code? So the hub grew a coding mode. Press the code button and the cockpit becomes a Claude Code front end, built on the Agent SDK, pointed at whichever of my projects I pick from the sidebar.

Coding mode. Projects on the left, session resume below, model picker and usage caps on the right, one prompt box in the middle.
The part I use daily is the session list. Every coding conversation is saved into the vault as a plain markdown note, like everything else, which means “resume where I left off” is just opening a file — from this machine or the other one. The second brain doesn’t have a separate memory for code; coding sessions are notes.
A few design decisions I’d defend:
An autonomy gate, not a yes-button. Agent actions pass through a command
gate with an explicit allow model. This got red-teamed properly: an early
version could be bypassed with shell chaining (&&, ;, backticks), a later
audit found a lone & and ^ still slipped through on cmd.exe. Each bypass
became a test. The gate is the most-attacked code in the project, which is
exactly what you want for the code that decides what runs on your machine.
Multi-model routing. The model picker isn’t decoration — the hub can route sessions to other providers through Anthropic-compatible endpoints. Claude does the serious work; cheaper models are there for the errands.
Usage caps on the dashboard. The 5-hour and weekly limits sit next to the prompt box, always visible. Hitting a cap mid-session taught me to treat tokens like any other budget: watch it, spend it deliberately.
The decision I’m most fond of, though, is a feature that isn’t there. Concurrent session tabs were specced, started, and then deliberately parked mid-implementation, with a note in the dev log that boils down to: this touches the permission gate, and you don’t 1am-marathon the permission gate. The unfinished tab registry is still in the codebase, waiting for a morning brain. Knowing which code needs you sharp is a feature too.