Pre-approve crit + tailscale serve remote-review pattern - #41
Merged
Merged
Conversation
crit writes its session lock under ~/.crit/sessions, which isn't in the global sandbox allowWrite list. Every crit launch (tailscale or not) hit a write denial and needed dangerouslyDisableSandbox as a retry, confirmed via cq across 6 sessions with a 100% hit rate. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
crit's documented remote-review recipe (SKILL.md's tailscale block) launches crit with --public-url + --allow-unauthenticated-network and proxies it with tailscale serve. The auto-mode classifier flagged --allow-unauthenticated-network as risky and forced a fresh confirmation every session, even though it's the expected pattern (confirmed via cq across tailscale-review sessions). Add explicit Bash allow rules for both commands so they don't need re-confirming each time. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
technicalpickles
enabled auto-merge (squash)
September 15, 2026 12:46
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
~/.critto sandboxallowWriteso crit's session lock writes don't hit EPERM.critstack pre-approvingcrit --public-url:*andtailscale serve:*, so the documented Tailscale remote-review recipe (loopback host +--public-url+--allow-unauthenticated-network+tailscale serve) doesn't need a fresh auto-mode confirmation every session.This resurrects work from taskwarrior task
766057bb(UUID766057bb-e506-4a30-a157-31c4091ee289), which was marked completed on 2026-09-01 but the actual commits (b45730e,6de6bb5) were stranded on an unmerged branch and never reachedmain. Cherry-picked here with a conflict resolved inclaude/roles/base.jsoncagainst the newerallowWritelist.Test plan
npm run lintpasses./claudeconfig.shregenerates~/.claude/settings.jsonand confirmedBash(crit --public-url:*),Bash(tailscale serve:*), and~/.critallowWrite are present