sbx up: take back the retired MultiEdit/LS/NotebookRead denies it wrote before #572
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 67/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- cli, developer-experience
Research direction
Start in packages/mocactl/src/sbx/agent-config.ts at writeAgentConfig and read how recorded item operations on permissions.deny are handled by dropAt and its guards. Add the retired deny entries to the take-back flow, removing only entries recorded as written by sbx up, and update the record to match. Done when those old entries are cleaned up while hand-added entries remain; the issue does not name a test to run.
Written by the indexing model from the issue text.
Description
Follow-up from the #572 review.
#572 dropped MultiEdit, LS and NotebookRead from CLAUDE_DENY, because current Claude Code warns at every start about a deny rule naming no known tool. Repositories configured before #572 still have those three entries in .claude/settings.json. Re-running sbx up adds the new entries but doesn't remove the old ones, so those repositories keep the three warnings until sbx rm then sbx up, or a hand edit.
sbx up records what it added in .sbx/agent-config.json (op item on permissions.deny). It could remove exactly the retired deny entries that it wrote earlier, and update the record to match. It would leave any the developer added by hand.
Where
packages/mocactl/src/sbx/agent-config.ts:writeAgentConfig(a retired-names list, plus a take-back of matching recordeditems throughdropAtwith its guards)
🤖 Assisted-By: Claude Code
- Dominant language
- TypeScript
- Stars
- 5
- Forks
- 11
- Avg merge
- 8h 32m
- Merged PRs (30d)
- 166
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from rossoctl/moca
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
rossoctl/moca#421 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
Similar issues
-
triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
🎙️ task - drop the raw `./node_modules/.bin/rhachet roles boot` line from bhuild's feedback templateOpen
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
ehmpathy/rhachet-roles-bhuild#639 ·
Maintainers usually reply within 1 day
-
e2e-failure ready-to-code
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
redhat-developer/rhdh-plugin-export-overlays#4650 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 13 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
omdsh-dev/DSH-better-sidebar#1098 ·
Maintainers usually reply within 2 days