v0.2.0

npm install -g pi-durable-bot

What is new

• The bot uses its computer's screen like a person. It sees the screen with screenshots and uses the mouse and keyboard: the real browser and apps, with the logins people made there. People can watch and take over at any time. On its first wake it checks that it can use the screen and walks you through any permission the system asks for, such as Screen Recording and Accessibility on a Mac. On a server with no desktop it works without a screen, and asks you before it sets one up. No browser automation tool is installed; the bot finds, installs or writes what it needs.
• pots trace shows what the gateway did for a wake, from the events to the messages sent, with the agent's run and each model request. Every span is kept in the bot's SQLite file for 7 days. With OTEL_EXPORTER_OTLP_ENDPOINT set, the same spans also go to any OpenTelemetry tool.
• The gateway core runs on Effect 4: inbox, waker, outbox, timers and the channel adapters' life, with typed errors and schemas for events and bot.json.

Fixed

• A crash right after a wake no longer gives the bot the same events twice.
• Stopping or restarting the service no longer loses a reply the bot is sending; its work goes on after the next start.
• A failed timer wake waits 30 seconds before the next try, instead of trying again without end.
• A gateway that fails to start releases everything it started.

Tested

55 tests that start a real gateway and check only what is visible from outside, TestClock and fast-check tests for the gateway core, and TLA+ models of the outbox, the inbox with the waker, and the debounce, checked with TLC. See docs/development.md.

This release is published from GitHub Actions with npm trusted publishing and provenance.