Blog
The design of a yes.
Loom answers Claude Code's permission prompts so six parallel sessions never stall. That sounds reckless until you look at how the yes is built. This post walks through the three decisions behind it.
Three decisions
A yes with a narrow meaning.
Only the safe affirmative
Claude Code prompts often offer more than one way to agree. Some approve the single action in front of you, some grant something broader. Loom presses only the conservative one, every time.
A deny-list that holds regardless
Secret paths are blocked on reads and writes below the prompt layer. It does not matter what was approved or by whom. The deny-list applies either way.
An override per terminal
Press shift+tab in any terminal to cycle that one session's permission mode. Five sessions run free while the one touching something delicate asks first.
The failure mode
Stalling six sessions is the worse outcome.
One Claude Code session that pauses for permission costs you a glance. Six of them pause constantly, and every unanswered prompt parks a session until somebody notices. Run a fleet by hand and you spend the evening pressing enter, which is exactly the job the Conductor exists to do. Auto-accept is what turns six terminals from six tabs you babysit into work that runs while you sleep.
# Claude Code asks before acting
Run cargo test?
$ Loom presses the safe affirmative
# the deny-list still guards secret paths
# shift+tab flips this terminal to manualWhy not just approve everything
Because a yes that means anything, forever, is not a permission system. It is the absence of one. The design rests on keeping the yes narrow and putting the real guarantees somewhere a prompt cannot reach:
- The affirmative approves the action in front of it, never a standing grant.
- The secret-path deny-list sits on reads and writes and holds no matter what was approved upstream.
- A workspace authorization registry covers every file, git, and shell operation. The security page has the full layered picture.
- The switch stays yours. Auto-accept is toggleable globally, and shift+tab tunes a single terminal without touching the other five.
The result is a yes you can leave alone for hours. Whether the work it unblocked actually got finished is a separate question, and Loom is just as careful about that one. Read done means verified next.
Hand it the work.
Walk away.
macOS, Linux, and Windows. Around 13 MB. Free and open source.