PRIVATE EXPERIMENT · PUBLIC OVERVIEW
EXPERIMENTAL CLIENT · PRIVATE PREVIEW

Keep agent work
findable, answerable, recoverable.

DELEGATOR is an experimental Go server, CLI and local UI for coordinating independently started Codex and Claude Code sessions. The temporary board was privately checked over loopback and managed connection-bound SSH. Native tools keep their own execution, identity and sign-in.

Explore the architecture ↓
CURRENT STAGE · Private experimental preview v0.1.0-preview.1 Last updated · 21 Oct 2026
01 / SYSTEM SHAPE

One shared board.
Execution stays close to home.

The Go server owns the temporary board. The CLI speaks to it. The local UI is read-only: manually refreshed central reachability, declared capabilities and explicitly registered session references. The explicit, scoped sessions-list metadata adapter is implemented. Independent background discovery, transcript parsing, native import/control and allowance enforcement are unsupported or not implemented.

FIRST-SLICE SHAPE · INLINE SVG
GO SERVER · TEMPORARY BOARDCoordination boardtasks · questions · policyBoard data & receiptsstored · received · acceptedENROLLED MACHINEGo CLI clientRegistered session referencesUSER INTERFACELocal UI · configConnection viewCredentials and provider permissions stay with each local user and native tool.
Board service · CLI client · local UI connection/config view
IMPLEMENTED · EXPERIMENTAL

Go server + temporary board

The experimental Go server stores the temporary board and receipts. It is being validated privately over loopback and SSH; production is not deployed.

IMPLEMENTED · EXPERIMENTAL

CLI + local UI

The CLI registers session references and sends envelopes to the board. The explicit, scoped sessions-list metadata adapter is available by CLI opt-in. Independent background discovery, transcript parsing, native import and control remain unsupported. The local UI manually refreshes central reachability, declared capabilities and explicitly registered session references. It is read-only and does not auto-poll.

IMPLEMENTED · READ-ONLY

Connection view

The local UI is read-only and manually refreshed. It shows central reachability, declared capabilities and explicitly registered session references. It does not auto-poll; registration is not a heartbeat or live-runtime signal. On the installed Windows PC only, the local dashboard opens at http://127.0.0.1:8766/.

BOUNDARIES BY DESIGN

Coordination can be shared.
Authority stays local.

Permissions: membership grants no access to another person's account or unrelated sessions. Each participant has a separate runner identity and approved roots.

Credentials: provider sign-in remains in supported native flows. Tokens and auth stores do not enter shared state or telemetry.

Session import: discovery, parsing and native live connection are separate statuses. Session import is proposed, not shipped.

REL01 · v0.1.0-preview.1 · RELEASE LIVE

Install the experimental client

Private preview v0.1.0-preview.1 is live. Release assets and isolated installation/operation checks passed; authenticated release download and checksum verification passed for all four curated assets. The build is unsigned and experimental. It includes a compiled per-user Go binary: no Node runtime, administrator rights, global PATH, service or firewall changes. No board token or private connection profile is bundled. The Windows ZIP is 4,278,933 bytes (SHA-256 5a747969d0d49bda7f18464a72c41eb4f850b48a2bb37ac4d0a7b460bb4fdcda); the Linux TAR is 4,053,451 bytes (SHA-256 7273394d4e8ac4f1790d8638757ea6cf5ba49cfa7e1b3dc8abb64a0552bccd40). Source revision: 908748b78cf163bc99336d0ea5e922287ce7ac38.

Download from the private GitLab release

WINDOWS · ZIP

Install for your user

  1. Download and extract the Windows ZIP to a folder you own.
  2. Double-click Install DELEGATOR.cmd. It installs under your user profile.
  3. Double-click Open DELEGATOR.cmd to start the app and open its dashboard.
  4. Use Status or Stop DELEGATOR.cmd to inspect or stop the owned app.

No administrator rights, Node, PATH, service or firewall changes.

LINUX · TAR.GZ

Install the worker CLI

  1. Download and extract the Linux archive.
  2. Run ./delegator install as your user.
  3. Use ~/.local/bin/delegator-client/delegator, or invoke ./delegator directly.
  4. On headless workers use app start, app status and doctor.

The installer does not modify PATH. No Node or administrator rights.

Initially disconnected: the archive has no token or connection profile. Existing private profile provisioning is separate. The managed route uses connection-bound SSH stdio (`-W`); it creates no local forwarding listener and has no fallback. Do not add a real token to commands, screenshots or public docs. Missing credentials or SSH must remain an explicit unknown/error and must never start provider inference.

Check status and optional native metadata

Run commands from the extracted or installed folder. On Windows use .\delegator.exe; on Linux use the full installed command path.

delegator --help
delegator client --help
delegator app status
delegator doctor
# Explicit, bounded metadata inventory only:
delegator sessions list --provider codex --executable ABSOLUTE_CODEX_PATH --limit 20
# or --provider claude --executable ABSOLUTE_CLAUDE_PATH

