Add an Agent Canvas local and Cloud parallel-work use case
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
This issue has not been assessed yet.
Description
I can
I can follow a public example to parallelize work locally or on OpenHands Cloud from Agent Canvas, track each child, recover from failure, and review results before integration.
Scope
Add a concrete parallel-work page to the existing examples/use-cases documentation structure and link it from the relevant overview/navigation. Document the public local implementation and only the existing Cloud API contract.
Acceptance criteria
- The local walkthrough launches at least two isolated child conversations from a parent using the typed Canvas action.
- The Cloud walkthrough launches at least two children using the same user-level flow and the existing Cloud API.
- Both walkthroughs show dependency-aware task briefs, child status tracking, direct child opening, and parent reload.
- A failure/recovery example demonstrates retry or relaunch without losing successful sibling work.
- The integration step includes an explicit human review gate and verification of combined results.
- The page explains isolation, concurrency limits, shared-state hazards, and when not to parallelize.
- Screenshots or equivalent live evidence match the released UI and skill behavior.
- The page is linked from the docs' examples/use-cases entry point and passes docs checks.
- No private-repository implementation or new Cloud API is presented as a prerequisite.
Dependencies
- OpenHands/software-agent-sdk#4751 — aggregate clients.
- OpenHands/agent-canvas#1987 — shared Cloud transport.
- OpenHands/software-agent-sdk#4119 — local relationships.
- OpenHands/OpenHands#15461 — typed launch.
- OpenHands/OpenHands#15460 — tracking and controls.
- neubig/workflow#9 — delegation skill and examples.
- Dominant language
- MDX
- Stars
- 14
- Forks
- 61
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 47
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No 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 OpenHands/docs
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Moonshot provider documentation references a deprecated model, setup fails per doc recommendationsOpen
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
OpenHands/docs#658 · 2 comments ·
Maintainers usually reply within 1 day
-
Document software factory setup through Agent Canvas UIPossibly taken @neubig claimed this 17 days ago. Openenhancement ready-for-dev
OpenHands/docs#796 · 1 assignee ·
Maintainers usually reply within 1 day
-
Document SDK-owned browser conversation event streamsPossibly taken @neubig claimed this 17 days ago. Open
OpenHands/docs#794 · 1 assignee ·
Maintainers usually reply within 1 day