TinTinWorkflows
GitHubSign in

Have an AI tester sign up for your product as a stranger

Tin signs up for your product with a Tin-owned test account, verifies the email, works through to first activation and reports every break along the way.

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. 01Opens your product URL in a real browser as a new visitor.
  2. 02Signs up with a Tin-owned identity and verifies the email.
  3. 03Continues until first activation, noting friction and failures.
  4. 04Saves a dated report with what broke and where.
ask your agent

Have Tin walk our signup as a new user and tell me everything that broke.

workflow keyqa.signup_walkthrough
required inputs
product_url
optional inputs
notes
outputreports/qa/signup/{host}/{started_at}.md
needsA public signup. No credentials from you.
guardrailUses a Tin-owned test account, never a customer's.

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

When the report names a break, your agent can open the file that caused it. That closes the loop in one conversation.

All workflows →

Questions

Is this a replacement for an end-to-end test suite?

No. It is an exploratory pass by an AI tester who has never seen your product, which is what your test suite cannot be.

Does it work with email verification?

Yes. The test identity has a working mailbox and the workflow completes verification.

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