Katia Bulatova
bb036f92e8
The agent ships Chat and Investigate here; Watch — telling the user later — follows in its own PR. The whole user-facing feature leaves: the watch card, chips, wake banner and toast, the unread-wake badge and its poll, the watch routes, checks, batches and sweeps, the watch alert email and its channel type, and the watchMaintenance cron. The agent no longer promises it either: schedule_watch and the alert tools are gone from the tool set, and the Watches section is out of the system prompt. Leaving that text in would have had the agent refuse to poll for something it could no longer offer. The datastore's watch tables stay. The migrations ship in this PR, so the drizzle schema that describes them has to ship too — a schema that no longer matched the migrated tables would make the next generate emit a drop.
Trigger webapp - powered by Remix
To start, run with pnpm run dev --filter webapp
Build the docker image locally:
pnpm run docker:build:webapp
docker run -it triggerdotdev-webapp sh