Attach Desktop / Your Company HQ
Your Company HQ
OpenClaw handoffs, private computers, manual approvals
Chief of Staff
Researcher
Builder
Reviewer
Publisher
Research
ready
Build
waiting
Review
queued
Publish
locked
Recording take
Prepare the new offer launch. Research the market, draft the page, review it in a browser, and prepare the final checklist. Ask before anything goes live.
Chief of Staff
I will keep HQ as the room, route work to named workers, and hold deploys plus paid actions for approval.
First visible workflow
Research
Researcher
Gather source notes, customer pain, and competitive context.
Build
Builder
Draft the page, brief, asset, or workspace the customer asked for.
Review
Reviewer
Open a worker computer to check sources, browser state, and claims.
Publish
Publisher
Prepare the final launch checklist. External actions stay locked.
qa-computer
Remote desktop · review-01
assigning
company-workspace.local / launch-brief
Launch review
Reviewer checks the customer launch away from your laptop.
Source notes are saved
Page draft works in a browser
External actions stay locked
Brief
launch-brief.md
Page
offer-page.png
Checklist
approvals.txt
F
B
F
T
waiting for provider assignment
view session minted only when requested
Live status
waiting for task
A2A not sent
computer unassigned
view locked
Live controls
Assign the task, open the worker computer, then request approval.
Approval gate
The team can prepare work across repos, browsers, and tools. Production deploy, sharing, and paid actions stay locked until the supervisor approves.
Production deploy
manual approval
Paid actions
manual approval
Credentials
per worker
Message Your Company HQ
What the page shows
A familiar room
The interface starts as chat, with named workers instead of disposable threads.
Visible handoff
Chief of Staff delegates work through OpenClaw sessions_send.
Worker computer
A reviewer gets an isolated machine in Box or customer-controlled cloud.
Locked launch
Deploys, credentials, and paid actions remain approval-gated.