TinTinWorkflows
GitHubSign in

One memory for every workflow

Tin consolidates the durable outputs of your project into a wiki. Every workflow reads it, so your audit, your content and your QA agree about what the product is.

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 reports, maps and approved outputs in the project.
  2. 02Consolidates them into the project wiki.
  3. 03Keeps the wiki current as new runs finish.
ask your agent

Garden our Tin project memory and tell me what changed.

workflow keyproject.memory
outputProject wiki
needsA Tin project with outputs.
guardrailWorks only inside your project.

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

Your agent knows the product from the code. Memory adds what the code cannot say: customers, results and decisions.

All workflows →

Questions

Where does memory live?

In your project's files. You can read and edit it like any other file.

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