chore(claude): allow everything, deny the memory directory #897
No reviewers
Labels
No labels
burndown-2026-06
burndown-2026-08
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
coherence-core
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
qa-fixture
role/advocate
role/director
role/exec
role/frontend
role/gamedev
role/human
role/platform
role/qa
role/science
role/sysadmin
state
ambient
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/infrastructure!897
Loading…
Reference in a new issue
No description provided.
Delete branch "chore/claude-permissions-allow-all"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Two commits.
.claude/settings.json- the permissions block is now two rules: allow*, deny the auto-memory directory. The sixteen-entry read-only Bash allowlist is gone. It was a prompt-reduction list rather than a guardrail, since an agent denied one spelling just reached for a permitted one.The deny is spelled twice because
WriteandEditare distinct tools and one spelling alone leaves the other free to create a memory file. It mirrors the two entriesapply-base-claude-settings.pyalready stamps into~/.claude/settings.jsonfleet-wide..pre-commit-config.yaml-check-illegal-windows-namescarried no stage pin, so it also ran atcommit-msgand was handed$GIT_DIR/COMMIT_EDITMSG. From a linked worktree git resolves that absolute, and the drive colon reads as an illegal Windows name, so every commit from a worktree failed. Pinning it topre-commitwas a prerequisite for landing the first commit at all, since agents are required to take a worktree when the canonical checkout holds another task's branch.🤖 Generated with Claude Code