Agents that work together

Accounts your agents may use on your behalf. Where a service has several accounts, agents use the default unless you name another.

Connect with someone

They become a contact of yours — a private conversation between the two of you, with agents you can bring in. If they are not on OS/A yet, the email carries the code that lets them register; either way your invitation waits for them to accept. Not a company: your contacts never see each other. Add a line of your own if you like — it is sent as written, above ours.

Whether an invitation came to anything. Someone shows as joined once they have signed in for the first time.

Every memory your agents hold, newest first. Click one to read it, see which conversation it came from, and which prompts have pulled it back out. If an agent says something you did not expect, this is where to look first.

Where every agent in this workspace starts. Any one of them can be moved on its own below.

Agents

What each agent is allowed right now, and why. Change one and it takes effect immediately — no restart.

Folders agents may reach

Agents work inside their own workspace folder. A mount opens one more directory, under a name they refer to it by — @OSA, say.

What was allowed and what was refused, most recent first, with the reason. Agents in the Semantic Security Zone are judged this way; agents at other levels appear here only when a fixed rule stopped them.

Every scheduled task across your agents — your own workspace and any company you belong to — with when it next runs. Agents set these up when you ask for something on a cadence ("check this every morning"); here you can run one now, pause it, or remove it.

Pair a machine

Run the machine client on a computer (see Downloads) and agents can do local work there — read files, run commands — sandboxed to a folder you choose. Pairing issues a token the client presents; it is shown once, here.

Your machines as one pool

Pointing an agent at a machine names one computer: it fails when that laptop shuts, and several agents asked at once queue behind each other, because a model daemon generates one thing at a time. A cluster is chosen per call instead — the member that already has that model loaded and nothing in flight. The OS/A server is a member too, so the pool is never empty.

One node per member, and a dot for every call: out with the model and why that machine was chosen, back with how long it took. Two dots in the air at once mean the work spread; a node counting more than one in flight means it queued, which is what a pool is meant to stop. A fast return is a model that was already loaded, a slow one is a cold start. Lanes trade the reason for the record: a bar per call over the last minute, which is the readable picture once there are more machines than the ring can name.

Site Agent — browser extension

Machine Agent — local client

macOS · Linux · WSL2

Windows (PowerShell)

Machine Agent (Safe) — local client

macOS · Linux · WSL2

Windows (PowerShell)

Machine Agent (Safest) — isolated container

macOS · Linux

Windows — inside WSL2

Start again — remove everything

macOS · Linux · WSL2

Windows