Tiden

Tiden is a product of Qase, Inc., from the team behind the Qase testing platform. It captures what a coding agent was asked to do, maps product behavior into specs, and checks each change and release against tests that prove those specs. It works alongside agents such as Claude Code, Cursor, Copilot, Codex and Gemini CLI.

What It Is

Tiden is an intent verification layer for AI-generated code. Instead of reviewing only the diff, it records the request at the start of an agent session as a spec change, then checks whether tests prove each promised behavior. Tiden says it runs beside code review tools rather than replacing reviewers.

How the workflow runs

• Map: After connecting GitHub or GitLab, Tiden reads code and tickets from Jira, Linear or Notion, drafts specs for review, and marks specs that no test proves. Existing specs or test suites can be imported.
• Session: An agent starts an intent through the CLI, and a close gate refuses to end the session while a promised spec has no test. The agent then writes the missing test.
• Spec upkeep: Tiden drafts spec updates on every merge, including merges that skipped Tiden.
• Review: Each branch shows what changed and which tests prove it, with options to merge, ask for a test, or accept the risk.
• Release: Each release gets a verdict with coverage and component results. Production errors link back to the release and the specs they touch.

Enterprise controls

The enterprise page describes an audit trail of what each change was for, what checked it, and who signed off. It lists SAML single sign-on, SCIM 2.0 provisioning, required two-factor or passkeys, and Owner, Admin and Member roles. Activity logs can be streamed over HTTPS or to Splunk. Tiden keeps file paths, line ranges, commit SHAs and short excerpts rather than whole repositories, and agent runs use the customer's own LLM keys. Spec drafting at setup uses Anthropic or OpenAI.