# Visibility
Use visibility controls to keep human-readable docs and agent-only context separate without duplicating pages.
Source: /docs/components/visibility
Last modified: 2026-06-20
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 instruction appears in the Markdown export for agents but does not render for human readers.

```mdx title="visibility-example.mdx"


This instruction appears in the Markdown export for agents but does not render for human readers.
```

Open the [Markdown version of this page](/docs/components/visibility.md) 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.


When updating this section, verify API credential behavior against `/Users/wavy/plandalf/api/routes/api.php` and related controllers before changing public claims.

## Properties


- `for` (humans | agents; required):
  Audience 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


- `mode` (visible | hidden | human | agent; default: visible):
  Compatibility mode. `visible` and `human` render on the web UI. `hidden` and `agent` are omitted from the human page.


- `class | className` (string):
  Optional 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 `View` when the reader should choose between alternatives.

## Related


  - [View](/docs/components/view): Switch between visible variants.
  - [Prompt](/docs/components/prompt): Author agent prompts.
  - [Disclosure](/docs/components/disclosure-views): Hide optional human detail.