Install, then connect.

Start with the installation you have. The downloadable preview and the enrolled central-workspace client use separate profiles.

1. Open the private workspace

Visit delegator.haviar.xyz/workspace/ and use the owner account provided to you. There is no public self-service signup in this preview. If you do not have access, request setup from the workspace owner.

Browser sign-in is separate from device enrollment and provider sign-in. Logging in to DELEGATOR does not sign you in to Codex or Claude. Provider accounts and their credentials stay on the destination device.

2. Choose your client

Windows preview

1. Download the Windows ZIP and SHA256SUMS from the same release. Compare the archive’s SHA-256 with that entry before extraction.
2. Extract into a user-owned folder. Double-click Install DELEGATOR.cmd. Installation opens the install folder; it does not start the app.
3. Use Open DELEGATOR.cmd to start the local app and open its browser UI. Use Status DELEGATOR.cmd or Stop DELEGATOR.cmd for its lifecycle.

# PowerShell: replace the path with your downloaded archive
Get-FileHash -Algorithm SHA256 "C:\Downloads\YOUR_RELEASE_ARCHIVE.zip"

The default install location is %LOCALAPPDATA%\Programs\DELEGATOR. The compiled client needs no Node runtime, administrator rights or global PATH change. Packages are unsigned and experimental.

Linux preview or headless worker

Compare the downloaded archive with its release SHA256SUMS, extract it, then run these commands in the extracted folder:

./delegator install
~/.local/bin/delegator-client/delegator app start
~/.local/bin/delegator-client/delegator app status
~/.local/bin/delegator-client/delegator doctor

The installer does not change PATH. Use app status on a headless worker; opening a browser is optional. Stop the installed app with ~/.local/bin/delegator-client/delegator app stop.

3. Verify the right connection

A fresh preview is disconnected until the owner provides a protected connection profile. That is expected. Run delegator doctor using the exact installed executable to check safe build and connection diagnostics. The original preview profile connects to its own experiment service; it does not automatically become a central-workspace enrollment.

4. Find one real task

Choose your project board, open a task and confirm its goal and accountable owner. Link the relevant discovered session. Save a short progress note with evidence and a next action. A session title or a recently online device is not enough to establish progress.