Skip to content

feat(setup): grant full access to .deepwork/ in every project#354

Merged
nhorton merged 2 commits intomainfrom
feat/setup-deepwork-permissions
Apr 9, 2026
Merged

feat(setup): grant full access to .deepwork/ in every project#354
nhorton merged 2 commits intomainfrom
feat/setup-deepwork-permissions

Conversation

@nhorton
Copy link
Copy Markdown
Contributor

@nhorton nhorton commented Apr 9, 2026

Summary

  • deepwork setup now adds Read(/.deepwork/**/*), Write(/.deepwork/**/*), and Edit(/.deepwork/**/*) to ~/.claude/settings.json permissions.allow.
  • The leading slash makes each path project-root-relative per Claude Code permission syntax, so the rules apply to .deepwork/ in every project — not ~/.deepwork/. (Confirmed with the claude-code-guide agent against https://code.claude.com/docs/en/permissions.md.)
  • Updates spec (DW-REQ-005.6.3.5), doc/architecture.md, and CHANGELOG.

Test plan

  • uv run pytest tests/unit/test_setup.py
  • DeepWork reviews clean

nhorton and others added 2 commits April 8, 2026 19:38
Adds Read/Write/Edit permissions for `/.deepwork/**/*` to the user-level
Claude settings during `deepwork setup`. The leading slash makes the path
project-root-relative per Claude Code permission syntax, so the rules
apply inside every project's .deepwork/ — not ~/.deepwork/.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Updates DW-REQ-005.6.3 with new sub-item, architecture.md setup section,
and CHANGELOG to reflect the new project-root-relative permissions for
/.deepwork/**/*.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@nhorton nhorton merged commit 1b8ac70 into main Apr 9, 2026
5 checks passed
@nhorton nhorton deleted the feat/setup-deepwork-permissions branch April 9, 2026 02:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant