1
Our loop is always the same: A UI flow breaks → backend says “spec is outdated” → someone spends 30–60 minutes in Devtools figuring out what the server actually returned → then we argue whether backend/spec/frontend should change.
I want drift to be caught during normal dev/staging usage while clicking through the app. Real traffic, real accounts, real data. Not just CI tests validating what we already expect.
If your team handles this well, what works?
Do you do runtime validation (client/proxy) that logs schema mismatches with enough context to fix fast (operationId, request id, response body/diff)? Gateway enforcement? Contract tests that actually reflect reality? Something else boring but reliable?
Also, what’s the slow part for you when drift happens, mapping to the right operation, getting a repro across envs/accounts, or turning Devtools into a clean ticket/PR?
You type "every Monday at 9am, query Postgres and email the CSV to team@" and it compiles that to a DETERMINISTIC CONFIG workflow spec, then executes it locally with a daemon.
No cloud dependency, no GUI. Runs over SSH, in containers, wherever you have a terminal. Credentials stay on your machine (AES-256). Uses your own OpenAI/Anthropic key for the NL planning.
Core is working (file ops, HTTP, email, cron, file watchers). Looking for early users and collaborators to help build out integrations.
Is this something you'd actually use? What integrations would matter most to you?