PRODUCT DESIGN / PUBLIC DOCUMENTATION
What this case establishes
This is a product-design case based on public project documentation. Repository visibility is not proof of secure deployment, maintained compatibility, adoption or revenue. Roseram did not install or benchmark this project; the proposed evaluation is not a reported result.
Primary material reviewed 2026-10-12. Analysis and proposed evaluation by Roseram Editorial.- 01Explicit backend authority
- 02Separated project workspace
- 03Reviewed agent actions
OpenHands: the documented workflow
At the review date, the OpenHands repository describes Agent Canvas as a self-hosted control center for coding agents and automations, with local, remote and cloud backends. Its documentation explicitly warns that a without-sandbox agent server has full access to the host filesystem. This case is documentation analysis, not a deployed security assessment.
The mechanism worth examining
A common frontend can route conversations to different agent backends, but the interface does not determine the actual permission boundary. A container, a remote host and a direct local process have different mounts, credentials and persistence. Workspaces sharing a directory can still conflict even when their conversations appear separate. The execution environment must be understood before enabling a write-capable agent.
The implementation decision
Start with a disposable repository and a documented isolated backend. Inspect mounted paths, network access and available credentials. Give each concurrent editing task a separate directory or worktree. Keep external publications and messages behind explicit authorization rather than treating a running automation as permission for every tool action.
Where the workflow can fail
A broad project mount can expose unrelated source or secrets. Two agents can modify the same file while each assumes its own baseline. A remote backend can retain state longer than expected. Test with harmless fixture directories and verify what survives restart. A frontend’s project name is not evidence that the backend sees only that project.
A practical evaluation, designed for this use case
Ask the agent to complete one bounded task and inspect changed files, runtime actions and persistence. Confirm that an outside fixture is inaccessible under the chosen design. Exercise interruption and recovery without external side effects. Measure accepted changes and review effort; a continuously available server is not evidence of continuously correct work.
Primary sources
Figures and product details above are dated and attributed; they are not current guarantees.
- OpenHands: official project documentation ↗Documented product features and maintenance status. Proposed evaluations below are original Roseram analysis, not measured customer results.
The decision matrix
Original evaluation criteria for this workflow. These are questions to test, not results measured by Roseram.
| Decision | Evidence to collect | Stop or revise when |
|---|---|---|
| Authority | Backend permissions and mounts known | The frontend is mistaken for isolation |
| Concurrency | Separate working directories used | Agents overwrite a shared baseline |
| Persistence | Restart state inspected | Unexpected files or credentials remain |
YOUR EVALUATION / NOT A REPORTED RESULT
A small pilot you can inspect
Use these steps as a planning checklist. Checking a box records your progress in this view; it does not run or validate an experiment.
Questions this case answers
Is the local without-sandbox option isolated?
The project warns that it gives the agent server full host-filesystem access.
Do separate conversations prevent edit conflicts?
Not if they share the same underlying working directory.
Tools & capabilities referenced
Operators studying this story often evaluate adjacent AI products. Explore Roseram guides where available:
PRACTICAL NEXT STEPS
Take the evidence into your own project.
Calculate the whole project cost
Compare subscriptions, usage, launch work and renewals.
Test an existing-project workflow
Check import, source loading, preview and publication.
Verify the output you buy
Require evidence tied to a real customer task.
Wiki brief
OpenHands is examined here for agent workspaces and execution boundaries. The article answers “What should a team inspect before running coding agents across workspaces?” using linked primary material and original evaluation design. It is not a customer testimonial for Roseram or an endorsement by OpenHands.
Operator takeaways
- Inspect the backend.
- Separate concurrent edits.
- Verify persisted state.
Related case studies
Plan → build → review with routed models and transparent usage.