Settings, keymap and themesGrid Console is meant to behave like a premium IDE: everything visible is configurable, per workspace, and the parts that are not settings are plugins.GeneralSETTINGNOTESStorage locationWhere cards and plans live. Default ~/.grid/<workspace>.Working directoryThe folder projects are discovered in.Text sizeOne base size drives every font in the console. Raise it once for a 4K panel; the whole hierarchy scales with it.Modal behaviourWhether clicking outside a diff or plan modal closes it.NotificationsWhich decisions notify, and how quiet progress stays.
Editor and languageFont family and size, ligatures, tab width, whitespace rendering, word wrap, minimap, folding defaults, and per-language overrides. Language support is tree-sitter for structure and your existing language servers for symbols, so Go, TypeScript, Python, PHP, Rust, YAML, Markdown and Dockerfiles behave the way your IDE already taught you to expect.KeymapFour presets: Grid, VS Code, IntelliJ, and Vim (as a plugin). Every command is rebindable, conflicts are shown, and a plugin can register new commands into the same table, so a keybinding you learn does not stop working because a plugin added a feature.ThemesFour built in: Grid dark, Dusk, Grid light and High contrast. High contrast is tuned so stage colour is never the only signal. Themes are plugins: a theme is a token file with a name, and marketplace themes that fail AA contrast on body text are rejected.Per projectAutonomy level, workflow document, stage contracts, deliver mode, model and effort defaults, the command map of what can and cannot run, MCP servers, and which plugins are enabled. Project settings win over workspace defaults, and Crew can lock a per-seat cap that a project cannot exceed.