Docs

Agent terminal

Insert the stock agent-fetch block on a page.

Open Markdown

Opt-in. Enable it in build.rs before use.

Lowers to a fixed text block illustrating how an agent consumes a Proa docs page: fetch the page, receive server-rendered HTML, extract the content with no client JavaScript.

content/quickstart.mdx
<AgentTerminal />

The tag takes no attributes and is self-closing. Its content is fixed; it is a shorthand for the agent-fetch illustration, not a container for your own transcript. It emits:

Agent fetches page -> receives server-rendered HTML -> extracts content without client JavaScript

Enabling

The MdxConfig::proa() preset enables this along with the other opt-in components. To turn on just this one:

build.rs
use proa_docs_build::{Config, MarkdownPipeline, MdxConfig};

let markdown = MarkdownPipeline::default().mdx(MdxConfig::new().agent_terminal(true));
let config = Config::new().source(source.markdown(markdown));

Like Cards and Files, it is off by default. Left off, the tag is not lowered, and the Markdown renderer drops it like any other block-level raw HTML.

When to reach for it

The block earns its place where you are making the agent-readability point itself: a quickstart or an agents page, next to the claim that a Proa page needs no client JavaScript to be read. For an actual command session, use a plain bash code block with a copy button: readers copy commands far more often than they watch them.

Code block · Demo · Quickstart

Search

Type at least 2 characters