Give your findings a page.

Keep the source. Build the page.

The original source stays in place while its values enter the core and a page emerges.

Open the evidence

This is a native figure built from the data below. Open it, inspect the values, then return to the page.

Source: Five UTC checkpoints from the fictional OrbitDesk incident. Example checkout failure rates, not Report performance metrics. · July 18, 2026

::::chart{type="line" title="Failed checkout attempts" description="Fictional OrbitDesk checkout failure rates at five UTC checkpoints." x-label="UTC checkpoint" y-label="Failed attempts, percent"}
:::series{label="Failure rate"}
::point{label="09:35" value="0.6"}
::point{label="09:50" value="8.7"}
::point{label="10:05" value="18.4"}
::point{label="10:20" value="7.2"}
::point{label="10:35" value="0.8"}
:::
::::

Tables, diagrams and local media use the same theme. The original Markdown remains the source for the next revision.

Put the question beside the passage

Select this sentence and choose Create note: every decision should make its supporting evidence possible to check.

Continue the thread, resolve the question, then export review.json when you want to return the discussion to the author. Feedback is not sent automatically. This built page stores local notes; it does not connect to Codex.

Revise with the conversation already doing the work

For a living document, run the local reader from the Codex conversation writing that source:

npx --yes agentic-report@0.21.1 serve ./my-page --human

Open the printed localhost address. Select a passage and choose Ask agent. The reply streams into the chat; source edits rebuild the page and highlight what changed. By default this connects to the current loaded, writable Codex conversation through its compatible local control endpoint.

serve is an opt-in, single-user local reader. It does not publish the conversation as a hosted service. Live discussion controls currently use English. A separate agent requires an explicit choice.

Follow a real task through the page

The organizations and evidence in these maintained examples are fictional. Their page layouts and interactions are actual package output.

The capability tour pairs working techniques with Markdown. The visual catalogue shows complete compositions.

Give your agent the material

Install the skill with the command at the top, then give your agent the real notes and evidence.

npx --yes agentic-report@0.21.1 init ./my-page --starter document --json
npx --yes agentic-report@0.21.1 build ./my-page --output ./my-page.html --json

The source contract describes the authoring boundary. The agent guide explains the page-making workflow.

Keep the source within reach

Human guide · Agent quickstart source · Exact skill · Landing starter source · Public route manifest · Release identity

The ordinary source format keeps remote fetching, raw HTML and implicit code execution outside its boundary. Declared extensions carry their own trust contract. Hosted collaboration, PDF export, pagination and disabled-JavaScript parity are outside the product.