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:
parent
2526dd458d
commit
7438fd1065
53 changed files with 1827 additions and 170 deletions
|
|
@ -21,7 +21,7 @@ Read these before larger changes:
|
|||
|
||||
```bash
|
||||
npm ci # once: installs jsdom for the tests
|
||||
npm run dev # play while developing: http://localhost:8080, reloads on save
|
||||
npm run dev # play while developing: http://localhost:8080, reloads on save (--host to share)
|
||||
npm test # node:test + jsdom, every tests/*.test.js, must stay green
|
||||
node scripts/i18n-check.js # must report "0 missing, 0 unused, 0 broken" (and sorted dictionaries)
|
||||
node scripts/i18n-add.js FILE.json # add/change/remove translations (see `add-strings`)
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue