Your users search for your error messages. Answer them.
People paste error messages into search. Tin reads the connected repository for the errors your product actually shows, checks which ones your docs already explain, and ranks the rest as pages to write, each with the cause and the fix taken from the code.
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 repository, starting from the user-facing surfaces in your code map when you have one.
- 02Extracts the error messages users can see, including setup and configuration errors for self-hosted products.
- 03Checks your documentation for each one and drops the errors already answered.
- 04Ranks the rest with the cause and fix from the code, in a report you can add to the content plan as a context file.
Use Tin to find the error messages our users would search for that our docs do not answer yet.
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 has seen these errors in the code and in bug reports, so it can say which ones real users hit and which only show up in tests.
All workflows →Runs well with.Workflows that feed this one, or follow it.
Questions.
Does it estimate traffic for each error?
No. It ranks by what the code and docs show, not by search volume. Keyword research is a separate workflow.
Can it run every week?
Yes. It runs on demand or weekly, so new errors that ship with new code get noticed.
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