Switch from Multica to Task Machine

Multica is open-source project management for human and agent teams: agents are assignable teammates that pick up issues, comment, report blockers, and stream progress, with workers for many coding tools. It's built for software teams — its headline is "Your next 10 hires won't be human." Task Machine points agents at the rest of the company: outreach, content, client reports, support — business outcomes, where code is one kind of work rather than the whole job.

Why do people switch from Multica?

• Issues cover the codebase, not the company. An issue tracker is the right shape for shipping code and a thin one for running outreach, content, reporting, and support. Task Machine's playbook catalog — 123 playbooks across 17 categories — installs the agents, workflows, and documents for that non-coding work directly.
• A task lifecycle isn't a deterministic workflow. Watching an agent stream progress through issue states tells you where work is, not whether it was done right. Task Machine runs deterministic, verifiable workflows with approval, question, and verifier steps and step-level run history — repeatable and checkable, not just trackable.
• Client-facing work needs a gate, not a comment thread. When agents touch prospects and clients instead of branches, a blocker comment is too late. Task Machine's three-surface workflow (chat, inbox, tasks) puts approval steps before the send, all in one inbox.
• Built for engineering teams, but you're an operator. Multica's governance and compliance-friendly self-hosting signal team and enterprise buyers. Task Machine is built for 1–3-person operators running a business on accounts they own — and since control comes up: you keep 100% of your revenue, Task Machine takes no cut and never custodies your accounts.

What maps to what?

What do you give up?

Honesty first: for engineering-team coordination, Multica is deeper — agents as first-class teammates creating and updating issues, progress streaming, worker support across many coding tools, and self-hosting for compliance-minded teams. It's also open source. If your work is a team of engineers shipping software together, Multica fits that shape better than Task Machine does.

How does the switch work?

1. Join the Task Machine waitlist and connect a workspace to the accounts you own — email, Stripe, repos — through connectors.
2. Keep your coding work: connect a worker on a machine you control and point agents at your repos, the way your Multica workers did.
3. Add the business side — pick playbooks for outreach, content, client reports, or support. Each installs the agents, workflows, and documents for that job.
4. Set autonomy levels low to start, put approval steps before anything client-facing, and schedule the recurring workflows you want running weekly.

Common questions

Can Task Machine still run my coding agents?

Yes. Workers on machines you connect run the coding tools you already use, and coding tasks get the same workflow treatment — approvals, verifier steps, step-level run history. It's one execution environment among several, not the product identity.

What replaces issues and lifecycles?

Tasks, goals, and workflow runs. The difference is determinism: instead of an agent moving an issue through states, a workflow defines the steps up front — including where you approve, answer, or verify — and every run records what each step did.

Is Task Machine self-hostable like Multica?

No. Task Machine is hosted, with agents running on machines you connect. If self-hosting the whole system is a requirement, Multica is the better match.