Documentation

From install to your first completed task.

Getting started

AI Workforce has two halves. The web app is where you work and where tasks are planned. The desktop bridge is a small app on your own computer that carries out the parts of a task that touch files or run commands — and only after you approve them.

You do not need an API key

Model access is included in your subscription.

Set up in four steps

Create an account
Download the desktop bridge for your platform
Link your computer with the short code
Run a first task and approve it

Then ask for something harmless that touches the disk — listing the files in one folder, say. You should see an approval prompt on your computer before anything is read.

Link your computer

Linking connects one computer to your account. You can link up to the number of devices your plan allows, and you can revoke any of them at any time.

Open the desktop bridge
It shows a short code, single-use and valid for ten minutes.
Open the link page in your browser
Go to /link and enter the code.
Check the device details
Device name, operating system and app version.
Approve
The desktop app receives its credentials within a few seconds.

If the details look wrong

Do not approve. Close the page and cancel the request in the desktop app — the code is single-use and expires on its own.

Revoking a device

Revoking takes effect immediately. Tasks in flight on that computer stop, and it has to be linked again from scratch.

Approvals and safety

Nothing runs on your computer without an explicit approval. Three kinds of action ask separately: reading a file, writing a file, and running a command.

What you see before approving

The exact path or command, the reason the agent gives, and whether the action needs network access. Commands are never truncated in the prompt.

Example approval request

run     pandoc q3-summary.md -o q3-summary.pdf
reads   ~/reports/*.csv (3 files)
writes  ~/reports/q3-summary.pdf
network none

Rules that let an action run again apply to that computer only, and never leave it.

The task flow does not collect credentials

Operating-system passwords and keys are not part of it. If a task asks for them, deny it.

Troubleshooting

Tasks survive a closed tab. Reopen the task and its event stream resumes from the last event you saw, not from the beginning.

If a computer sleeps, its work pauses rather than fails, and continues when the desktop bridge reconnects.

If the desktop app cannot reach the control plane at all, check service status before re-linking the device.