Safety system
Open
Nobody has claimed this yet.
needs-info
priority: low
question
triage: unclear
- Dominant language
- Rust
- Stars
- 19.9k
- Forks
- 2.3k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 30
Description
Very cool project. I would really love to try jcode for a production project at my work, but the lacking safety system makes it hard for me to feel confident in trying. I can tell the agent to always ask for permission to execute bash commands, but that feels like a workaround.
Is the safety system that's specced out a priority?
Contributor 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.
Research direction
The issue names no files or tests and refers to a safety system that is only described as specced out. Start by locating that specification and the bash-command permission flow, then clarify the intended safeguards and acceptance criteria before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bash, rust
- Domain
- cli, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100