Settings

Settings opens from the bottom of the channel list, below the channels themselves, and it opens on your profile. Its left column carries two groups, and the split between them is the whole model: My settings is personal to whoever is signed in, and Account, below it, is the workspace.

Each Account pane is opened by its own permission rather than by one role, and a pane you may not open is absent from the column rather than shown and disabled. The panes you see are the ones you hold, so a colleague seeing fewer than you holds fewer — the column does not say which are missing. See Roles and permissions .

The panes #

Planned Five of the ten panes hold nothing yet.

My history, Providers, Connections, Credits and billing and Integrations each open on a blurred picture of the pane, one sentence, and a disabled Coming soon control. What the table records against those five is what the pane is designed to hold, not what it shows today.

Roles and invitations are not a pane of their own: Directory carries the roster, the seats it consumes and the invitations that have been sent and not accepted, in one place.

What sits behind four of them #

My profile carries the display name, the bio and the avatar, and under them the sign-in methods: GitHub, Google and Microsoft each show either the account they are connected as or an invitation to connect one.

Planned My history holds no sessions yet: the pane reads Every session you run will land here, ready to replay. above a disabled Coming soon control. What it is designed to hold is a member’s own record and nobody else’s: a Session history list — Rewind any terminal session and watch it pour again — grouped by when each session ran, with an Export all control above it. Each session carries its start time, a status of Completed or Error, a duration, a count of the commands it ran, and the first of those commands. Opening one plays it back: an action log of every command, searchable and filterable by the kind of command, against a scrubber with a speed control.

Appearance carries five theme modes — System, Warm paper, Ember, Aurora and Matrix — each previewed as a miniature terminal rather than a colour swatch, and below them density and the agent avatar set. Density is How tight the workspace packs — type, rows, and spacing scale together. across three steps: Compact, Default and Comfortable. The four avatar sets keep one colour per discipline, so changing set never changes which colour means which kind of work.

Providers and Integrations are two different things with similar names. Planned Neither pane holds a row yet: Providers reads Connect a compute provider, then choose where each run lands. and Integrations reads Connect GitHub, Linear, Slack and the rest, and keep their keys in one place. above a disabled Coming soon control. What they are designed to hold differs. Providers holds the machines the workspace runs on: Cloud, Docker, Kubernetes and SSH, each reading Connected or Not connected. Integrations holds the outside tools that back a surface, grouped by what they are for — source control, project management, communication, monitoring, and the model provider behind the agents.

What Settings does not carry #

Settings is workspace chrome. A channel’s own configuration — its members, its Access policy, its signal dial, its enabled surfaces and its archive control — is in that channel’s settings pane, not here, and is set per channel.