Guides
Ask first, ask less, ask never.
Claude Code pauses before edits and commands. Loom gives you three ways to answer, and shift+tab lets every terminal in the fleet make its own choice.
The three modes
From cautious to hands-off.
Ask first
With auto-accept off, every prompt waits for you, exactly as plain Claude Code would. The right setting for a session working somewhere you want to watch closely.
Auto-accept
Loom watches every terminal and presses the safe affirmative, approving the specific action in front of it and never a broader grant. It is a toggle, not a policy. The auto-accept page has the full story.
Skip entirely
Claude Code ships its own escape hatch, the dangerously-skip-permissions flag, which removes prompts altogether. The word dangerously is in the name for a reason.
Per-terminal control
One fleet, six policies.
Permission modes are not all or nothing. Press shift+tab inside any terminal to cycle that one session's mode, so five sessions can run free while a careful sixth asks before every action. It is the same mechanic plain Claude Code users already know, applied per slot. Mode discipline matters most on long unattended missions, covered in overnight runs.
# cycle one terminal's permission mode
press shift+tab inside that terminal
# Claude Code's own no-prompt escape hatch
$ claude --dangerously-skip-permissionsQuestions
Modes, answered.
Is auto-accept the same as skipping permissions?
No. Auto-accept answers each prompt as it appears and presses only the safe affirmative for that specific action. The flag removes the prompts entirely, so nothing is ever asked. Most missions get all the speed they need from auto-accept.
When is the flag the right call?
Rarely, and mostly in environments where the blast radius is already contained, such as a disposable sandbox. On your own machine, auto-accept covers the same ground while keeping a prompt in the loop for every action.
Can I change modes mid-mission?
Yes. Auto-accept toggles at any time, and shift+tab cycles a single terminal's mode whenever you like. The mission keeps running either way.
What protects the machine beyond prompts?
Loom keeps a secret-path deny-list on reads and writes, routes every file, git, and shell operation through a workspace authorization registry, and stores keys in the OS keychain only. The security page has the full picture.
Hand it the work.
Walk away.
macOS, Linux, and Windows. Around 13 MB. Free and open source.