WARSHALL
Docs/Get started/Quickstart

Quickstart

From a fresh install to a first run. It takes a few minutes, most of them spent checking that your agent tools are installed and signed in.

Open a project

Click the project switcher at the left end of the top bar, then Open folder… at the bottom of its list. In the Terminals view the strip has an Add a Project button instead.

Any folder works, but a git repository gets the most out of the app. In a repository every terminal gets its own worktree, so several can work at once. A folder without git runs one terminal at a time.

Every project you open starts with one terminal, ready to work. Opening a folder that is already open brings it forward.

The WorkMap question

When the folder you add is a git repository without a WorkMap, Warshall offers to create one. Generate reads the git history, the README and the top level files and drafts the diagram. Not now leaves the project without one and is not asked again for that project.

To stop the question for every new project, set Settings > WorkMap > Maintain WorkMaps for new projects to Never. See Generating a WorkMap.

Check your agent tools

Open Settings with the gear at the right end of the top bar, or with Ctrl and comma. Go to the AI Providers tab. It has one tab per provider.

The CLI row shows the installed version. If the tool is missing, the row says Not installed, shows the command it would run and offers an Install button that runs it for you.

Go to the Accounts tab. If you were already signed in to claude or codex before Warshall, that sign in shows up as a linked account and there is nothing to do.

Otherwise press Link account under Claude or Codex and finish the sign in in your browser. The row updates by itself. You can link up to ten accounts per provider. API keys and OpenAI compatible endpoints have their own sections further down the tab. See Accounts and usage.

Pick a model

The model button sits in the terminal's head and shows the model with its reasoning level beside the name.

  • Click it for the list of models, then click a model to switch this terminal to it.
  • Under the models, the Effort line opens the levels that model offers, and the Account line opens the linked accounts of its provider.
  • Right-click the model button to step to the next reasoning level without opening anything.

Each model keeps its own level. See the model picker for the details.

Run a prompt

Type in the terminal and press Enter. Shift and Enter make a new line.

  • The + at the left end of the composer picks files to send with the prompt. Dropping files onto the terminal stages them too.
  • Prompts at the right end opens your recent prompts, saved prompts and skills. See Prompts and skills.
  • The run streams into the transcript. You see the reasoning, each tool call with its output, code blocks and the commits as they land.

A terminal cuts its worktree on its first run, so that run takes a moment longer than the ones after it.

Build it

Press Build on the top bar. On a project with no build script yet, the first press works out how the project builds and runs and writes one. The queue then shows each step until the project is up on its port. See the build queue.

Prompt every project at once

Press Terminals on the top bar for the view that holds every project side by side. Use the input box across the bottom to describe several tasks in one request. See the orchestrator.