Switch from Nebula to Task Machine
Nebula keeps agent work in shared channels and live calls. Task Machine gives people and agents Tasks with plans, review gates and an Inbox for decisions.
Prefer the side-by-side comparison?Why people switch
-
Write approval starts off
Nebula's risky-write safety gate is off by default and each person enables it separately. Irreversible browser actions still get checked against your request, and unattended risky writes are checked regardless of the gate.
-
Local agents stay private
A coding agent on your own computer is yours alone and cannot join a channel's team. Sharing that agent with teammates requires putting it on a cloud device and sharing it with the workspace.
-
Idle files need backups
Without a subscription, Nebula deletes a cloud device and its files after 60 idle days, without a warning or notice. A remaining credit balance does not keep the device.
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 15, 2026.
| Area | In Nebula | In Task Machine |
|---|---|---|
| Tasks |
In Nebula
A task lives in the thread that started it. Follow-ups continue that task, and its activity shows tool inputs, outputs and progress. |
In Task Machine
Every job is a Task that a person or an agent owns. Its plan, discussion, decisions, runs and history stay together, so people and agents can hand work to each other on the same record. |
| Recurring work |
In Nebula
Scheduled tasks keep their runs together. Channel events, connected-app events and webhook calls can also start work. |
In Task Machine
Start a Task or Workflow once or on a repeat in your timezone. A recurring job keeps one stable root Task, with each occurrence's own status and history. |
| Procedures |
In Nebula
A skill saves a reusable procedure in a SKILL.md document. Channel, personal and agent skills can run as slash commands. |
In Task Machine
A Workflow repeats explicit steps with branches, human questions and approvals. Verifier checks judge results against requirements and send failed work back with feedback. |
| Approval |
In Nebula
Tasks can show plan and action approval cards. Waiting threads rise to the top of the desktop Inbox, and you can answer cards in the thread or inside the task. |
In Task Machine
Decisions arrive in your Inbox with context. Set each agent's actions to Ask first or Automatic, and put a Human approval step before an action such as sending a report. |
| Memory |
In Nebula
Native agents show learned memory under Brain, where you can delete a wrong note. Coding agents use their runtime's own memory instead. |
In Task Machine
Agents carry lessons such as accepted examples into later work. Keep notes per agent, Project, Goal, Team or workspace, and read, correct or restore them. |
| Coding agents |
In Nebula
Connected coding agents run their own tools and instructions. Their tokens use the owner's plan or API key rather than Nebula Credits. |
In Task Machine
A Local Worker runs tamacode, Task Machine's coding agent, with subscriptions you sign in to, such as ChatGPT or GitHub Copilot. It does not host your existing coding-agent runtime. |
| Pricing |
In Nebula
Nebula Workspace is $25 per person per month, including the owner. Native-agent tasks, tools and cloud-device hours use extra Nebula Credits. The subscription adds no monthly credits. |
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. Nebula is named only to identify it, and there is no relationship between the two companies. Has something changed? Tell us.
You may stay with Nebula if
You may stay with Nebula if your team wants to discuss work together on a live call, show Nebula a screen and delegate tasks while the conversation continues. Nebula keeps the recap with the channel. Its coding-agent connections also suit teams that want to keep using their existing runtimes rather than move the work to another coding agent.
What you give up
Task Machine's docs do not describe live team calls with an agent listening, screen sharing or an importer for Nebula's channels and task threads. Keep your meeting tool and archive the conversations you need. Rebuilding procedures, reconnecting accounts and checking that recurring jobs still produce the right result takes time.
There is no trial. Your first payment funds usage, and ordinary failed attempts still consume it. Read Billing before moving a busy schedule.
How the switch works
- Before cancelling, download needed files from each native agent's desktop Files view. Copy files from cloud devices too. Check Nebula's export options for conversations and call records, and keep a separate archive rather than assuming a file download includes them.
- Copy the instructions and useful memory from each agent's Brain, save your skill text, and record each scheduled task's prompt, steps and schedule. Create your workspace, reconnect the required accounts, and upload reference files to the Library.
- Move one job first. Choose a Playbook or rebuild the procedure in the Workflow builder, with an owner, expected output and checks. For code work, connect the repository and choose Cloud execution or an optional Local Worker.
- Choose Supervised autonomy for unfamiliar work. Add approval before sending or publishing, test with copied inputs, and review the result in Run history.
- Once the replacement passes review, pause the original scheduled task before enabling the new schedule. Redirect event sources separately so both systems do not act on the same event.
Common questions
Can I bring my existing coding agent unchanged?
Treat it as a rebuild. Nebula connects external coding runtimes. Task Machine's Local Worker uses tamacode instead, so review the instructions, tools and account permissions before moving a coding job.
What happens to my data?
Keep original source files and download the native-agent files you need before deleting agents. Nebula's storage guide says deleting an agent also deletes its stored files. Upload selected files to Task Machine's Library, and check Nebula's export options for messages and call records separately.
How do the costs compare?
Nebula separates seats and usage credits. Task Machine's pricing starts at $29 a month before tax, with no base fee and no trial. Compare the usage of one representative job before moving the rest. You keep 100% of your revenue, Task Machine takes no cut, and never custodies your accounts.
Can scheduled work wait for my decision?
Yes. A Human approval step pauses a workflow until a permitted person decides. Put it before the action it controls, such as emailing the weekly report, then set the schedule and timezone.