Agent View is a workspace inside NIBWP: a browser tab showing real pages of your site, which a connected agent can open, read and drive. It exists because an agent editing content it cannot see is guessing, and because you should be able to watch.
Without it, an agent writes into the database and hopes. With it, the agent opens the page, reads what is actually on it with a selector for every element, changes something, and reads it back. You see each step as it happens.
Open NIBWP and go to Agent View. Connected agents can then open pages, read them, click, fill, edit blocks and audit accessibility, with a human approval prompt on anything that changes something.
Seeing beats guessing
Working in the workspace changes what an agent can do reliably:
- It reads the real page — Rendered output with a selector for every element, not a guess from the database.
- You watch it happen — Every tool call is listed in the workspace as it is made.
- Saves appear on screen — Any post saved while the workspace is open is brought up, whichever skill wrote it.
- Accessibility built in — Contrast, alt text, labels, headings and overflow can be audited directly.
- Block editing — It can insert, update and delete blocks in the editor the workspace has open.
- Approval on writes — Anything that changes something stops and waits for you, unless you turn that off.
What it exposes
Fourteen abilities drive the workspace. They travel down the same MCP endpoint as everything else and obey the same scopes:
| Ability | Type | What it does |
|---|---|---|
nibwp/visual-open | read | Open a page of this site in the workspace and return it once loaded. |
nibwp/visual-read | read | Return what is on the page, with a selector for every element. |
nibwp/visual-click | write | Click an element. Approval-gated, because a click can be a Delete button. |
nibwp/visual-fill | write | Fill a field. Approval-gated. |
nibwp/visual-viewport | read | Resize the viewport to check a layout at another width. |
nibwp/visual-audit | read | Check contrast, alt text, labels, heading order and overflow. |
nibwp/visual-console | read | Read the browser console, so a JavaScript error is visible rather than mysterious. |
nibwp/visual-blocks | read | List the blocks in the editor the workspace has open. |
nibwp/visual-block-insert | write | Insert a block into that editor. |
nibwp/visual-block-update | write | Change the attributes of one block. |
nibwp/visual-block-delete | manage | Delete a block. The manage scope, because it destroys something. |
nibwp/visual-block-schema | read | Read the real attribute schema for a block before writing to it. |
nibwp/visual-batch | write | Run several steps in one call: open, read, click, read again. |
nibwp/visual-tabs | read | List, focus, close or reload the workspace tabs. |
From hours to one prompt
Say what you want to see and the agent works in front of you:
Open the pricing page and check the contrast on the middle tier
nibwp/visual-open (run)
nibwp/visual-read (run)
nibwp/visual-audit (run)
✓ 3 tools · 2 contrast failures foundYou are watching the same page it is reading, so when it reports a problem you can look at it yourself.
What you can build
A few of the things the workspace is good for:
Design review
Have an agent walk a page at three widths and report what breaks.
Accessibility passes
Audit contrast and alt text on real rendered output, not on source.
Guided edits
Watch a change land and say stop before it goes further.
Debugging
Read the console to see the error the page is actually throwing.
How it stays safe
- Approval on by default — Anything that changes something waits for you. Reading never does.
- Same account only — The workspace only accepts commands from an agent signed in as the same WordPress user.
- Batches are not a loophole — A batch is judged by its steps, so it cannot smuggle a write past the prompt.
- Same scopes as everything — These are ordinary abilities. They obey your token and land in the audit log.
Getting started
- Open the workspace — In WordPress, go to NIBWP and open Agent View. It has to be open for any of this to work.
- Sign in as the same user — The agent connects as a WordPress user; the workspace must be open under that same account.
- Ask for something visual — Say show me, or in the workspace, and the agent will reach for these tools.
- Leave approval on — Turn it off only once you trust what you are watching.