Visibility
Use visibility controls to keep human-readable docs and agent-only context separate without duplicating pages.
Visibility is a simple audience gate. Human-visible content renders on the web page and is excluded from the Markdown export. Agent-only content is hidden on the web page and included in the .md export. Use it sparingly: hidden context should support the page, not replace clear human documentation.
Example
This sentence appears in the public docs.
<Visibility for="humans">
This sentence appears in the public docs.
</Visibility>
<Visibility for="agents">
This instruction appears in the Markdown export for agents but does not render for human readers.
</Visibility>Open the Markdown version of this page to verify the audience flip: the human sentence is omitted and the agent instruction is present.
Agent-only implementation notes
Use agent-only visibility for source-of-truth reminders, verification hints, or migration context that would distract a human reader but help an agent update the page correctly.
Server-side API examples should keep bearer credentials out of browser code.
Properties
forhumans | agentsrequiredAudience for the wrapped content. humans renders on the web UI and is removed from .md output. agents is hidden on the web UI and kept in .md output.
Plandalf extensions
modevisible | hidden | human | agentdefault: visibleCompatibility mode. visible and human render on the web UI. hidden and agent are omitted from the human page.
class | classNamestringOptional class names applied to the rendered wrapper.
Authoring rules
- Keep public docs understandable without agent-only blocks.
- Put source-verification notes in
for="agents"only when they help future docs edits. - Do not use visibility to hide warnings, security constraints, or unsupported feature caveats from humans.
- Prefer
Viewwhen the reader should choose between alternatives.