Sandbox to Sandbox Communications
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 8.7k
- Forks
- 1.3k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 253
Description
Sandbox-to-Sandbox Communications enables controlled communication between OpenShell sandboxes. This supports multi-agent workflows where one sandbox runs an agent and another hosts a tool, service, model, database, or ephemeral resource.
This supports patterns such as:
- Sandbox A with long running agent running tool on Sandbox B
- Sandboxes being used to deploy ephemeral or long-running resources (such as local LLMs)
The goal is to make cross-sandbox communication explicit, policy-controlled, observable, and ergonomic, without requiring direct unmanaged reachability between sandbox environments.
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
No files, tests, or entry points are named in the issue. Start by mapping how OpenShell sandboxes are isolated and how policy, observability, and network access are currently handled. Define the supported cross-sandbox communication patterns and what explicit, policy-controlled, observable, and ergonomic behavior would count as done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- distributed-systems, networking, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100