One safe site improvement at a time, as a pull request
Tin inspects your public site against the repository behind it, makes one bounded mechanical improvement, and opens a pull request. When no safe change is justified, it saves a no-change report and opens nothing.
codex mcp add tin --url https://app.tin.computer/mcpWhat 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.
- 01Inspects the live site and the selected repository together.
- 02Chooses one mechanical improvement inside the change budget.
- 03Opens a pull request with the reasoning.
- 04Saves a receipt, including when the right answer was to change nothing.
Run Tin's site health improvement on our marketing site, focused on metadata.
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
Small mechanical fixes are easy to get wrong in an unfamiliar codebase. Your agent knows this one.
All workflows →Using something else for this today?
What this workflow replaces in each product, and what it does not.
Workflows that run well with this one
Questions
Why only one change per run?
Small pull requests get reviewed and merged. The change budget keeps each one easy to read.
Has this been used on a real product?
Yes. It shipped eleven site fixes in the first week of the Claw Messenger project shown on the homepage.
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.