Skip to content
Wagglet

Official documentation

Two agent paths. One product authority.

Use Task Handoff for one claimed task. Use the MCP Workspace Workflow for ongoing access to the Wagglet records and actions already authorized for one person in one Team.

Choose by scope

Start with the job you are handing over

The two workflows use different credentials, boundaries, and lifecycles. A convenient setup must not blur them.
One claimed taskTask HandoffCopy exact task instructions into a fresh agent session, refresh bounded context while the claim is active, then use a separate later delivery capability.Read guide →One person · one TeamMCP Workspace WorkflowConnect an agent to current authorized Wagglet views and explicit actions through a named, revocable MCP Connection.Read guide →Product flowHow Wagglet worksSee how an author prepares the work, a teammate claims and supervises it, and a reviewer records the verdict.Read guide →Trust boundarySecurity and privacyUnderstand what each credential can expose, what Wagglet rechecks, and where the human remains responsible.Read guide →

The shortest comparison

A copied task is not workspace access

Both paths preserve Wagglet's current product permissions. They differ in where the boundary starts.
Task Handoff
Rooted in one current claim. A read-only capability covers that task and, when linked, permitted current Story context. It ends with the claim and expires after at most seven days.
MCP Workspace Workflow
Rooted in one named MCP Connection for one person and one Team. It has no automatic expiry, but Team access, membership, roles, permissions, and revocation are checked again on every request.
Task Handoff delivery
The starting read credential cannot deliver. The runner later copies a separate, one-time delivery prompt into the same agent session.
MCP mutations
Explicit Wagglet actions use current revisions and a fresh operation id. There is no generic status override and no database-shaped interface.
  1. AuthorPrepareOutcome, context, limits, evidence
  2. RunnerClaimChoose appropriate work and capacity
  3. PairSuperviseAgent execution plus human judgment
  4. AgentDeliverRecord branch, outcome, changes, warnings
  5. ReviewerDecideAccept, send back, or reopen

Before real work

Match the task, person, and provider policy

Wagglet moves prepared work. It does not make an unauthorized task, unqualified reviewer, or prohibited provider use acceptable.

Start with a small synthetic or low-risk task. Confirm that the runner may access the repository and data, knows what to inspect, and uses their own authenticated agent. Keep secrets out of task text. Use Human-only work when an agent should not receive the task.