Find your way around Cook

Cook has two apps. The Cook CLI runs in your terminal, and Let Cook is the desktop app for Windows, macOS, and Ubuntu. Both work with your local projects…

The Cook CLI supports browser login, API keys, enterprise single sign-on (SSO), and external auth providers for automation. This page covers the CLI. In L…

Reference for key bindings in the Grok Build TUI. Bindings are built in and cannot currently be remapped.

Headless mode runs Cook non-interactively from the command line. It accepts a single prompt, executes it with full tool access, and returns the result. Us…

Agent mode runs Cook as a long-lived server that clients talk to over ACP (JSON-RPC). Use it from IDEs, SDKs, eval harnesses, and custom apps. For a one-s…

Let Cook is Cook's desktop app for Windows, macOS, and Ubuntu. It gives you a chat window for working in a local project, with a session list, model setti…

Type / in the prompt to open the command menu. It fuzzy-matches as you type, and picking a command runs it immediately.

Use cook --help for the options in your installed version. Use cook --help for a command's details. This page lists the main commands and common options.

Subagents are independent child sessions that handle tasks in parallel. Each subagent has its own context window, so the main agent can delegate work (res…

Cook saves every conversation to disk automatically. Whether you work in the TUI, in headless mode, or over agent stdio, Cook records the exchange as a se…

Plan mode is a structured planning phase: the agent explores the codebase and designs an implementation approach before writing any code. Use it for tasks…

Cook runs long-lived processes without blocking the conversation. This document covers background commands, the /loop command, the monitor tool, and the s…

Use a goal for a long task, plan mode when you want to review steps before code changes, and compaction when the conversation is getting large.

Cook reads settings from config files, environment variables, and CLI flags. This page covers the common options. The field list for config.toml, managedc…

Cook draws all TUI colors from a central theme. You can switch themes while Cook is running, follow your operating system's light or dark appearance, and…

MCP (Model Context Protocol) servers extend Cook with external tool integrations. They let Cook interact with any service that implements the MCP standard.

Skills are reusable prompt packages that extend Cook with task-specific instructions. They let you capture a repeatable procedure once, instead of re-expl…

A plugin bundles skills, slash commands, agents, hooks, and MCP servers into one installable unit. You get plugins from a marketplace, install the ones yo…

Hooks let you run a script or send an HTTP request at key moments in a Cook session. Use them to automate tasks, enforce safety checks, log activity, send…

Cook connects to custom model endpoints for alternative providers, self-hosted models, and overriding built-in settings. This guide explains how to select…

Project rules let you configure Cook per project or directory. By placing an AGENTS.md file in your repository, you can set coding conventions, build inst…

Memory lets Grok recall facts, decisions, and patterns from earlier sessions. Grok indexes the information you save and searches it automatically, so a ne…

Sandbox mode restricts what the agent process and its spawned commands can access on your filesystem and network using OS-level kernel primitives (Landloc…

Control what Cook can access and do: permission modes, allow/ask/deny rules, hooks, and the optional OS-level sandbox.

An optional row at the bottom of the pager — above the shortcuts bar in the full screen, under the prompt's info row in minimal mode — and disabled by def…

This file ships with the CLI and is extracted to ~/.cook/docs/user-guide/26-config-reference.md on launch. It is the complete field list for config.toml,…

Cook runs as a full-screen TUI. It relies on terminal support for color, clipboard, keyboard input, mouse input, and full-screen display. Terminals, multi…

The Agent Dashboard lists every top-level session in this pager process — local sessions and forks — grouped by state. From one screen you can peek, reply…

Status: alpha. The schema below is versioned (grokcode.schema.version = v1); additive changes may occur without notice, renames/removals will bump the ver…

grok clone fetches a Git repository into a Grove content store and mounts a projected working tree (NFS on macOS, FUSE on Linux). Each invocation reads GR…

Cook injects a set of model-facing prompt templates: the plan-mode reminders, the goal templates, and the built-in subagent bodies. Each one ships as the…