openwiki

Guide · Codex publishing

Publish Codex work as a reader-ready link

Codex is useful for producing decisions and artifacts inside a working session, but the recipient usually needs the result rather than every prompt, command, discarded idea, and repository detail that produced it.

Updated August 3, 2026Practical guide

Define the handoff before generating it

  1. Name the reader and the decision or task.
  2. List the evidence that can be disclosed.
  3. Separate confirmed results from proposals and unknowns.
  4. Choose whether the recipient only reads, gives feedback, or must approve.

Build the artifact inside the Codex workflow

ow a2ui draft init ./artifact --title "Migration recommendation" --description "Decision, evidence, and rollback plan" --language en
# Add the supported typed sections and visual nodes.
ow a2ui draft check ./artifact
ow a2ui draft build ./artifact
ow a2ui digest ./artifact/document.mdw

Publish the right kind of handoff

# Read-only publication
ow publish ./artifact/document.mdw --no-open

# Blocking decision
ow publish ./artifact/document.mdw --review --no-open --timeout 900

Inspect the real rendered page

Open the returned URL and verify the layout, evidence, links, and access state in a real browser before sending it. A successful CLI response proves delivery, not complete reader acceptance.

FAQ

Frequently asked questions

Does the OpenWiki link expose my Codex conversation?

No. It exposes the separate typed document you chose to publish, not the underlying Codex session.

Can Codex read the reviewer’s decision back?

Yes. When published with --review, the CLI waits for a structured approve, request-changes, reject, timeout, or error result.

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.

Choose HostedSign in