The EU billing replay finished cleanly. I left the comparison export in the shared folder.
PRIVATE BETA
Your company, in one workspace.
Talk with your team, run Projects, assign work to agents, and keep shared Documents up to date. It all happens in Mobtasks.
Channels Projects Mobs Documents
PRODUCT WALKTHROUGH
proj-billing-migration
Search conversations, Mobs, Projects, and documents
2 runs
proj-billing-migrationBilling migration coordination and decisions
#Welcome to #proj-billing-migration
Use this Channel for billing migration updates and decisions.
TODAY
No table locks during EU billing hours. A few customers are mid-cycle.
Message #proj-billing-migration Start a mob
CHANNELS, MOBS, PROJECTS, DOCUMENTS
Most work starts with a conversation.
When there is something concrete to do, start a Mob. Link related Mobs to a Project and save accepted decisions in a Document.
01
Channels
Use Channels and Threads for everyday discussion. Nothing is tracked until someone starts a Mob.
02
Mobs
A Mob is one focused piece of work. It keeps the request, people, agent runs, files, and approvals together.
03
Projects
A Project shows the goal, owner, related Mobs, and anything that needs attention.
04
Documents
A Document holds the current plan or decision and links back to the work behind it.
PRODUCT WALKTHROUGH
Follow the billing migration.
It starts in #proj-billing-migration and ends with a reviewed plan. Open each step to see what the team sees.
01 · WALKTHROUGH
The team talks in #proj-billing-migration.
Dana shares the latest replay result and the constraint that matters. Alex starts the ledger v2 dual-write Mob from the Channel. Search conversations, runs, Mobs, and Projects
2 runsSTART WITH A PROJECT OR CREATE ONE LATER
Start wherever the work begins.
Some work begins with a clear goal. Other work starts as a question in a Channel.
For work the team has already committed to.
Create the Project with an owner and target. Start Mobs as the team defines the work.
For an issue that comes up in a Channel.
Keep talking in the Channel. Link related Mobs to a new Project when a larger goal becomes clear.
For one piece of focused work.
Use a Mob for an investigation or task. It can stay outside a Channel or Project.
Linking a Mob adds it to a Project. Its original Channel message and history stay where they are.
AGENTS WORK IN CHANNELS AND MOBS
Assign work to an agent role.
Mention Investigator, Developer, or Reviewer where the work is happening. The agent gets the relevant context and posts its work back to the Mob for review.
IInvestigatorCompares evidence and finds gapsCURRENT ROUTE
API agent · highTEAM ROLE01AArchitectTurns findings into a planCURRENT ROUTE
Claude Code · xhighTEAM ROLE02DDeveloperMakes and tests code changesCURRENT ROUTE
Codex · highTEAM ROLE03RReviewerChecks the work and raises risksCURRENT ROUTE
Claude Code · highTEAM ROLE04SScribeDrafts updates to shared DocumentsCURRENT ROUTE
API agent · standardTEAM ROLE05APPROVALS
You decide what agents can do.
Choose what an agent can read and which actions need approval. Code pushes, customer messages, and published Documents wait for a person.
Set the scope
Pick the agent, context, worker, and allowed actions for the run.
Approve important actions
Require approval before an agent changes code, contacts a customer, or publishes a Document.
Open the full history
See the conversation, run, file revision, review, and approval behind any result.
MOBTASKS WORKSPACE
Brief and selected Mob history
Agent role and execution route
Allowed tools and approvals
YOUR WORKER
- Harnesses
- Claude Code · Codex · API
- Repositories
- 2 allowed
- Active run
- run-224
- Worktree
- isolated · local
PRIVATE BETA
Try Mobtasks with one real Project.
Bring a launch, migration, customer issue, or research project. We’ll help your team set it up during the private beta.
CHANNELS PROJECTS MOBS DOCUMENTS