RStack’s sandbox model is simple: the orchestrator plans the work, then each builder/validator receives a bounded task packet instead of the whole project and whole catalog.
This matches current agent-platform trends: multi-agent orchestration, explicit handoffs, tool governance, typed output contracts, traceability, and cost-aware context selection.
The sandbox flow
1. Choose the smallest useful profile
For a specific user ask, edit .rstack/rstack.config.json to keep only the relevant domains.
Example: “Help me upgrade this Node API with tests and security review”:
2. Start and plan the run
From Pi or any host exposing the RStack tools:
tasks.json will now include:
- selected profile/workflow
- selected domains
- routing explanations
- specialists selected from the registry
- budget envelope per task
3. Builder packet expectations
Builders are allowed to change files, but only inside task scope.
Recommended builder tools:
Every builder must write:
Required fields:
Optional Contract v2 telemetry is accepted and should be used when possible:
4. Validator packet expectations
Validators should review only. They should not edit files or mutate project state.
Recommended validator tools:
Validator output:
Required fields:
5. How to install only the required agent packs today
Today, the npm package ships the complete catalog. For a scoped project, use a profile plus project-local plugin copies:
Do not copy random GitHub agent files directly into production RStack runs. Read open-source patterns, adapt the ideas, keep licenses intact, and validate the local agent frontmatter/contracts before enabling them.
6. Upgrade-agent prompt pattern
Use this pattern when the end user says “help me upgrade this application”:
Loopholes to watch
- If a host framework does not expose token usage,
actual_usd remains builder-reported or zero.
- Profiles currently guide routing and dashboard visibility; they do not shrink the npm tarball yet.
- Validators are read-only by convention/tool selection; a host that ignores tools can still violate it.
- Open-source agent patterns require license review before redistribution.
- Dashboard panels only show data that exists in
.rstack; empty panels mean missing contracts/events, not hidden state.