feature: Better terminology around "sandbox"
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- typescript
- Domain
- cli
Research direction
Start by reading the CLI entry points for mocactl and the existing mocactl sbx and mocactl run command implementations. The issue describes confusion about sandbox terminology and proposes a mocactl claude command with settings support, but leaves the command behavior and scope open. Done would require a decided command design that lets users start Claude without editing their settings.
Written by the indexing model from the issue text.
Description
Feature Description
mocactl has two sandbox concepts:
- Chat-session sandbox
- mocactl (the TUI), run, spawn
- sbx sandbox
- mocactl sbx … commands
My previous experience is using the Claude Android app. In that app, when I use the Code tab, it associates a VM with each session, and this VM can check out multiple repos an install packages.
When I created an sbx "sandbox" I expected Claude runs on that sandbox, in the same way the Code sessions I create with the Android app run Claude. That isn't what happens -- sbx sandboxes contain files, and sometimes can run Python programs, but don't have network access to install CLIs such as Go.
It confused me that I could start chatting about my code, and mocactl could fetch the code, but then couldn't edit the code or get it back to my laptop. The Android Claude app has a "Chats" section for chatting and a "Code" session for persistent VMs with installed tools, and neither matched what was happening.
Because I didn't understand that mocactl 's workflow is to patch Claude to run locally against an sbx sandbox I was confused about tool restriction. I did mocactl sbx up --name ecs-for-cortex --no-agent-config because I didn't want to patch my Claude.
Proposed Solution
I'd like to run Claude or a mocactl session with a single command that doesn't break anything.
I shouldn't have to understand and edit my Claude settings to remove tools. I have many different Claude settings directories, it is too hard to manage! Better would be a way to use mocactl run claude with --settings to disable local tools.
e.g. mocactl claude -- -- resume my-work
Want to contribute?
- I would like to work on this issue.
Additional Context
No response
- Dominant language
- TypeScript
- Stars
- 5
- Forks
- 11
- Avg merge
- 8h 58m
- Merged PRs (30d)
- 154
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
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
-
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
Similar issues
-
category::task code priority::normal
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
e0ipso/strikethroo#145 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
cocos/cocos-docs#3333 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
RevenueCat/react-native-purchases#2079 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
RevenueCat/purchases-hybrid-common#2039 ·
Maintainers usually reply within 1 day
-
agent-reported area/react bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day