Skip to main content

Integrations overview

Tiden connects to the coding agents, code hosts, trackers, test runners, and runtimes your team already uses. Each line below links to its setup page where one exists.

Coding agents​

tiden setup detects the agents on your machine and wires each one. See Set up intent capture.

  • Claude Code and Codex: Tiden skills plus intent-capture hooks.
  • Cursor, GitHub Copilot CLI, and Gemini CLI: session capture through hooks.
  • Any other agent: capture through a git post-commit hook.
  • Any MCP-capable agent: Tiden tools through the MCP server.

Code hosts​

Trackers and docs​

Each one is a read-only import: Tiden drafts specs on a branch for you to review and never writes back. Set up Jira, Linear, and Azure DevOps from the Agents page.

  • Jira: import a project’s issues, optionally filtered by JQL.
  • Linear: import a project’s issues.
  • Notion: import pages and databases. See Notion.
  • Azure DevOps: import a project’s Boards work items.

Test reporters​

Report test runs to Tiden from your existing suite. Your product’s setup plan in Tiden has the install snippet for each.

  • Playwright, Vitest, and Jest: npm reporter packages.
  • PHPUnit: a Composer reporter package.
  • Go: run go test through tiden run exec.
  • Swift: the tiden-swift reporter.
  • JUnit XML: upload any JUnit XML report with tiden run report.

GitHub merge queue​

A GitHub merge queue runs your CI on temporary branches named gh-readonly-queue/<base>/pr-<number>-<sha>. Tiden never creates a Tiden branch for them. It routes a queue run by the pull request number in the name:

  • Pull request linked to an open Tiden branch: when the pull request was linked with tiden intent link-pr <pr-url>, test results and test and spec writes from the queue run go to that Tiden branch.
  • No linked pull request: test and spec writes that name the queue branch use main. Unlike a run with no branch name, the run does not update the tests on main or on any other branch. Tiden keeps the run and shows that step as skipped, with the reason.

tiden run exec and tiden run create also send the repository when the origin remote is on github.com, so pull request numbers from other repositories of the same product do not collide. A GitHub Enterprise Server remote sends no repository. The JavaScript reporters do not send the repository: in a product with more than one repository, Tiden does not route their queue runs to a pull request's branch. It uses main and does not update the tests from the run.

To report queue runs, add the merge_group trigger to the workflow that reports to Tiden:

on:
  pull_request:
  merge_group:

The CLI detects the queue branch by itself when the base branch name has only lowercase letters, digits, /, _ and -. For another base, such as release/1.2, pass --branch "$GITHUB_REF_NAME" to tiden run exec or tiden run create. For the JavaScript reporters, set TIDEN_BRANCH to ${{ github.head_ref || github.ref_name }}; Tiden recognises the queue branch name. With TIDEN_BRANCH unset, the run has no branch name and uses main.

Error-tracking SDKs​

Send runtime errors to a product’s Issues page. See the Telemetry SDK overview.