supertool

SuperTool Toggle

Controls whether SuperTool enforcement is active. Enforcement makes the pre-tool-block hook reject competing tools (Grep, Glob, LS, Bash fallbacks), forcing the model to batch via ./supertool.

State lives in ~/.claude/supertool-enforced (empty file = enforced; absent = permissive).

Usage

• /supertool on — enable enforcement (block Grep/Glob/LS + Bash fallbacks)
• /supertool off — disable enforcement (all tools allowed again)
• /supertool status — show current state

Steps

on

mkdir -p "$HOME/.claude"
touch "$HOME/.claude/supertool-enforced"
echo "SuperTool enforcement: ON"
echo "Blocking: Grep, Glob, LS, Bash(cat|find|grep|ls|sed|awk|tail|head)"
echo "Use ./supertool for all reads and searches. Disable with /supertool off"

off

rm -f "$HOME/.claude/supertool-enforced"
echo "SuperTool enforcement: OFF"
echo "All tools allowed. SuperTool still available (./supertool ...)"

status

if [ -f "$HOME/.claude/supertool-enforced" ]; then
    echo "SuperTool enforcement: ON"
    echo "State file: $HOME/.claude/supertool-enforced (present)"
else
    echo "SuperTool enforcement: OFF"
    echo "State file: $HOME/.claude/supertool-enforced (absent)"
fi

When to use each mode

on (enforced) — for autonomous / headless / Kevin-style work

Every file op goes through SuperTool. Model can't fall back to find or grep via Bash. Maximizes batching, saves round-trips, lowers Max-plan quota consumption.

off (permissive) — default for interactive sessions

All tools available. SuperTool still works if you want it, but nothing blocks grep -r or find . -name when those genuinely fit. Less friction for ad-hoc exploration.

Related

• ./supertool — the batched-ops binary (stays available in both modes)
• /tmp/supertool-calls.log — per-call log for adoption analysis
• hooks/session-start.sh — injects batching prompt at session start
• hooks/pre-tool-block.sh — the enforcement hook itself