TinTinWorkflows
GitHubSign in

Give developers something they can clone and run

Developers try a product by running an example. Tin finds the SDK, API, webhook or embed a developer calls first in your repository, picks the framework your users build with, and opens a pull request with a small runnable starter and a five-minute README.

Try in browser →
codex mcp add tin --url https://app.tin.computer/mcp
Framework starter
growth.framework_starter
outputUnmerged GitHub PR and reports/framework-starter/{run_id}/RESULT.md
guardrailSays no when there is nothing a developer integrates, and never repeats a starter. Never merges, deploys, publishes a package or creates a repository.
needsThe GitHub integration with write access to the product's repository. A code map is recommended.
required inputsnone
optional inputsframework, use_case
sourcegithub.com/tin-computer/tin →

What the workflow does.The same steps, every run.

A Tin workflow is a repeatable job: declared inputs, a bounded run and a defined output.

  1. 01Reads the repository for the first thing a developer integrates.
  2. 02Picks the framework your users build with, skipping any that already have a starter.
  3. 03Writes a small runnable starter under examples/ with a README that takes five minutes.
  4. 04Opens an unmerged pull request and saves a result receipt.
ask your agent

Have Tin add a Next.js starter for our SDK under examples/ as a PR.

What every workflowcomes 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

Your agent can run the starter against the real SDK before you review it, which is the check that matters most.

All workflows →

Runs well with.Workflows that feed this one, or follow it.

Code mapproduct.code_mapFeature mapproduct.deep_divePublic articlecontent.public_article

Questions.

Which frameworks does it support?

It picks the one your users build with, or the one you name, as long as there is no starter for it yet.

Will it publish the starter?

No. It opens a pull request in your repository. You merge it when you are happy.

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.It takes one command.

Try in browser →
codex mcp add tin --url https://app.tin.computer/mcp