---
title: Your first session
description: A first session from start to finish, from a sentence to a merged pull request.
url: https://docs-v3-preview.elastic.dev/getting-started/first-session
---

# Your first session
This walks through one task from start to finish. Each step links to the page that covers it in full.

## 1. Describe the task

Press `o` and describe what you want done. Heed guesses the repo from your words and recent sessions, names a branch
from the first word (`Fix …` becomes `fix/…`), and shows the command it will run. `⌘↩` starts it.
![The Start work dialog with a prompt typed, docs-builder guessed, and the branch named fix/broken-anchors-redirect-pages](https://docs-v3-preview.elastic.dev/images/shots/getting-started/first-session-1-start.png)
Heed makes a git worktree for the branch, opens a session for it, and starts the agent on your prompt.
More in [Start work](https://docs-v3-preview.elastic.dev/start-work).

## 2. The agent works

The session's agent runs in a real terminal. Its state, here **working**, comes from the agent itself through hooks,
and sorts the session in the sidebar.
![A working session: the agent's output in the left pane, a shell beside it](https://docs-v3-preview.elastic.dev/images/shots/getting-started/first-session-2-working.png)

## 3. It needs you

When an agent wants permission or asks a question, its session moves up under **Needs you**, and the Dock and the
menu bar show how many are waiting. `ga` jumps to the next one.
![A blocked session: the agent asks permission to run dotnet publish](https://docs-v3-preview.elastic.dev/images/shots/getting-started/first-session-3-blocked.png)

## 4. Answer it

Press `i` to type into the agent: the pane taking your keys gets a white border. Answer, then `⇧⎋` to give the
keyboard back to Heed. More in [Typing into agents](https://docs-v3-preview.elastic.dev/sessions/typing-into-agents).
![The agent pane in INSERT, outlined white](https://docs-v3-preview.elastic.dev/images/shots/getting-started/first-session-4-insert.png)

## 5. Review feedback goes back to the agent

When the agent opens a pull request, the session tracks it. Review comments and failing checks queue up in the PR
overlay (`go`) and go back to the agent when it is idle. More in [Review feedback](https://docs-v3-preview.elastic.dev/github/review-feedback).
![The PR overlay: two items queued for the agent, the prompt that will be sent](https://docs-v3-preview.elastic.dev/images/shots/getting-started/first-session-5-feedback.png)

## 6. Done

When the pull request is merged, the session moves to History with its outcome. Its prompt, timeline and agent session
stay there, ready to reopen. More in [History](https://docs-v3-preview.elastic.dev/history).
![History: closed sessions grouped by day, with their outcomes](https://docs-v3-preview.elastic.dev/images/shots/getting-started/first-session-6-history.png)