TinTinWorkflows
GitHubSign in

A feature map from using the product, not reading about it

Tin reads your docs, signs in and uses the product with a Tin-owned account, reconciles what it saw with the code map, and writes the Feature map section of project memory with evidence on every feature.

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. 01Reads the docs you point it at.
  2. 02Signs in and uses the product in a real browser.
  3. 03Reconciles what it saw with the code map.
  4. 04Writes the Feature map with evidence per feature.
ask your agent

Have Tin map what our product actually does and flag anything the docs promise that it could not find.

workflow keyproduct.deep_dive
required inputs
product_url
optional inputs
docs_urlsdepthnotes
outputwiki/INDEX.md (Feature map section)
needsA reachable product. A code map is recommended.
guardrailTin-owned account only.

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

Differences between code, docs and the live product are where bugs and bad marketing come from. Your agent can act on each one.

All workflows →

Questions

What if the docs and the product disagree?

The map records what the product did, with evidence, and notes the disagreement.

Which workflows use the feature map?

The feature-by-feature audit reads it directly, and content workflows use project memory for accuracy.

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