docs: adopt a consistent convention for OpenHands Enterprise differences in the Agent Canvas docs
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 初心者へのやさしさ
- 48/100
- issue の種類
- ドキュメント
- 明瞭さ
- おおむね明確
- 活発さ
- 活発
- 技術スタック
- markdown
調査の方向性
Start with .agents/skills/docs-writing/SKILL.md and the ownership guidance in AGENTS.md, then verify each candidate passage against the source repositories before editing. Review the listed Agent Canvas pages, keeping the default behavior separate from backend-specific caveats and naming local, OpenHands Cloud, and self-hosted OpenHands Enterprise precisely. Done means the convention is documented, the selected passages meet the acceptance criteria, and mint broken-links passes.
索引モデルが issue の本文から書いたものです。
説明
Problem
The Agent Canvas docs describe behavior for three different backends (local, OpenHands Cloud, and self-hosted OpenHands Enterprise), but there is no convention for marking which sentences apply to which. Today the pages under openhands/usage/agent-canvas/ use about seven different shapes for the same kind of Enterprise caveat, and most of them don't tell the reader what the other backends do. A reader on a local backend can't tell whether a paragraph applies to them.
This surfaced while consolidating the v1.36.0-v1.39.0 release docs (#1124). The v1.38.0 draft overwrote the paragraph in agent-profiles.mdx that explained how profile selection works by default, leaving only the self-hosted Enterprise exception, and it pulled a universal rule ("you cannot switch profiles mid-conversation") into the Enterprise sentence so it read as Enterprise-only. That was fixed in f92e00ed on #1124, but nothing stops the next release draft from doing the same thing, because the rule isn't written down.
Shapes currently in use
| Shape | Example |
|---|---|
| Inline, condition first, states what other backends do | openhands/usage/agent-canvas/customize-and-settings.mdx:28 |
| Inline, Cloud and Enterprise lumped together | openhands/usage/agent-canvas/llm-profiles.mdx:150 |
## section |
openhands/usage/agent-canvas/overview.mdx:58 |
### subsection |
openhands/usage/agent-canvas/agent-profiles.mdx:63 |
<Note> |
openhands/usage/agent-canvas/first-time-setup.mdx:93, openhands/usage/agent-canvas/agent-profiles.mdx:11 |
<Tabs> |
openhands/usage/agent-canvas/automation-events.mdx:229 |
## on a sub-page |
openhands/usage/agent-canvas/prebuilt/github-pr-review.mdx:56 |
customize-and-settings.mdx:28 is the best existing model. It leads with the condition and closes with "Other deployments keep the in-app MCP Servers page." That closing clause is what the others are missing.
Proposed convention
Pick the shape by the size of the difference:
- A one-sentence caveat: inline text, condition first, and say what the other backends do.
- A control that only exists on Enterprise, or works substantially differently there: its own
###, titled<Feature> on OpenHands Enterprise. - Parallel instructions per deployment:
<Tabs>, asautomation-events.mdx:229already does. <Note>or<Warning>: only when the reader would otherwise get it wrong. The existing "Limit caveats and callouts" rule in.agents/skills/docs-writing/SKILL.mdstill applies.
Two rules regardless of shape:
- Document the default behavior first. An Enterprise caveat adds to the baseline explanation; it never replaces or absorbs it. Keep behavior that applies to every backend out of the Enterprise-specific text.
- Name the backend precisely. Distinguish self-hosted Enterprise from OpenHands Cloud from a local backend. "Enterprise" alone is ambiguous when Canvas talks to all three. Name the admin control that flips the behavior (for example
Enable Agent Profilesin the Admin Console) and link to the page underenterprise/that documents it.
Suggested work
- Add the convention to
.agents/skills/docs-writing/SKILL.mdas a new section, so agents editing these pages follow it. Consider a line inAGENTS.mdunder "Docs writing conventions" pointing at it. - Retrofit the inconsistent spots. Candidates, in rough priority order:
llm-profiles.mdx:150— lumps Cloud and Enterprise together; confirm whether the behavior really is identical on both, and say what local backends do.first-time-setup.mdx:93—<Note>whose Enterprise clause ("On Cloud and Enterprise environments no checklist will be shown") would read better inline.overview.mdx:58— "Enterprise License Warnings" as a top-level##in an otherwise backend-neutral overview page; consider whether it belongs here, underenterprise/, or as a###.agent-profiles.mdx:11—<Note>covering thedefaultprofile rules; check it against the convention.managing-automations.mdx:146— says "On a cloud backend"; verify that covers both Cloud and self-hosted Enterprise, and that local backends are addressed.prebuilt/github-pr-review.mdx:56— section title says "Enterprise" but the body says "self-hosted (OpenHands Enterprise)"; pick one phrasing.
- Leave
architecture.mdx,backends.mdx, and thebackend-setup/pages alone. Those compare deployments as their actual subject, so a table or dedicated section is correct there.
Acceptance criteria
- The convention is written down in
.agents/skills/docs-writing/SKILL.md. - Each retrofitted passage names the specific backend, states what the other backends do, and does not leave backend-neutral behavior inside an Enterprise-only paragraph.
mint broken-linkspasses.
Notes for whoever picks this up
Verify behavior against the source repos before rewording, rather than preserving the existing phrasing. Several of these passages describe capability-gated or admin-gated behavior, and the gate's effect on other backends is often the undocumented part. AGENTS.md lists which repository owns which behavior.
- 主要言語
- MDX
- スター
- 19
- フォーク
- 104
- 平均マージ
- 2日 12時間
- マージ済み PR(30日)
- 80
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートあり
- コントリビューションガイドなし
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
OpenHands/docs のほかの issue
-
docs: document FORGEJO_BASE_URL (self-hosted Forgejo host for the backend integration)対応中かも @remote-controlled-man が 18 日前に担当しました。 オープン
難易度 1/5 1時間未満 初心者へのやさしさ 85/100
メンテナーはふだん 1 日以内に返信
-
docs(sdk): custom-tools 'register_tool' example passes a factory function, which raises TypeErrorオープン
難易度 2/5 1〜3時間 初心者へのやさしさ 62/100
メンテナーはふだん 1 日以内に返信
-
難易度 1/5 1〜3時間 初心者へのやさしさ 83/100
メンテナーはふだん 1 日以内に返信
-
Docs: Child Conversations incorrectly implies the child's result is returned to the parent対応中かも @sahithib20 が 36 日前に担当しました。 オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 82/100
メンテナーはふだん 1 日以内に返信
-
enhancement
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100
OpenHands/docs#658 · コメント 2 件 ·
メンテナーはふだん 1 日以内に返信
似ている issue
-
[Docs] CONTRIBUTING points the Backend Remake milestone at a branch that does not exist対応中かも @franpts2 が今日担当しました。 オープンdocs
難易度 1/5 1時間未満 初心者へのやさしさ 90/100
メンテナーはふだん 3 日以内に返信
-
postgresql-rules / queue-rules: implicit KEY SHARE before a parent key update, and job self-overlapオープン
難易度 2/5 1〜3時間 初心者へのやさしさ 82/100
jonathanong/no-mistakes#3879 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 84/100
cloudflare/nimbus#423 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 70/100
NYCPlanning/data-engineering#2996 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 82/100
メンテナーはふだん 2 日以内に返信