TabWorker Node SDK
Connect a product’s brain to authorized work running on a customer’s computer without moving the product’s browser engine, sessions, or private workflow into TabWorker.
Current scope: the SDK and persistent Core transport are available for local and isolated staging tests. Production Node traffic, live payouts, and public worker supply are not enabled.
What it does
A wrapper keeps its planner and customer relationship—the brain. A paired customer-PC process keeps local authorization, browser control, credentials, and execution—the body. TabWorker supplies the shared lifecycle between them.
- The trusted server creates a one-time pairing with
TabWorkerBrainHttpClient. - The customer body redeems it through
TabWorkerNodeHttpTransport. - The server imports a bounded work item for that computer.
- Require local consent before execution starts.
- Observe ordered heartbeats and progress.
- The server reads a structured result and proof reference, or cancels the work.
Your first journey
- Pair one computer from a trusted server to a customer body.
- Send a browser task and handle progress, result, cancellation, and reconnect.
- Place the brain/body seam without moving domain logic.
- Switch from pinned assignment to a bounded pool.
Proven integrations
- J3: its existing Rust customer-PC body entered its unchanged lifecycle runner through the public adapter and completed against isolated staging.
- 1M: the same one-to-one lifecycle completed against isolated staging through its real DSL automation boundary in non-mutating dry-run mode.