Send your awesome list entries, after you see every change
Tin takes the lists an awesome lists run found, places your entry where each list's current file expects it, and shows you every exact change. After you approve, it forks each list and opens one pull request or issue from your own GitHub account.
codex mcp add tin --url https://app.tin.computer/mcp
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.
- 01Reads the newest awesome lists report in the project, or the run you name.
- 02Places your entry in each list's current file: the right section, the right order, the right format.
- 03Shows you every exact change and waits for one approval.
- 04Forks each approved list and opens one pull request or issue from your account, with a receipt per list.
Submit our entry to the top three lists from the last awesome lists run. Show me the changes first.
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 read each diff against the list's rules with you before you approve, so a submission does not fail on a rule nobody read.
All workflows →Runs well with.Workflows that feed this one, or follow it.
Questions.
Whose GitHub account opens the pull requests?
Yours. You connect your GitHub account to the project, and the submissions come from it, the way a maintainer expects.
What if I run it again later?
Each list has a project-wide receipt, so a later run skips every list you already submitted to.
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.
codex mcp add tin --url https://app.tin.computer/mcp