Skip to main content
Ten minutes, end to end. The TUI and cortex exec run on the Cloud Code runtime by default, so a fresh install completes a turn without any extra configuration.
Cortex CLI first-run tips panel above the empty composer

First run: the welcome splash and four tips — /model, @ files, Shift+Tab to cycle Agent / Plan / Ask, Ctrl+x for shortcuts and F2 for settings.

1

Install

Then cortex --version. Details and options: Install.
2

Sign in

The browser opens; approve the sign-in. cortex whoami confirms it. No browser on this machine? cortex login --device-auth. See Sign in.
3

Start a session in your project

The session view opens: a timeline, a composer at the bottom, and a footer with the model and mode — Cortex Mini 1 · Agent. Type what you want changed and press Enter.
Cortex works through the request as a series of tool calls — searching, reading, editing, running commands — and each appears on the timeline as it happens. Press Esc to interrupt a turn that is going the wrong way.
Cortex CLI thinking on a prompt, with Add a follow-up — Enter to queue in the composer

A turn in flight: Thinking with the elapsed time, and a composer that already accepts a follow-up to queue.

4

Tell Cortex about your project

Writes an AGENTS.md in the current directory. Cortex reads it at the start of every session, so put build commands, test commands, house style, and anything a new contributor would need there. /init does the same from inside the TUI.
5

Choose how much autonomy to grant

Every session runs under an approval policy and a sandbox. By default Cortex asks before it does anything consequential. Press Shift+Tab to cycle Agent → Plan → Ask, use /permissions to pick Read-only, Smart, or Full access, or set it up front:
See Modes and permissions.

​
Other ways to start

The TUI needs a terminal on both stdin and stdout. In a pipeline or a CI job, use cortex run or cortex exec.

​
Where to go next