Mods need allow permissions to iterate on them, could be added to docs
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- cli, documentation
Research direction
No documentation file is named in the issue. Start by locating the documentation for mod-builder output and permission configuration, then add guidance for allowing edits to .commandcode/mods/**. Done means the documented configuration explains how to avoid repeated approval prompts when iterating on generated mods.
Written by the indexing model from the issue text.
Description
Summary
After building a mod with mod builder, I want to iterate on it.
But, the mods dir requires allow permissions.
That's fine but would be nice to add that to the docs so know for to do.
⚠ Sensitive file — path is inside .commandcode/ (Command Code settings). Never touched without approval.
Do you want to create .commandcode/mods/erd/commands.ts?
❯ 1. Yes
2. No, tell Command Code what to do differently
Expected Behavior
Add to docs something like:
{
"permissions": {
"allow": [
"Edit(.commandcode/mods/**)",
]
}
}
so editing mods can flow smoothly.
Actual Behavior
- asked to approve edits to any mod
Steps to reproduce the issue
- use mod-builder to build a mod
- then iterate on it to make changes
Command Code Version
1.5.0
Operating System
macOS
Terminal/IDE
ghostty
Shell
zsh
Additional context
No response
- Dominant language
- No language data
- Stars
- 4k
- Forks
- 350
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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 CommandCodeAI/command-code
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
CommandCodeAI/command-code#855 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
CommandCodeAI/command-code#841 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
CommandCodeAI/command-code#655 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 70/100
CommandCodeAI/command-code#893 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
CommandCodeAI/command-code#892 ·
All issues in CommandCodeAI/command-code
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
from:qa priority:P2 reliability tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
spec-kitty/spec-kitty#4874 ·
-
0. Needs triage bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
nextcloud/fulltextsearch#1011 ·
-
automation code-quality cookie deep-report documentation improvement quick-win task-mining
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100