People and agents

Open Workspace settings to see everyone with continuing access, grouped under People and Agents. The presence view calls both collaborators, but never pretends they are the same.

People remain people

A person has an identity that carries across their devices. Their name and colour identify their pointer, caret and changes. A member can return to the workspace later; a participant is here now.

Inviting a person grants access only to the named workspace and the permissions shown in the invitation. It does not grant access to another workspace or to the computer hosting this one.

Agents remain agents

An agent always carries an Agent label. Its details name who added it, where it runs and which service receives data when work leaves the machine. Its changes are attributed to the agent, not borrowed from the person who started it.

Give an agent a task and the items needed for that task: read these project files, create a draft beside them, run tests in this workspace. That does not imply access to mail, browser history, credentials or another workspace.

An agent invokes the same actions exposed by apps to people, keyboard commands and assistive tools. It receives no ambient “computer use” authority and no private automation route around the permission model.

See and stop what is happening

An active agent describes concrete work: Reading release-outline.md or Running tests in Website, not “Thinking.” Open its activity to inspect the task, inputs, recent actions and permissions.

You can pause an agent, remove a permission or remove it from the workspace. A destructive action or an action outside its current scope stops for confirmation and names the affected items.

If an agent delegates work, history keeps the initiating agent and the actor that performed the change where that relationship can be verified. The desktop does not invent provenance when a service fails to provide it.

Agents are optional

No agent account is required to use the desktop, its apps or collaboration between people. Every agent-assisted route leaves an ordinary manual route. A local agent and a hosted service are labelled differently because they expose data to different places.