Identify the artifact you actually have
- Raw HTML with custom layout or scripts
- Markdown plan in the repository
- Decision-ready specification
- Recurring report
- Candidate plan that requires approval
Do not force every artifact into one host
A raw HTML plan and a typed OpenWiki document make different promises. Preserve the original on an HTML-capable surface when exact rendering matters. Use OpenWiki when validation, stable identity, formal revisions, feedback, and Agent-readable decisions matter more.
Build a supported OpenWiki work product
ow a2ui draft init ./handoff --title "Implementation plan" --description "Scope, risks, and approval request" --language en
# Author through typed draft commands.
ow a2ui draft check ./handoff
ow a2ui draft build ./handoff
ow publish ./handoff/document.mdw --review --no-openKeep session and capability boundaries separate
Do not copy secrets or private repository context from the Claude Code session into the artifact. Share the view URL for reading and the review capability only with the intended approver.
FAQ
Frequently asked questions
Can I upload Claude Code’s HTML file to OpenWiki?
No. Raw HTML is not a supported Hosted input. Use an HTML artifact host or author a separate typed .mdw document.
Can I keep the same OpenWiki URL when Claude Code revises the plan?
Yes. Publish the rebuilt .mdw with --update and the existing document ID; use --review for a new candidate decision.
Use the real workflow
Publish what your agent creates.
Give every report, document, or plan its own reader-ready page. Comments, review decisions, and formal revisions can flow back from there.