Settings
Settings at /settings is where a workspace is configured. It is one shell
with a tab rail grouped into six sections; a tab is addressable directly with
?tab=, so every deep link below opens straight onto it.
Most tabs are workspace-scoped. Two — Organization and Members — act on the organization above the workspace, and Billing on its subscription. Nothing here is instance-wide: instance administration lives in the separate owner console.


The rail
Section titled “The rail”| Section | Tab | What it governs | Goes deeper |
|---|---|---|---|
| Workspace | Workspace | Name, autonomy level, debug ceiling, the system-LLM credential, onboarding | Set the autonomy level · Use debug mode |
| Organization & members | Organization | The organization above this workspace: name, SSO, invitations | Configure OIDC SSO |
| Runner | The runner fleet available to this workspace — organization-owned, rented and (for an instance admin) the whole fleet | Set up a runner securely · Steer and monitor runners | |
| Members | Who is in the organization, their roles, invitations and seats | Manage seats and billing | |
| Cost | Budget & Usage | The monthly dollar cap for API-mode spend, its alert thresholds and the hard stop; the subscription saturation gauges | Track usage and budget |
| Billing | The organization’s subscription and seat count | Manage seats and billing | |
| Credentials & integrations | Access credentials | Every provider credential in ONE table — API keys you supply and OAuth subscriptions you connect, told apart by a Type column | Manage secrets in the UI |
| Git | Git credentials — access tokens and SSH keys | Manage secrets · Create a project | |
| Variables | Environment variables handed to agents and code | Manage secrets in the UI | |
| Chat accounts | Linking Telegram and Discord to your account, and the per-account chat preferences | Connect a Telegram bot · Connect a Discord bot | |
| API tokens | Workspace tokens (scmt_) for an external MCP coordinator, plus its rate limits |
Connect an external MCP coordinator | |
| Agents | Models | Which models are available and the per-tier fallback chain | Handle a model quota wall |
| Agent Profiles | The saved who of an agent: model, tool tiers, checks, execution mode | Create and manage an agent profile | |
| MCPs | The capabilities an agent may reach | Create and manage an agent profile · Entitlements and tool tiers | |
| Skills | Reusable instruction sets an agent can draw on | Create and manage an agent profile | |
| Closeout | The workspace default for the ritual an agent runs at the end of a task | Configure the standard closeout | |
| Data & sync | Repo Sync | The repository this workspace round-trips through, and the conflict rules | Create a project and connect its repository |
| Shared library | The workspace-wide lib/ tree every code node can import |
Share code between code nodes |
Deep-linking a tab
Section titled “Deep-linking a tab”?tab= accepts the tab’s key, and several tabs also answer to an alias — ?tab=mcp
and ?tab=tokens both open API tokens, and ?tab=lib opens Shared library.
A link that names a tab you may not change still opens; the panel is simply
read-only.
On a phone the rail becomes a grouped index list: you pick a section, drill into a
tab, and return with the back control in the top bar. A link carrying ?tab= opens
the panel directly, skipping the index.
What is not here
Section titled “What is not here”- Instance administration — users, plans, feature availability, the marketplace review queue: the owner console.
- Per-project configuration — automation, approvals, closeout overrides and guardrails live on the project itself, in its Configuration tab. See Create a project and connect its repository.
- Memory governance — the per-scope review policy is the Governance view of Intelligence → Memory, not a Settings tab. See Manage memories.
- Your own profile and connected accounts — the user panel at the foot of the sidebar, under Edit Profile. See Sign in with Google or GitHub.