Settings is one left rail: eight workspace pages above the list of projects. Every row is a live control, a readout of a fact, or a stub drawn with the default Grid Console ships and a dashed chip saying what it waits on.
Open it with ⌘5, or from Settings at the foot of the sidebar. The eight pages, in rail order:
| PAGE | WHAT IT HOLDS |
|---|---|
| General | Where files live, blast radius, schedule. |
| SDLC | The workflow: stages, arrows, gates, who approves, card types. |
| Agents and models | Provider, budget, the model matrix. |
| Accounts | The provider logins a card can bill to, and the pools they sit in. |
| Editor | Font, size, rulers and card preferences. |
| Appearance | Theme and text size. |
| Keymap | Every command and its keys. |
| Plugins | Bundled, installed and registry plugins, and trust. |
Six groups. GENERAL is readouts: FILE STORAGE prints the workspace's state folder and WHERE MEMORY LIVES the project memory folder. SAFETY holds the one control the page was built for, BLAST RADIUS: the workspace default for what a card may touch (git worktree, branch in place, no branch), inherited by every project that has not chosen its own. SCHEDULE has three live controls, SESSIONS AT ONCE, PAUSES FIRST and PAUSE FROM, and a RECURRING readout. One schedule control sits elsewhere: a column's own cap, how many sessions may be live in that column at once, is set on the board's column header beside the count it caps, and Limit agents on the board head is the master switch over all of them. The switch is off in a new workspace, so a stored cap is remembered and drawn and refuses nothing until it is on.
Arrives with the public beta. NOTIFICATIONS (push me when, quiet hours, grouping), BUDGET (soft cap per day, spent this week, hourly rate) and MEMORY & CONTEXT (inject into every agent, context budget, compact closed cards, keep transcripts).
The page the workflow plugin contributes. WORKFLOW PROVIDER names the plugin that owns the stages; switch it off and the page empties with the reason. STAGE APPROVERS picks the roles allowed to move a card out of Prepare or Review. Below them is the rail: every stage as a tile with its model role, and the arrows between them.
A stage opens its contract: scope, stage N of however many the workflow has, and MODEL ROLE as a readout, since the role a stage draws from is fixed by the stage and what each role resolves to is set on Agents and models.
An arrow opens its detail: whether it hands the card to a fresh agent or keeps the one running, AGENT ON THIS ARROW, and MUST BE TRUE TO PASS, the gates the arrow states. The agent's prompt, its model role and its card-type variants are edited on the Agents page, and Edit on the Agents page › goes there; see agent definitions.
Under the rail sit DEFAULT PROFILE (the provider new cards run on) and CARD TYPES, the workspace's table of types and the stages each walks, including your own. See Workflows.
| CARD | WHAT IT DOES |
|---|---|
| AGENT PROVIDER | A real probe of this machine's PATH. Claude Code and Codex are selectable when found. A plugin-contributed provider, such as Copilot, gets a row too, and it is selectable once its binary is found on PATH, its plugin declares a spawn contract, and a person has approved that binary to run. Installing the plugin alone leaves its row unselectable. |
| COMPUTE BUDGET | Economy, Balanced, Quality or Maximum, for the whole workspace. |
| THE THREE ROLES | Four difficulties (easy, normal, hard, very hard) by three roles (research and planning, implementation, delivery and validate). Every cell is a model and an effort; click to cycle. A fourth column switches adversarial review per difficulty. |
| DYNAMIC WORKFLOW | The agent cap for cards at ultracode effort (5, 15, 40 or no cap), and whether an agent may drop to a smaller model on a simple step. The cap is shown at capture but not enforced yet. |
| GRID INTELLIGENCE | The model behind titles, summaries and explanations. |
Non-Claude rows on GRID INTELLIGENCE are drawn with their reason and are not clickable. See Models.
A card can pin a model, an effort, or both, one stage at a time, over Prepare, Doing, Review, Deliver and Verify; a stage that names only an effort keeps the matrix's model, and a stage the card says nothing about takes the table. The difficulty ladder on a card carries a fifth tile, Custom, for exactly that: it lights while the card holds any pin and is never a rung you pick, so a card reads Hard and Custom at once.
The registry of provider logins a card can bill to. An account is one login in a config root of its own (CLAUDE_CONFIG_DIR for a Claude account, CODEX_HOME for a Codex one), so two accounts are two separate credentials rather than two views of one. Primary is the row that sets no variable at all and means each CLI's own default home.
REGISTERED lists them and marks the workspace's active account, which is what a thread or a card that has pinned nothing resolves to; a card pins its own from the account chip in its session header or from the card sheet's ACCOUNTS tab, and can only bill to an account of the provider it runs on, or to Primary. ADD AN ACCOUNT names a new one and prints the sign-in command for you to run in a terminal, because Grid never handles a provider login itself.
POOLS is where pools are made. A pool is a named set of accounts a project's cards take turns on, round robin, skipping a member that is held and picking it up again once the hold lapses. A project chooses its pool on its own Settings tab, and a pool holds one billing type. The card is disclosed only once a second account is registered: with one account the word "pool" appears nowhere on the page. See providers.
Live on Editor: Font, Size and leading and Rulers, stored on this machine; Click outside closes them; Rewrite long titles and Start new cards immediately, stored in the workspace because the daemon acts on them. SYNC exports theme, editor preferences and rebound keys to a JSON file and imports them back.
Appearance: Theme is live, with four themes: grid dark, dusk, grid light and high contrast. Text size is live, the same base size the status bar's − and + move, with chips from 11 to 17.
Keymap is one table. Every command is rebindable: press change, then the keys; Esc leaves it as it was, and conflicts are shown. The Grid chip puts every key back.
Arrives with the public beta. The VS Code, IntelliJ and Vim presets are drawn but inert: one keymap is built.
Pick a project in the rail and you get two tabs, Settings and Memory. Settings holds these groups:
| GROUP | ROWS |
|---|---|
| CODE | REPOSITORY, BASE BRANCH per repo, BRANCH PER CARD with a per-repo override. |
| COMMANDS | A readout over grid.toml: where it lives, with edit…, and one row per repo with its commands, port and coverage as N of 4. |
| VERIFICATION | The verify command, saved on blur. BROWSER says whether this machine has the Claude in Chrome pairing. |
| DELIVERY | HOW WORK LANDS has four chips (Push the branch; Push the branch, open a PR; Merge, don't push; Merge, then push), with per-repo overrides, and WHEN (at Deliver, at Verify). A project that has chosen neither reads NOT SET: the first card to reach Deliver asks you once, records the answer with grid project delivery <name> branch|pr|local|push, and it is the project's from then on. Push the branch commits on the card branch and pushes that branch, merging nothing and opening nothing; Merge, don't push commits on the card branch and merges it into your checkout with nothing pushed. Any of the four can be changed at any time, mid-card included: live sessions are told. |
| SAFETY | ANSWERED HERE, the permission answers this project's cards have minted. |
| SCHEDULE | SESSIONS AT ONCE for this project and a RECURRING readout. |
| VISIBILITY | IN THE RAILS: shown or hidden. A hidden project leaves the top rail, the board, capture, the code view and the phone; its cards, sessions, memory and settings stay, and it stays in this page's project list, dimmed, so it can be shown again. |
ANSWERED HERE is every answer you gave at a permission prompt on one of this project's cards, with a Revoke. A revoke deletes the record and scrubs the rule from the card tree it was answered in. It cannot reach a session already running; the row names those cards and says they keep what they were given until they end. There is no OS sandbox around a session; see Security.
The Memory tab shows the four memory files with add, edit and delete per entry, and four derived Environment rows that carry no controls.
The left column is what this workspace runs: BUNDLED, the first-party set that ships in the app, and INSTALLED, what arrived afterwards from the registry or a file. An installed row has an ON/OFF toggle and a panel for the settings its manifest declares. The right column is NOT INSTALLED, the registry catalogue minus what you already have, then AGENT & MODEL PROVIDERS and WHAT A PLUGIN MAY DO.
Trust is a chip per plugin: OFFICIAL is signed with Grid's own publisher key, VERIFIED with a key you trust, UNVERIFIED otherwise, and a broken or merely claimed signature says so. Trust publisher adds a key to PUBLISHER KEYS, after which everything it signs resolves VERIFIED. Allow unverified plugins is the workspace switch that lets an unsigned plugin load at all. A stability chip beside it says how proven the plugin is. See Plugins and installing a plugin.