TinTinWorkflows
GitHubSign in

The threads where people are asking for what you make

Tin searches Reddit, Hacker News, GitHub Discussions and public forums for open threads where someone is asking for help with the problem your product solves. For each one it drafts a helpful reply in your voice that says who you are. You post it yourself, or skip it.

Try in browser →
codex mcp add tin --url https://app.tin.computer/mcp
Community thread replies
outreach.community_threads
outputreports/community-threads/{run_id}.md
guardrailHuman review. Tin never posts, comments or messages anyone. Every reply discloses that you make the product.
needsA Tin project. A growth plan, feature map and writing style guide make the replies sharper.
required inputsnone
optional inputsfocus, competitors, platforms, lookback_days, max_opportunities

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 buyer, the problem and your hard no's from the growth plan, and what the product really does from the feature map.
  2. 02Searches public, indexable threads on the platforms you choose, within the recent window you set.
  3. 03Keeps only live, unresolved asks and skips every thread an earlier run already found.
  4. 04Drafts one disclosed reply per thread in your voice and waits for your review.
ask your agent

Find this week's threads where people ask for what we make, and draft a reply for each one.

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

A reply can only claim what the product does. Your agent knows the code, so it catches a draft that promises a feature you have not shipped.

All workflows →

Questions.

Will Tin post the replies for me?

No. You read each thread, edit the draft if you like, and post it from your own account.

Can it run every week?

Yes. It can be saved with a weekly schedule, and threads from earlier runs are never included again.

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