Orbitrum Worker Control

Workers online — Waiting for server

ChatGPT signed in — Reading worker pages

Signed out — Waiting for detection

Unknown — No page signal yet

What “signed in” means: the worker confirmed the ChatGPT session when it connected or immediately before accepting work. A visible authenticated profile control is sufficient even when ChatGPT's compact sidebar does not expose the account name. Offline and stale observations are shown as unknown, with the last observation retained only as history.

Live inventory

Browser workers

Workers in view

Unlock as super admin for native previews

Not refreshed yet

Select a worker

No worker selected

Waiting

Native controls require the super-admin credential.

ChatGPT status unknown

Waiting for worker inventory

Expected account: —
Session verified: —
ChatGPT tabs: —
Extension: —
Worker seen: —

Working tenant No tenant selected Choose a tenant in step 02

Memberships, credentials, and apps follow the tenant you select. Not selected

People first Identity registry Create a person once, before granting access to any organization. 0 identities

Canonical people

All identities

One identity can join several tenants

Loading identities…

Organization boundary Tenants Create an organization with an existing identity as its first administrator. 0 tenants

Registry

Choose tenant

Selection scopes steps 03–05

Loading tenants…

Organization access Roles & memberships Add an identity as a member or administrator, then promote or demote it safely. Select tenant

Select a tenant first. Every role is a tenant-scoped membership.

Product access User API credentials Issue a one-time key only after the identity has the correct tenant role. Select tenant

Select a tenant first. Each user key belongs to one membership.

External app boundary Apps & callback endpoints Register each source app and its signed result-delivery endpoint. Select tenant

Select a tenant first. Source apps cannot cross tenant boundaries.

Source registry

Tenant apps

No tenant selected.

Platform identity ownership

External user links

0 links

A valid user key refreshes the current platform-user link automatically. Use this form only to correct the projection before another request arrives; historical jobs never change.

Source app	Platform user ID	Current owner	Claim evidence	Reassignment
No tenant selected.

Audited ownership change

Reassign a platform identity

Locked

Current source identity claim New tenant user Audit reason

Select a claim to review its current owner and job evidence.

Worker tenant No tenant selected Choose which organization may use this browser profile.

Tenant scope Manage users

Browser authorization Worker allocation, key & owners Bind one browser profile, authenticate it, and choose whose work it may run. Select tenant

Select a worker tenant first. Every worker key belongs to one tenant.

Active keys —

Disabled keys —

Bound workers —

Worker activation

Locked

Enable an allocated worker here to make it eligible for new work and include it on the next app start. A worker without a current access key must also receive and install a new key below before it can connect.

Select a tenant to manage worker activation.

Authentication & tenant binding

Install worker access

Locked

Select the worker you are installing. If it already has access, this issues a safe replacement for that same worker; it never reuses another worker's key.

Ownership & job eligibility

User assignment

Locked

Only tenant-bound workers appear here. Bind a configured profile by creating its worker auth key first.

Bound browser worker

Tenant-owned worker Every active user in this tenant may route eligible work here. User-owned worker Assign one owner or share this worker with several selected users.

Effective scope Choose a bound worker

No bound worker selected.

Authorization registry

Worker access keys

Not refreshed yet

Show revoked key history

One current credential is shown per worker, ordered by worker name. The public prefix is only an identifier and cannot authorize a worker. The worker selected on the Board is carried here as the install target. Confirm that target, then use Install new key; the current key remains valid until that same worker verifies the new full secret.

Worker	Tenant	Authorized by	Public key ID (not secret)	Status	Last used	Actions
Loading worker access…

Scheduling tenant No tenant selected Choose the organization whose worker pacing and capacity you want to manage.

Tenant scope View jobs

Limits apply to each worker separately. New worker-local project copies are balanced across workers that are currently eligible. An accessible copy stays with its worker through cooldown or daily limits; when the user has no accessible copy, Orbitrum balances a new one across eligible workers. Recent usage follows the browser-worker account across tenant reallocations; project counts remain scoped to the selected tenant. Startup controls are host-wide: a disabled worker receives no new work and is skipped the next time the app starts, while work it already accepted is allowed to finish.

Select a tenant first. Scheduling settings and worker usage are always isolated to one organization.

Tenant execution policy

Scheduling & pacing

Locked

These values govern future leases. Saving a change never interrupts a job that a worker has already accepted.

Cooldown between jobs

seconds

Measured from the worker’s last completed accepted job. Maximum jobs per worker per day Leave blank for unlimited. Accepted browser jobs consume the limit. Daily-limit timezone Use an IANA timezone. The daily counter resets at local midnight, including daylight-saving changes. Minimum pause between UI actions

seconds

Shortest randomized rendered-page settling window. Maximum pause between UI actions

seconds

Set the same value as the minimum to remove random variation.

Not loaded

Worker-account usage

Worker capacity

0 workers

Unlock the dashboard and select a tenant to load its current calendar-day window.

Worker scheduling capacity and recent usage
Worker	Current projects	Queued / active	Today / cap	24h / 7d / 30d	Last finish	Next eligible / status	Startup
Scheduling report not loaded.

Job configuration tenant No tenant selected Choose the organization whose job subtype prompts you want to manage.

Tenant scope View jobs

Open a job type, then open a subtype to edit its system prompt. The saved prompt is appended to future user requests for that subtype. Every job keeps the revision that was active when it was created.

Select a tenant first. Job subtype prompts are isolated to one organization.

Queued — Waiting for a worker

In progress — Leased or running

Succeeded — Worker result ready

Needs attention — Job or callback failed

JSON auto-recovered — Waiting for recovery telemetry

Autonomous recovery

Codex remediation incidents

Problem families are deduplicated and leased to one visible Codex thread rooted in the exact VS Code Solution workspace. Prompts, raw results, credentials, and callback URLs stay out of incident evidence. Select any incident for its live activity, retained history, and VS Code handoff.

— open

Problem family	Severity	Jobs	Status	Last seen	Remediation	Actions
Loading incidents…

Durable queue

Jobs

Advanced: reset saved ChatGPT project and conversation links

!

Select a tenant before resetting project continuity. Choose the organization in User management or Worker access. This action is always limited to that selected tenant.

Job	Source	User	Subtype	Project	Worker	Status	Callback	Updated	Actions
Loading jobs…

External app API

Create a project scoring job

Authenticate as an internal user, identify the source app, and send the first ChatGPT text-generation subtype.

POST /api/v1/jobs
Authorization: Bearer <userAuthKey>
Idempotency-Key: <unique request key>
Content-Type: application/json

{
  "tenantId": "<tenant UUID>",
  "appSourceId": "<app UUID>",
  "userSourceId": "<external user ID>",
  "userId": "<internal user ID>",
  "jobTypeId": 1,
  "jobSubTypeId": 1,
  "projectId": "<source project ID>",
  "projectName": "<project name>",
  "prompt": "<scoring prompt>"
}

Result delivery

App callbacks

0 apps

Loading callback routes…

Worker control

Copy this key now

Browser workers

No worker selected

All identities

Create identity

Choose tenant

Create tenant

Administrators and members

Add identity to tenant

User auth keys

Create user key

Tenant apps

Register app

External user links

Reassign a platform identity

Worker activation

Install worker access

User assignment

Worker access keys

Scheduling & pacing

Worker capacity

Codex remediation incidents

Remediation incident

Jobs

Reset saved ChatGPT routing links

Job details

Create a project scoring job

App callbacks