Native inventory is opt-in and lists whitelisted metadata only; it does not auto-register or upload sessions. Native live activity remains unknown. Discovery outside this explicit inventory, transcript parsing, native import and launch are unsupported. The local UI is read-only and manually refreshed, with no auto-polling. Registration is not a heartbeat.

For current flags, token-file handling and rollback notes, see the prototype README quickstart.

02 / PROGRESS

What is known
and what is still a bet.

OBSERVED

Native question transports

Bounded Codex and Claude answer/action paths were demonstrated in disposable fixtures. This does not prove a complete coordinator or universal observer.

Evidence →
IMPLEMENTED · EXPERIMENTAL

Installable Go client preview

An installable per-user Go client includes CLI and a read-only, manual-refresh local UI. Isolated package installation and smoke checks passed; authenticated release download and checksum verification passed for all four curated assets. The UI displays central reachability, declared capabilities and explicitly registered session references, with independent observed/stale/unknown evidence age; it does not auto-poll. Registration is not heartbeat or proof of runtime activity. The temporary board passed bounded private loopback and managed connection-bound SSH checks; no production service is deployed.

PROPOSED

Allowance-only admission

Allowance-only admission is planned. Allowance collection and enforcement are not implemented; usage statistics are not an admission gate.

UNSUPPORTED

Cross-device live import

The explicit scoped sessions-list metadata adapter is available; independent background discovery, transcript parsing, native import and control remain unsupported. Native runtime activity remains unknown.

REL01 · VERIFIED INSTALLATION

Per-user install checks passed

WINDOWS

Isolated install, offline read-only UI, repeat start, wrong-nonce rejection, stop/restart, upgrade and manual removal passed. User ACL checks passed.

LINUX WORKER

User-local install, app start/restart, doctor and status passed. The existing board baseline stayed unchanged.

RELEASE REVIEW

Independent review cleared the source after two fixed bugs. 39 test entries included 2 helper fixtures. Authenticated download verification passed; checksums matched for all four curated assets.

RECENT BOUNDED VALIDATION

Repair accepted after baseline rejection

REJECTED

The initial five-task-turn baseline was rejected for missing substantive results.

ACCEPTED

A bounded two-turn repair was accepted, following 7 task activations, 1 setup activation and 1 failed auth-mode attempt.

CHECKS

15 Go top-level checks plus vet passed for UI/help; integration checks passed 10/10.

Counts describe the bounded scenario only. They are not a savings claim or a general performance benchmark.

OBSERVED NATIVE METADATA · OPT-IN

Inventory results are not runtime status

WINDOWS CLIENT

Codex returned 20 metadata entries with partial=true; Claude returned 1. Inventory is explicit and bounded.

LINUX WORKER

Codex returned 2 entries; Claude returned 0, with partial=false.

UNKNOWN

Native live activity remains unknown. Metadata listing does not establish whether a session is active, waiting, complete or resumable.

RECEIPTS ARE NOT ACCEPTANCE

Three separate states

SERVER STORED

The board has durably recorded the envelope.

RECIPIENT RECEIVED

The intended participant or client has received it.

WORK ACCEPTED

The recipient has explicitly accepted the task. Storage or delivery alone is not acceptance.

03 / EXPERIMENT LOG

Evidence first.
Numbers only when measured.

Findings load from a small JSON file. The publication state starts pending; no unverified metrics are shown.

Open experiment findings →
LIVE FINDINGS
Pending
Waiting for reviewed, sanitized results.
Source: experiment-results.json
04 / DECISIONS & TRADEOFFS

Keep the first boundary small.

Board decides; provider runs

The board stores coordination state. Provider execution integration remains unimplemented; native tools retain authority for execution, sign-in, prompts and pending-request validity.

PLAN

Allowance gates the next turn

A hold delays the next managed turn; it does not stop work in progress. Explicit user overrides bypass the soft reserve only, never hard limits or another user's permissions.

PLAN

Unknown stays unknown

Windows may be missing or stale. Show evidence age and reason; hold affected automation until resolved.

PLAN
NEXT EXPERIMENT · PROPOSED

Replace manual orchestration with explicit contracts

PROPOSED

Discoverable CLI / MCP

Define typed, discoverable commands and a versioned result-content schema so callers can inspect capabilities and validate outcomes.

PROPOSED

Separate context from reply

Keep context_ref (what the task is about) distinct from reply_to (where the answer must go) in messages and receipts.

PROPOSED

Bounded event wakeups

Use event-driven notifications to wake a coordinator when useful state changes, with explicit limits and no polling loop. No time or usage savings are claimed.

NEXT CHECKPOINTS

From bounded proof
to trustworthy tool.

  1. Observe Versioned, sanitized allowance and usage records.
  2. Hold Shared admission gate and durable inspectable jobs.
  3. Override & release User authority, expiry, concurrency and crash recovery.
  4. Prove integration Disposable start/hold/release receipts per provider.