Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Docs: Child Conversations incorrectly implies the child's result is returned to the parent

オープン 初心者向け
  • 何か問題がありますか？
#925 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
2/5
見積もり時間
1〜3時間
初心者へのやさしさ
82/100
issue の種類
ドキュメント
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
markdown
領域
documentation

調査の方向性

openhands/usage/agent-canvas/conversations.mdx の Child Conversations セクションを読み、記載されている launch_child_conversation ツールの説明と表現を比較してください。起動確認と子の最終応答を区別し、子は親をブロックせずに独立して実行されることを説明するよう、セクションを更新してください。最終応答は自動的に届けられるのではなく、子の会話を開くか問い合わせて読む必要があることが明確に記されていれば完了です。

索引モデルが issue の本文から書いたものです。

説明

Summary

The Child Conversations section of openhands/usage/agent-canvas/conversations.mdx states that a child conversation's result is returned to the parent conversation. In the current product this is not accurate: children launched via the launch_child_conversation tool run independently, and the child's final response is never delivered to the parent automatically. The parent only receives a launch acknowledgement (the child's id/URL/initial status), and a user has to open the child conversation to read its output.

This wording has already caused user confusion in the community (a user read it as "the child's answer is pushed back to the parent" and spent time chasing a handoff that does not exist).

Current text

openhands/usage/agent-canvas/conversations.mdx (Child Conversations section):

The child remains linked to its parent, and its result is returned to the parent conversation. Agent Canvas validates the launch inputs before creating the child conversation.

Why it is confusing

Two separate things are being conflated:

  1. The launch result / link is returned. When the agent calls launch_child_conversation, the frontend posts a machine-generated follow-up message beginning with [child-conversation] back into the parent, carrying the child's conversation id, URL, target and initial status (or corrective guidance on a malformed call). This happens at launch time — not when the child finishes.
  2. The child's final answer is NOT returned. The child runs on its own ("It does not block you, you do not see its output", per the tool description). Its final response is not forwarded to the parent on completion. The parent_conversation_id / sub_conversation_ids relationship is persisted server-side but is used for discovery, recovery and deletion bookkeeping, not for message delivery.

The phrase "its result is returned to the parent conversation" reads naturally as (2), when what actually happens is only (1).

Contrast this with the SDK Task tool (software-agent-sdk), where delegation is blocking and the sub-agent's final response genuinely is returned in the tool observation. Because the docs use the same word "result" for both, readers reasonably assume the Canvas child behaves the same way — it does not.

Acceptance criteria

  • The Child Conversations section no longer states or implies that a child's final response/output is automatically returned to the parent.
  • The section distinguishes the two events described above:
    • the automatic launch acknowledgement posted back into the parent (child id/URL/initial status, the [child-conversation] follow-up), and
    • the child's final result, which is not auto-delivered and requires the parent (or user) to open/query the child conversation.
  • The section explicitly states that a child launched this way is non-blocking and independent — the parent does not wait for it and does not automatically see its output (consistent with the launch_child_conversation tool description in OpenHands/OpenHands: "The child runs on its own. It does not block you, you do not see its output...").
  • If a contrast with the SDK Task tool is added, it correctly notes that Task tool delegation is blocking and does return the sub-agent's final response, so the two are not confused.
  • Wording is consistent with the child-conversation behavior implemented in OpenHands/OpenHands (src/api/launch-child-conversation-client-tool.ts, src/services/child-conversation-launch.ts) and OpenHands/software-agent-sdk (agent-server child linking, openhands-tools/openhands/tools/task).

References

  • openhands/usage/agent-canvas/conversations.mdx — Child Conversations section (line 12)
  • OpenHands/OpenHands src/api/launch-child-conversation-client-tool.ts — tool description and "What comes back" text
  • OpenHands/OpenHands src/services/child-conversation-launch.ts — reportLaunchResult (launch receipt only)
  • OpenHands/software-agent-sdk openhands-agent-server/openhands/agent_server/models.py — parent_conversation_id / sub_conversation_ids (link, not delivery)
  • Community thread: user reported with Agent Canvas 1.25 that the child's response did not return to the parent, citing this documentation line.

This issue was drafted by an AI agent (OpenHands) on behalf of a community member.

主要言語
MDX
スター
16
フォーク
63
平均マージ
2日 1時間
マージ済み PR（30日）
63

環境構築

  • Dockerfile・Docker Compose ファイルなし
  • プルリクエストのテンプレートあり
  • コントリビューションガイドなし

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

OpenHands/docs のほかの issue

OpenHands/docs の issue をすべて見る

似ている issue

Documentation の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。