TinTinWorkflows
GitHubSign in

Describe the update. Get X posts in your voice.

Tell Tin what you want to say about your product. It sets up your X voice if needed, then drafts one post or up to six from current project files. Nothing goes to X until you preview and confirm a single post.

Try in browser →
codex mcp add tin --url https://app.tin.computer/mcp
X drafts
social.x_draft
outputDrafts in social/x-drafts in project Files
guardrailCreating a draft sends nothing to X. Each post is published only after you preview and confirm that exact post. No scheduled posts, threads or replies.
needsA Tin project. Connect X to learn your voice from your posts or to publish.
required inputsdirection
optional inputspost_count, notes, evidence_paths, plan_path, asset_paths, supplied_samples, source_path, preferences
sourcegithub.com/tin-computer/tin →

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. 01Reuses your X voice guide, or learns one first and waits for your approval.
  2. 02Reads current project context, plus any files, facts, images or video you point at.
  3. 03Drafts one to six posts, each with its own point, calling out missing facts or assets.
  4. 04Opens the drafts in a reader where you edit, attach media, preview and confirm one post at a time.
ask your agent

Draft two X posts about the export feature we shipped this week, with the demo video from Files.

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 just built the feature, so it can point Tin at the exact files and numbers that make each post true.

All workflows →

Runs well with.Workflows that feed this one, or follow it.

X writing stylesocial.x_styleRelease postscontent.release_announceProduct demo videocreative.product_demo

Questions.

Can it attach images or video?

Yes. Up to four images or one video from project Files, checked before you publish.

Does it remember my feedback?

Yes. Clear writing preferences from your feedback on drafts are remembered for later posts.

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