Switch from win.sh to Task Machine
win.sh routes company work through one operator and editable business loops. Task Machine keeps each job on a shared Task, with explicit workflow steps when you need them.
Prefer the side-by-side comparison?Why people switch
-
GitHub availability is unclear
The integration catalog marks GitHub Soon, but its GitHub page says Available now. Check which applies to your account before relying on it.
-
Hosted writes are restricted
The public API connects local loops to hosted connector snapshots. Its documentation says hosted write endpoints are not public yet.
-
Refunds have usage conditions
The pricing page promises a full refund if you email within 7 days because win.sh did not deliver value. Its terms make refunds subject to reasonable use limits and allow refusal for abuse or excessive usage.
What maps to what
Every answer links to its source and shows when we last checked it. The oldest check on this page was November 14, 2026.
| Area | In win.sh | In Task Machine |
|---|---|---|
| Agents |
In win.sh
A goal becomes projects with deadlines and priorities, and one company operator routes the work. |
In Task Machine
Every job is a Task that a person or an agent owns. The Task keeps its plan, discussion, decisions, runs and history together, and people and agents hand work to each other on the same record. |
| Recurring work |
In win.sh
Schedules, events, anomalies and fresh signals can start a run. Local and hosted loops choose their next useful run date rather than a fixed interval. |
In Task Machine
Start a Task or Workflow once, on a schedule in your timezone, or when a service event arrives. A recurring job keeps one stable root Task and gives each occurrence its own status and history. |
| Approval |
In win.sh
An authority matrix sets what each type of work may do alone and what needs approval. You adjust it from the Decisions tab. |
In Task Machine
You set what each agent may do on its own, with Ask first or Automatic for each action. A Human approval step can pause a Workflow before publication. |
| Memory |
In win.sh
Company memory saves decisions, rules, customer patterns and confirmed learnings. Local loops also keep append-only journals of signals, actions, results and lessons. |
In Task Machine
Agents keep lessons from your corrections and carry relevant notes into later work. Memory is kept per agent, project, goal, team and workspace, and you can read, correct and restore any note. |
| Briefings |
In win.sh
Morning reports arrive in Telegram, with real-time alerts when something needs attention. Decisions are logged with their reasoning. |
In Task Machine
Consequential decisions land in your Inbox with their context and resolution actions. The Task keeps the plan, discussion, decisions, runs and history together. |
| Connections |
In win.sh
The catalog labels Stripe, Plausible and Google Search Console Live. It labels Custom API and Custom MCP Soon. |
In Task Machine
Install services from a catalog as MCP servers, APIs or command-line tools, or add your own custom Connector for any of the three. Events Connectors receive service events and start Workflows or wake a waiting Task. |
| Hosting |
In win.sh
Hosted workflows run code in cloud sandboxes. The local harness hands runs to Codex or Claude Code using readable loop files in your repository. |
In Task Machine
Run agents in Managed Cloud with nothing to install, or connect a Local Worker, a computer you control, for local files, tools and accounts. You choose where each agent runs. |
| Pricing |
In win.sh
Self-serve monthly budgets range from $50 to $10,000, with a hard monthly limit and optional one-time top-ups. |
In Task Machine
Usage based, from $29 a month before tax. The whole payment becomes usage that your workspace shares, with no base fee. |
A fact we cannot find or cannot check is left out, and prices can change after the date shown. Task Machine publishes this comparison and is an interested party. win.sh is named only to identify it, and there is no relationship between the two companies. Has something changed? Tell us.
You may stay with win.sh if
You may stay with win.sh if you prefer to edit business loops as files and let each loop choose when to run again. Its open-source harness lets you use your own agent subscription and keep the loop contracts, state and journals in your repository. That fits a business whose operating process already lives alongside its code.
What you give up
You give up the file-first loop format as your way of editing the process. In Task Machine you configure agents and publish Workflow steps. Its docs do not describe importing win.sh loop packs or restoring their journals as Task histories. A Local Worker uses Task Machine's tamacode agent, so moving a local loop also changes the executor.
Budget time to rewrite instructions, reconnect services and test approval boundaries. There is no trial. You keep 100% of your revenue, Task Machine takes no cut, and never custodies your accounts, as its pricing page explains.
How the switch works
- Keep a copy of your local loop contracts, skills and journals before changing anything. The harness documentation lists run briefs under
.win/runs/, execution logs under.win/executions/and state under.win/state/. For hosted company memory and history, check win.sh's export options before cancelling. - Create your workspace and connect your services. Copy reusable company guidance into Library documents and curate the lessons you want to keep in Memories. Set up fresh credential access rather than copying local harness tokens.
- Choose a Playbook for one job, such as a weekly business review. Rewrite the loop's inputs, outcome and verification rules as agent instructions and Workflow steps, with a human approval before consequential actions.
- Start with Supervised autonomy, run the process once and inspect its output. Test both approval and rejection before allowing recurring work.
- Pause the old loop before enabling its replacement's schedule. The local harness has a disable command that preserves its files and journal, and hosted win.sh has pause controls. Review the replacement's decisions in Inbox.
Common questions
What does Task Machine cost after switching?
Pricing is usage based, from $29 a month before tax. The whole payment becomes usage that your workspace shares, with no base fee. There is no trial. Your external service subscriptions remain separate.
Can I bring my win.sh data?
Keep the local files that the harness documents, and check export options for hosted data before cancelling. Save useful guidance as Library documents or memory notes. Task Machine's docs do not describe importing win.sh run history into Tasks.
Can I keep using my own model subscription?
Yes. Sign in to your ChatGPT (Codex), Claude or GitHub Copilot subscription on a Local Worker. Task Machine's tamacode agent uses that subscription. This changes the executor rather than hosting your existing Codex or Claude Code process.
Do I need a Workflow for every loop?
No. Use a Task for one result with an owner and history. Use a Workflow when the job needs explicit steps, branches, approval or verifier checks. Schedule the recurring job only after its first result and review boundaries work.