Launching today
Tiden
Intent verification for coding agents
107 followers
Intent verification for coding agents
107 followers
Tiden verifies your coding agents built what you actually asked for. Most checks run inside the session that wrote the code, so the tests agree with it by construction. Tiden keeps your intent as requirements that branch and merge like code, and checks every change against that record. The verdict comes from tests run in your environment; no model grades the diff. You decide what merges, and production errors trace back to the release. Works beside Claude Code, Cursor, Codex and Copilot.
Keeping requirements updated alongside code changes sounds useful. It could help teams catch things that get missed development.
@aarav_pittman Yes, living functional specification of product behaviour has been maintenance challenge and Tiden solves that by making sure product spec is maintained same as a codebase automatically. This ensures tribal knowledge is not lost when someone leaves and there is alignment for different stakeholders by creating cross functional visibility.
No model grading the diff is the right call. I built an eval gate where only deterministic assertions could fail a build and the model-judged ones only reported. That split is what kept people trusting it. How do you handle a requirement that can't be written as a test, like "this should feel fast"?