TinTinWorkflows
GitHubSign in

AI QA testing that covers every feature you ship

Tin exercises every feature in your project's Feature map as a user, with a Tin-owned account, and reports what works, what is broken and what to improve. Every finding comes with reproducible evidence.

Find it on GitHub
codex mcp add tin --url https://app.tin.computer/mcp

What the workflow does

A Tin workflow is a repeatable job: declared inputs, a bounded run and a defined output. The steps below are what this one does, every time.

  1. 01Loads the Feature map from project memory.
  2. 02Uses each feature in a real browser as a user would.
  3. 03Records working, broken and improvable, with steps to reproduce.
  4. 04Saves a dated audit report.
ask your agent

Run Tin's product audit on the billing features and summarize what is broken.

workflow keyqa.product_audit
required inputs
product_url
optional inputs
scopedepthnotes
outputreports/qa/audit/{host}/{started_at}.md
needsA Feature map, from the feature map workflow.
guardrailTin-owned account only. It reports; it does not change your product.

What every workflow here comes with

Battle tested on real products

These are the workflows we run for real companies. Claw Messenger went from about $45 to $2,105 in monthly revenue in 124 days on them. Each one has declared inputs, bounded execution and tests, and anything public waits for your review.

See the case study →

Open source: read it, fork it, self-host it

Apache 2.0. Every workflow is a folder in the repository: the steps it runs, the data it reads and what it is allowed to do. Change it, or run the whole system on your own machine.

Open the repo →

Runs on the agent that already knows your product

The Feature map is built from your code and your live product, so the tester knows what should exist. Your agent then fixes what the audit finds.

All workflows →

Questions

How does the tester know what my features are?

From the Feature map in project memory, written by the feature map workflow and reconciled with the code map.

Can I limit the audit to one area?

Yes, with the scope input.

Is Tin really open source?

Yes. Tin is licensed under Apache 2.0 and the source is at github.com/tin-computer/tin. You can read every workflow, change it, and self-host the whole system.

Which coding agents can run Tin workflows?

Any agent that speaks MCP, including Claude Code, Codex and Cursor. There is also an API, and the same projects run in the browser at app.tin.computer.

Why run marketing from a coding agent?

Because it already knows your product. It has the repository open, so it fills workflow inputs accurately, reviews output against what the product really does, and can act on the results in the same session.

Add Tin to your coding agent

Run this once in your terminal. It connects Tin to your agent and opens the sign-in. Then ask your agent to grow your project.

Find it on GitHub
codex mcp add tin --url https://app.tin.computer/mcp