Activate a device
On the gateway host, create a one-time code:Profile and sessions
The account area lets you edit the display name, nickname, and avatar. It also lists active sessions with their device name, platform, last-seen time, and current-session marker. You can sign out the current session or revoke another device. Revoking a session does not remove the principal or its workspace memberships. A suspended or removed member loses access through the gateway and active sessions are terminated. The gateway sends an access-expiring event before an access credential expires. Clients refresh in the background when possible. If a session is revoked or refresh fails, the app returns to gateway activation instead of retrying a credential indefinitely.Invitations
An invitation grants a role and one or more workspaces. It is tied to one gateway and expires. The recipient can preview the gateway name, inviter, role, workspace list, expiry, and transport before accepting. To join:- Open the invitation link or paste its code into the app.
- Check the gateway and workspace details.
- Enter the profile and device name for the new installation.
- Accept the invitation.
Members and workspaces
Members are managed at two levels. Gateway member administration controls a principal’s lifecycle. Workspace membership controls which workspaces that principal can use. Depending on your capabilities, the administration screen can:- list members and their role presentation;
- suspend or restore a member;
- remove a member;
- create an activation for a member’s additional device;
- add or remove a member from a workspace;
- create, inspect, revoke, and accept invitations.
Collaborative threads
Thread access and thread participants are separate from workspace membership. A collaborative thread can have a participant list that is narrower than the workspace. Owners and authorized managers can add or remove private participants; ordinary members see only what the gateway allows. In a shared thread, each submitted message can run as independent background work. The composer remains available while the task runs. A task card links the request to its child conversation, shows progress, and delivers the result back to the originating thread. Message mode is for collaboration rather than agent tool orchestration. In that mode, Pioneer hides skill and MCP controls and keeps the message flow focused on people. Replies and mentions let a participant point to a specific message or another principal without copying the whole conversation into the text.Message history
Your own messages can be edited or deleted when the thread capability allows it. Revisions are kept as a separate history so clients can show what changed without rewriting the timeline’s identity. A read cursor records how far a participant has read and can be synchronized across devices. The timeline also preserves agent authorship. A message or task written by an agent shows the presentation captured when that work happened, even if the agent is later renamed or retired.Notifications
Task results can be delivered back into a thread or to your durable task notification inbox. The inbox lets you find completed, failed, blocked, or review-required work after the original thread is no longer open. Acknowledge a notification after the result has been seen; acknowledging it does not delete the task or its result. Access changes, invitation changes, member changes, participant changes, message edits, deletions, and read-cursor updates arrive as live events. The app reloads the affected projection when an event arrives, so a second device sees the same gateway-owned state.Further reading
- Identity, authentication, and authorization explains sessions, capability snapshots, and access invalidation.
- Conversation timeline explains task cards, replies, mentions, revisions, and live work.
- Workspace explains workspace selection and scope.
- Permission modes explains approval behavior inside an authorized turn.
- Authentication and access API lists the corresponding JSON-RPC methods.