Guide
Writing code together
Let your agent work in the example you can see
Ask your agent to change a data app or repair a program while you watch the same source, results and pictures. The page lends its editor and compiler to the agent, so every edit and run shows up in your tab.
1. Connect the tab
If your agent's browser supports WebMCP site tools, turn them on for this page and keep the tab open. Setup for each host.
Connect an ordinary browser through the local relay
Add this to your agent's MCP settings (Node 20 or newer), then open the example with ?webmcp=1 in its URL. The page and the relay must be on the same computer.
{
"mcpServers": {
"yichus-browser": {
"command": "npx",
"args": ["-y", "@yichus/mcp@0.1.4"]
}
}
}
2. Give it a concrete change
Every example's source drawer has a Work with your agent prompt. For the event-budget tutorial, try:
Call yichus_example_guide, then read exampleId "event_budget". Add a $50 booking fee to the cost calculation. Use the source revision you read when updating and running it. Check the preview: the starting balance should be $150. Open Why beside the balance and check that it includes the fee. Tell me what you changed and tested.
Edits stay in that tab, so ask your agent to save a copy before you leave.
3. Check the result together
Your agent can read what you see, run the example, open Why, compare a picture before and after its edit, and save a copy you can run. Ask it what it tested and what the result does not cover.
Other places to work
- Data app editor
- API workbench
- Explorer playground and the state-machine spec demo
- The game and the other demos, whose sources your agent can read
Compilation happens in your browser. Source and results reach your agent only through your browser or the local relay.
Make a data app → · Repair a program →
Ask your agent about anything here; it has the detail.
Where this fits
What this is about: How the pieces fit