TabTwinTaskTwin← Back to home
Subsystems/TaskTwin

Collaborate

TaskTwin

Don’t send instructions. Send your workspace.

TaskTwin combines an assignment with the exact browser context required to complete it. The recipient opens the relevant route, entity, notes, and saved state instead of reconstructing context from a chat message.

01
Why this capability exists

From friction to a clear outcome

The user problem

A handoff message often says what to do but not where the work is, which record matters, what has already been checked, or why a decision is needed. The receiver spends time reconstructing the sender’s browser context.

The TabTwin answer

TaskTwin packages the assignment with the exact safe browser context needed to continue. The teammate opens the relevant route, selected entity, notes, and expected outcome as one resumable task.

02
Real-world scenario

Handoff a vendor approval without losing context

  1. 1

    Open the vendor record that needs review

  2. 2

    Create a TaskTwin from the current page

  3. 3

    Include selected tabs, notes, and the approval criteria

  4. 4

    Assign the task to the finance owner

  5. 5

    Receive the completed decision with its context trail

03
End-to-end workflow

How TaskTwin works

  1. 01

    Create a task from the page and select the relevant context.

  2. 02

    Add the requested outcome, notes, deadline, and safe state snapshot.

  3. 03

    The assignee opens the TaskTwin link, completes the work, and returns a contextual result.

04
What is included

Core capabilities

01

Contextual assignment

Combines the requested outcome and supporting browser state in one link.

02

Saved routes

Returns the assignee to the relevant URL, record, and working location.

03

Selected evidence

Includes only the tabs, fields, snippets, or references needed for the task.

04

Instructions & notes

Keeps intent, constraints, deadlines, and decision criteria beside the work.

05

Stateful resume

Restores scroll, selection, and safe page context where supported.

06

Completion trail

Links the result, decision, and follow-up back to the original handoff.

05
Where it wins

Best use cases

  • ✓Approval and verification tasks
  • ✓Customer record updates
  • ✓Cross-team operational handoffs
06
What the user gets

Expected outputs

  • →Context-rich task link
  • →Saved route and page state
  • →Completion trail and result
Business value

What changes for the team

  • ↗Reduce the time teammates spend rebuilding context
  • ↗Make asynchronous browser work easier to assign and verify
  • ↗Keep decisions connected to the page state that informed them
Built for control

Safe by design

  • ✓The sender chooses exactly which context is included
  • ✓Credentials and restricted page data are never packaged as task content
  • ✓Access, expiry, and recipient permissions can match the task
Why TaskTwin is different

TaskTwin hands off a working state, not just a sentence—turning browser context into part of the assignment itself.

One shared technical foundation

Powered by the Browser Session Engine.

TaskTwin consumes the same structured DOM events, timeline, context, snapshots, and safe execution primitives as the rest of TabTwin—without requiring another extension.