The multi-agent-notepad demo.sh fails because sandbox create rejects --upload together with a command.
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
Research direction
Start with examples/multi-agent-notepad/demo.sh, especially its run_sandbox calls, and reproduce the failure using the README steps or the parse-only command shown. Compare the script's invocation with the current sandbox create CLI behavior; done means bash examples/multi-agent-notepad/demo.sh starts both the worker and synthesis sandboxes successfully.
Written by the indexing model from the issue text.
Description
User Story
As an agent evaluator, I want the demo script to run on the current CLI so I can see it work.
Problem Statement
The script's run_sandbox calls openshell sandbox create with --upload and a trailing command in the same invocation, and the CLI rejects the combination, so no worker sandbox starts.
Impact / Why This Matters
The example does not run as shipped. Users need a workaround, but the workaround is not written down anywhere.
Acceptance Criteria
demo.sh starts its worker and synthesis sandboxes on the current CLI.
Reproduction Steps
- Follow the example's README with any image that has Codex, curl, bash and node.
- Run
bash examples/multi-agent-notepad/demo.sh.
Expected: the worker sandboxes start.
Observed, the text the CLI prints:
error: the argument '--upload <UPLOAD>' cannot be used with '[COMMAND]...'
Usage: openshell sandbox create --name <NAME> --upload <UPLOAD> --no-tty [-- <COMMAND>...]
The same error comes from a bare parse-only command, openshell sandbox create --name x --upload /tmp:/sandbox --no-tty -- true, which fails at argument parsing.
Environment
- OpenShell 0.1.2 (Homebrew)
- macOS 26.5.1, arm64
- Docker Desktop, Docker 29.6.1, Docker compute driver
- Local gateway under brew services
Logs
- Dominant language
- Rust
- Stars
- 8.7k
- Forks
- 1.3k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 344
Getting set up
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 NVIDIA/OpenShell
-
state:triage-needed
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
state:triage-needed
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
area:docs
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
state:triage-needed
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
NVIDIA/OpenShell#3400 · 1 comment ·
Maintainers usually reply within 1 day
-
area:cli state:validated
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
NVIDIA/OpenShell#2888 · 1 comment ·
Maintainers usually reply within 1 day
All issues in NVIDIA/OpenShell
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Automattic/harper#4503 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100