---
title: "Finish a session and build"
description: "Complete a session, download the spec bundle, open it in a build tool, or hand it to your coding agent."
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.myspec.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Finish a session and build

When your specs are ready, complete the session. You can then download the
files, open them in a build tool, copy a prompt for your coding agent, or let
the agent read them straight from MySpec.

## Complete a session

Completing a session needs **Write** access on the project, like everything
else you do in a chat. With **Read** access you can still download the specs.
See [Teams and project access](/guides/teams-and-project-access/).

### A Generate session

A Generate session completes on its own after you finish the review of its last
stage. The chat then shows a **Session completed** card with the bundle name and
the number of spec files generated, plus two buttons:

- **Edit** starts a new [Edit session](/guides/edit-sessions/) for this bundle.
- **Download** saves the bundle as a ZIP file.

### End a session early

You don't have to run every stage. For example, you may only need the
requirements. Type `/complete` in the message box and press Enter.

1. MySpec asks **Complete this session?**: "This ends the Generate session now
   and marks it as completed. You won't be able to continue generating in this
   session."
2. Select **Complete session**.

In a Generate session, `/complete` becomes available once the first spec file
has been generated. Before that, it is greyed out.

When you end a session this way, the chat doesn't show the **Session
completed** card. Download the files with **Download all** in the file explorer
or **Download** in the session's menu in the **Chats** list. See
[Download your specs](#download-your-specs).

### An Edit session

In an Edit session, `/complete` opens **Review changes before completing**,
where you check every edited file before you finish. See
[Complete the session](/guides/edit-sessions/#complete-the-session).

### After completing

- The message box disappears. A completed session can't be continued; start an
  [Edit session](/guides/edit-sessions/) to change its files.
- In the file explorer, the bundle's badge changes from **In Progress** to
  **Completed**. The session's card in the **Chats** list shows **Completed**.

## Download your specs

| Where | What you get |
|---|---|
| **Download** on the **Session completed** card | A ZIP file named after the bundle, with the files as the session left them. |
| **Download** in a completed session's menu in the **Chats** list | The same ZIP file. |
| **Download all**, the icon next to **Specs** in the file explorer | A ZIP file named after the project, with the latest revision of every spec file, one folder per bundle, and the project's attachments in an `attachments` folder. |

## Build with your favourite tool

After a Generate session completes, the chat shows **Build with your favourite
tool**: "Open this spec in a vibe-coding platform to scaffold a working
prototype in seconds."

1. **Pick a tool**

   Select **Lovable**, **Bolt** or **Replit**.
2. **Review the prompt**

   MySpec generates secure links to your spec files and shows the prompt that
   will be sent, under **Instructions**. The prompt asks the tool to read your
   specs (all except `tasks.md`) and build a working prototype from them.
3. **Open the tool**

   When you see "Ready to open in …", select **Open Lovable** (or **Open Bolt**,
   **Open Replit**). The tool opens in a new tab with the prompt filled in.
   Their terms and privacy policy apply.

> **Lovable asks for a workspace first**
>
> Lovable requires you to select a workspace first. The prompt is only filled in
> after you choose one.

For a [Brownfield project](/guides/brownfield/), these three buttons are hidden,
because the specs describe a change to existing code rather than a new
prototype. Use **Generate AI Prompt** instead.

> **Anyone with a link can open your specs**
>
> The links in the prompt are temporary links to your spec files that anyone
> with the link can open for 24 hours. With Lovable, Bolt and Replit, they are
> handed to that company's website.

### Turn integrations off

An organization owner or admin can switch this panel off under **Organization
settings** → **Spec integrations**, with the setting "Allow “Build with your
favourite tool” after a Generate session". When it is off, the panel is hidden
and no links are created. Downloading the bundle still works. See
[Spec integrations](/guides/organizations/#spec-integrations).

## Generate AI Prompt

**Generate AI Prompt** is in the same panel. It creates a prompt you can copy
into Cursor, Copilot, Claude or any other AI tool:

1. Select **Generate AI Prompt**.
2. Wait for "Prompt is ready to copy."
3. Select **Copy Prompt** and paste it into your tool.

For a new project, the prompt lists your spec files except `tasks.md`, with a
link to each one, and tells the tool to read them all before writing code. For
a Brownfield project, the prompt frames the work as a change request: it lists
every file, and tells the tool to read the proposal, spec deltas, design and
tasks in order, apply them, and match the existing code's conventions.

The prompt uses the same temporary links as the build tools.

## Connect your coding agent over MCP

For ongoing work, connect your coding agent to MySpec over MCP instead of
copying files. The agent then reads the latest revision of each spec file
directly, and can update the specs and add comments as the code changes.

- [Connect your coding agent](/mcp/) — Set up the MySpec MCP server in Claude, ChatGPT, Cursor or your editor.
- [Tool reference](/mcp/tools/) — Every tool your agent can call, such as list\_spec\_file and read\_spec\_file.

Source: https://docs.myspec.dev/guides/finishing-a-session/index.mdx