# Your first project

> Add a repository, open a terminal, and put a card on the board.

These five steps take you from an empty window to a card that runs something. Each step links to the page that covers it in full. Chat and agent steps need Claude Code installed. See [Installing](/docs/installing).

The first time devpit opens, it asks you about three things: **Account**, **Theme** and **Project**. The account is optional, and **Not now** skips it.

## 1. Add a project

Choose **Add a project**, then one of:

- **Open a folder**: for a repository already on this computer. devpit reads it where it is and never moves it.
- **Clone a repository**: give a **Repository** URL, and choose where it lands under **Into**. The default is `~/.devpit/repos`.

To add more projects later, use the **+** at the foot of the project rail on the left edge, or **Add project…** in the project picker at the top left. Each project has an icon in the rail; click one to switch to it, or open the picker with ⌘P (Ctrl on Linux and Windows). More in [Projects](/docs/projects).

## 2. Open a terminal

Choose **New Task → Terminal**, or press ⌘T. The terminal opens your default agent, or a plain shell. You choose which in **Settings → Providers**. Type into it, and your agent CLI behaves exactly as it always has. If you close devpit and reopen it, whatever was running is still running. See [The terminal](/docs/terminal).

## 3. Chat

Choose **New Task → Chat**, or press ⌘N, and ask something about the project. The pane's corner shows what the conversation has cost so far. See [Chat](/docs/chat).

## 4. Put a card on the board

Open **Board** in the sidebar. A new project gets six columns: `inbox`, `refine`, `review`, `doing`, `check` and `ship`. None of them runs anything yet. Press **+ Add card** at the foot of a lane, type a title and press Enter. The field stays open for the next card. Click a card to open it. See [Columns and cards](/docs/board).

## 5. Give a lane a step

Each lane header has a step badge that reads **no step**. Click it, choose **New step…**, and pick a kind:

| Kind | What it is for |
|---|---|
| **Command** | Your tests, a build or a deploy. |
| **Agent** | One headless turn. It needs a **Spending cap (USD)**, or it does not run. |
| **Session** | A session you drive in the terminal. |

Now drag your card into that lane. Moving a card is what starts the work. The card's **Runs** list shows what happened and what it cost. See [Steps](/docs/steps) and [Runs and cost](/docs/runs).

<!-- Screenshot — a card in a lane whose step badge names a command step. -->

After the step finishes, the lane can keep the card where it is or move it on. Nothing moves on its own until you set the lane to do that. See [Moving cards](/docs/moving-cards).
