Agent mode: an AI agent plays in the player's own tab, with the agent's clock or a running one

The MCP server gains a second session, --browser: the game in the player's tab, reached through the
agent relay npm run dev hosts at /agent (loopback unless --host; Host and Origin checked, no token).
The player turns it on in Settings → Agent API, a section only the development page has, and picks the
clock: a pace of 30 s to 5 min a day that nobody can pause, or the agent's own. Headless gets the
running clock too (--clock realtime --pace MS) and both get a wait tool.

All of it lives in src/agent/ (development page only). The game offers HOOKS, UI.clockLocked,
setSpeed() and runClock(dt), the frame's day block moved out unchanged, and nothing more: the page
players get grows by under 1 KB gzipped and runs exactly as before.
This commit is contained in:
Wolfgang Nagele 2026-11-03 15:30:04 -05:00
parent 2526dd458d
commit 7438fd1065
53 changed files with 1827 additions and 170 deletions

View file

@ -19,7 +19,8 @@
"page": "node scripts/lib/page.js",
"serve": "npm run build && npx --yes serve@14.2.4 _site",
"perf": "node scripts/perf-bench.js",
"mcp": "node scripts/mcp.js"
"mcp": "node scripts/mcp.js",
"mcp:browser": "node scripts/mcp.js --browser"
},
"engines": {
"node": ">=20"
@ -28,6 +29,7 @@
"@modelcontextprotocol/node": "2.1.2",
"@modelcontextprotocol/server": "2.4.0",
"jsdom": "24.1.3",
"playwright-core": "1.56.0"
"playwright-core": "1.56.0",
"ws": "8.22.0"
}
}