Roadmap 0.11, Decision points

PERM.1 Decide the permission rules for kickoff sessions: review the stalls seen in 0.10 and the five proposed rules

  • Decision
  • Decision Time

Decision for the owner (2026-11-16). During the 0.10 kickoff run, Claude Code sessions stopped and waited on permission prompts about ten times, some for 14 to 15 hours (about 60 session-hours in all): `rm` of a session's own scratch folder, a read of its own test output, `rmdir` of an empty temp folder, a `grep` for the words DELETE FROM, a Monitor wait, and two real file deletions. Each was safe and was answered by hand. The full table, what is already in force (the rewritten rm hook, three allow rules, each with how to revert) and the proposed rules is in docs/0.10-sessions/permission-review.md.

PROPOSED, none applied: (1) rmdir allowed inside /tmp, repo tmp/ and docs/results/ only; (2) the words DELETE FROM allowed only in commands that just read files, never in anything that can run SQL (in the hook, with a log); (3) no rule for deleting a repo file: sessions log each deletion with its reason and backup and the owner reviews the list at closing; (4) one permanent watcher that records every prompt, instead of a 30-minute monitor someone must re-arm; (5) simpler commands for the prompts no rule can clear (Claude Code's own 'dangerous rm' and 'variable can't be checked' warnings), added to the next kickoff's rules.

To decide: which of 1 to 5 to implement, change or drop, and whether to keep or revert what is already in force. A rule is added only after that, in the hook file, with a backup.

Waits on: Owner's pick.

Add a comment

Community comments

No comments yet

Add detail as we go: how you would use it, files or steps that show the problem, what other programs do. The team reads every comment.

Sign in or create a free account to add a comment.