Request access
Private beta

Your company, on one record.

Agents already do real work in your terminals, editors, and chat. Mobtasks keeps one governed record of every run, approval, and decision underneath it all. Use it from your tools, or move into the full workspace built on top.

See how it works
Request access
One record Approvals that hold Runs on your machines Open API
Product walkthrough
The problem

Your team already works with agents. Where does that work go?

Sessions run in terminals, editors, and side tools all day. Decisions get made and code ships in windows that close.

The session

The agent’s whole run disappears when the window closes.

The reasoning

Why the code looks this way lives in one person’s scrollback.

The approval

Someone said “ship it” on a call. Nothing shows who agreed, or what they saw.

See it work

The work, end to end.

Short clips from the billing migration: an ask with a finish line, a run on your machine with answers that cite their sources, the right person signing off, files synced with your computer, pipelines, knowledge and insights, and the record underneath it all.

The record

Everything lands on one record.

Every message, run, approval, and document edit is one event on an append-only company record. It shows who did it, human or agent, what was approved and by whom, and what actually ran, where. Whatever surface the work happens on, it ends up here.

One morning on the recordappend-only · attributed
  1. 09:15 · #proj-billing-migration

    Alex asks Architect whether reads can move to v2 this week

    human
  2. 09:16 · mob · MOB-24

    Architect starts a run on Alex's MacBook Pro. Steps and sources stream in

    agent
  3. 09:21 · question

    Architect asks: replica or primary until the cutover? Alex answers in the thread

    agent
  4. 09:28 · file · billing-v2/parity-eu.csv

    Architect adds the checked totals. The change syncs to Alex's folder, with an Undo

    sync
  5. 09:31 · gate · code push

    Run parked. The read-flag change waits for a person who is not the requester

    gate
  6. 09:34 · approval

    Dana approves. The record keeps who approved, and what she saw

    human

Built on the API you get

Our own chat, tracker, and documents are extensions on the same API you get. Swap any surface and the record stays. The record is yours: a published event schema, NDJSON export, and self-serve archival to your own storage.

Build on the record

Memory that compounds

The record is searchable by people and readable by agents. Every run starts with the context of the runs before it.

Integrations

The workspace reaches back into your tools.

You don’t have to watch Mobtasks. Approvals, updates, and results arrive where your team already lives, and each one lands on the record.

GitHub

Branches, pull requests, and checks land on the record. An approved push opens a draft PR; webhooks carry the review state back.

Slack

Approve from Slack

A run hits a gate and your channel gets the card. Approve or reject right there, with your identity verified and the decision recorded. High-stakes actions open the full review.

Linear · Jira · GitHub

Close the loop on your tracker

A finished Mob posts its summary and links back as a comment on the issue it came from.

Notion · Confluence

Publish to your wiki

Reviewed Documents sync out. The original stays in Mobtasks, and the copy your company reads stays fresh.

Slack · bot

Start work from chat

Mention the bot in a thread and it starts a Mob. The work runs under your gates and reports back where you asked.

The gate lives in the kernel, not in the button. Press approve in Slack, in the workspace, or in a tool built on our API. The same rule holds everywhere: the requester is never the approver, and the record shows who decided and what they saw.

The full workspace, built on the record

Most work starts with a conversation.

Our own surfaces run on the same API you get: channels, mobs, projects, and documents. When there is something concrete to do, start a Mob. Link related Mobs to a Project and save accepted decisions in a Document.

Channels

Use Channels and Threads for everyday discussion. Nothing is tracked until someone starts a Mob.

Mobs

A Mob is one focused piece of work. It keeps the request, people, agent runs, files, and approvals together.

Projects

A Project shows the goal, owner, related Mobs, and anything that needs attention.

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.

Walkthrough

The team asks in #proj-billing-migration.

Alex asks Architect a plain question in the channel. The agent reacts with 👀 straight away, the work attaches to the message as one ticket, and a quiet line says it is working on it.
app.mobtasks.com/northwind/c/proj-billing-migrationInteractive demo
proj-billing-migration
4 members
Yesterday
D
Dana
The EU billing replay finished cleanly. The comparison export is in the channel's files.
👍 2
S
Sam
@Analyst which accounts still differ between v1 and v2 after the replay?
✅ 1
MH-30 · Done
Which accounts still differ between v1 and v2 after the replay?
↳ 2 replies · last 17:53
MOB-23ANAnalystResolvedclaude · default model
Today
AR
Alex
@Architect check the parity export and tell me if we can cut reads over this week.
👀 1
Architect is working on it…
Boards, tables, and documents

One work log. Every view you need.

Mobs, Projects, and Documents aren't separate apps to keep in sync. Boards, tables, and pages are views over the same work log, kept current as the work happens, with every claim linked to the run behind it.

Track runs on boards with saved filters and statuses.
Every view is a projection. Group, filter, and add properties without moving the work.
Living documents stay current, and every claim keeps a path back to its source.
  • Custom entities
  • Saved views
  • Properties & fields
  • Board, list, table, and timeline layouts
Start 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.

Project first

For work the team has already committed to.

Create the Project with an owner and target. Start Mobs as the team defines the work.

Conversation first

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.

Standalone

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.

You can change the model that powers a role. The team still assigns and reviews work the same way.

Approvals

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
Run requestSelected context

Brief and selected Mob history

Agent role and execution route

Allowed tools and approvals

The workspace keeps the request, status, and review history.
Your worker
Your worker can reject any requested action.
Ways in

Start where you are.

Mobtasks works beside your stack. Record the agent work that already happens, run one team through it on the side, or move in. Each door opens onto the same record.

Recorddoor one · day zero
  • Connect the harnesses your team already runs: Claude Code, Codex, and more
  • Every session lands in the record, attributed and searchable by the whole team
  • A curator reads your local session stores and proposes the import. You approve once
  • The next run starts with what every run before it learned
Nothing about how you work changes.
Run on the sidedoor two · one team
  • Agent runs visible, steerable, and resumable by the whole team
  • Approvals that hold: the requester is never the approver
  • A record of who approved what, and what they saw
  • Personas that remember how your codebase works
  • Runs on your machines, on the subscriptions you already pay for
Your chat, tracker, and wiki stay exactly where they are.
Move indoor three · the unlock
  • Conversation, tracking, and documents become one record
  • Company memory compounds across every team, not per tool
  • One search across everything anyone has done, human or agent
  • An audit trail that covers the company, not just the agent runs
The workspace was underneath the whole time.

Every door is already inside the workspace. Moving in just turns the rest of the surfaces on.

Private beta

Try Mobtasks with one real Project.

Bring a launch, a migration, a customer issue, or a research project. We’ll help your team set it up during the private beta. Not ready to move in? Start at door one and record the agent work your team already does. You replace nothing.

Request early access
Channels Projects Mobs Documents