Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Add an Agent Canvas local and Cloud parallel-work use case

Closed
#627 0 comments 0 reactions 1 assignee View on GitHub

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

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OpenHands/docs

All issues in OpenHands/docs

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.