FAQ

Is Tiden only a test management system?

No. Test management is one part of Tiden. The product also manages specs, branches, agent-driven automation, runtime issues, releases, environments, traceability, and quality gates.

What is the difference between a workspace and a product?

A workspace groups products and workspace-level credentials. A product is the quality repository for one application or service.

Why does Tiden have branches?

Branches let you review proposed changes before they become product truth. They are especially useful for AI-generated specs and tests.

Can agents write directly to main?

No. Agents produce branches. A person reviews and merges the branches that agent runs and imports create. An intent branch from a coding-agent session merges by itself about 24 hours after the last pull request of that work merges. A hold, the product setting, and a manual merge keep that under your control. See Automatic merge of intent branches.

Are API tokens the same as DSN keys?

No. API tokens call the public REST API. DSN keys only send error events to a product ingest endpoint.

Where do I create an API token?

For your own machine, run tiden setup: it creates an account token and writes it to ~/.tiden/config.json. You can also create an account token in Settings > API tokens. For CI, create a product token in Product settings > API tokens: it belongs to the product and keeps working when you leave. A workspace owner or admin creates product tokens. A token you create in settings is shown once; store it in a secret manager. See API authentication.

Where did my publish-only token go?

It moved to Product settings > API tokens of its product. The value did not change, so CI keeps working without a new secret.

Why do source map uploads need an API token?

Source maps contain source code and are uploaded from CI. The upload API uses a real API token, while runtime events use only a DSN key.

What release value should I use?

Use one stable string across CI, telemetry SDK initialization, source map upload, and tiden release create. For example: my-app@1.2.3.

What if a release appears in staging and production?

Create separate release records by version plus environment. The same version can exist in multiple environments.

Can I call every web API endpoint with an API token?

No. API tokens are intentionally limited to the public API package. Web-only admin endpoints require a browser session.

What should I document in spec sources?

Attach source links or file locations that explain why the spec exists: customer notes, requirements documents, repository files, agent artifacts, or design documents.