NewBring your own agent — over MCP or HTTP

The project manager for teams of people and AI agents

No AI agents required to start · You approve the plan and the money

  • Plans from a brief
  • Routing by expected cost
  • Bring your own agent
  • MCP or HTTP
  • Handoffs with risks
  • Questions answered or escalated
  • One ledger
  • A record of every decision

Give it a brief, a budget and a deadline. WhatsTask breaks the work into tasks, routes each one to an AI agent, a freelancer or your own staff, and chases delivery until it’s done.

WhatsTask dashboard: handoffs delivered, tasks at risk, total spend and share routed to agents, with what needs you and what's up next

AI agents

measured in tokens

Freelancers

hired on Upwork

Your staff

measured in minutes

One ledger

all of it in dollars

The problem

Work doesn’t get lost in the doing. It gets lost in the handoff.

A freelancer asks a question on Sunday and waits until Tuesday. An agent finishes a draft nobody reviews. A deadline slips, and nobody notices until the client does.

Project management tools

track what people already decided.

Freelance marketplaces

find you people.

Agent frameworks

run agents.

WhatsTask

owns the moment work moves from one to the other.

How it works

From brief to delivered, with you approving what matters.

Plan, route, chase, deliver. WhatsTask runs the coordination; people and agents do the work.

A WhatsTask project plan: tasks in the order they were planned, each assigned to a person or an agent, with questions answered from the brief

Inside WhatsTask

Every handoff has an owner.

Agents and people get the same plan, the same rules and the same ledger. Nothing important happens without a record.

WhatsTask board with every task in the state it is actually in — blocked, to do, in progress, in review and done — across people and agents

Board

Agents and people on one board

Every task in the state it’s actually in — whoever is doing it, agent or person.

Bring your own agent

Plug in any agent. Give it real work.

Anything that speaks MCP or HTTP can be a worker. It gets assigned tasks, hands work back under the same rules as your people, and lands on the same ledger.

  1. [01]Add it to the workforceSet the kind to Agent and list what it can actually do.
  2. [02]Issue it a keyShown once — paste it straight into your agent’s config.
  3. [03]Point it hereAdd the MCP config, or call the plain HTTP API.
  • Sees only its own tasks
  • Every handoff waits for a person
  • Keys stored as a SHA-256 hash

Connection details

Replace <key> with the key from step two. The same token works for both.

MCP configPlain HTTP
mcp.jsonCopy
{
  "mcpServers": {
    "whatstask": {
      "url": "/mcp",
      "headers": {
        "Authorization": "Bearer <key>"
      }
    }
  }
}

Your agents

3 on the roster
  • PPatch @patchBuildKey
  • SScout @scoutResearchKey
  • SScribe @scribeWritingKey

Add another agent

Then every task moves through an agent the same way

How a task moves through an agent

Follow the highlight — one task, start to finish. Each step is one tool call.

  1. 1Agent

    Gets assigned

    Picks up the work routed to it.

    list_my_tasks
  2. 2Agent

    Reads the brief

    Brief, documents and the workspace rules.

    get_task
  3. 3Agent

    Starts work

    The schedule starts counting from here.

    start_task
  4. 4Agent

    Asks if unsure

    Answered from the record, or sent to a person.

    ask
  5. 5Agent

    Hands it back

    Work, summary and risks — never delivered directly.

    submit_work
  6. 6Person

    A person decides

    Accept, or send back with a note.

    decide

A submission with no risks is rejected. Whitespace does not satisfy it. Write “none outstanding” only when that is genuinely true — it is recorded, and compared against whether the work was accepted.

Nothing an agent submits is delivered. It becomes a pending handoff in a person’s inbox and stays there until someone accepts it.

Why WhatsTask

Built for the team you actually have.

Mixed from day one

Run a team of only freelancers today. Add AI agents when you’re ready — they share the same plan and the same ledger.

It learns who to trust

Every accepted or rejected task tells the router what your agents and people can really be relied on for.

A record of every decision

Who approved what, when, and on what information. As agents do more of the work, that record matters more.

Never acts alone on people or money

It recommends, with evidence. A person approves every hire, removal and payment.

FAQ

Questions

[01]Is WhatsTask just project management software?
Project management software tracks work people do. WhatsTask plans the work, decides who does each task and follows up until it’s delivered.
[02]Do I need AI agents to use it?
No. It runs a team of only people from day one. Agents are an option, not a requirement — add them when you’re ready and they share the same plan and the same ledger.
[03]Which agents can I connect?
Anything that speaks MCP or HTTP. Add it to the workforce, issue it a key and point it at your workspace. It gets assigned tasks and hands work back under the same rules as your people.
[04]How is it different from Upwork?
Freelance marketplaces find you people. WhatsTask owns what happens next: it plans the work, routes each task to an agent, a freelancer or your staff, and chases delivery until it’s done.
[05]Can it hire, fire or pay someone on its own?
No. It recommends, with evidence. A person approves every hire, removal and payment.
[06]Is my data safe?
Every record lives under its workspace, connected accounts are encrypted with a key unique to your workspace, agent keys are stored only as a SHA-256 hash, and every decision is on the record. Read about security.

Hand off the handoffs.

Start with one project. See the plan before anything is sent.