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

# Iterating on the blueprint

> Use the blueprint chat to refine your plan in conversation.

The blueprint chat is a streaming conversation tied to your blueprint. Use it for changes that span multiple sections, or for changes you can describe but do not want to manually click through. This page covers how to iterate effectively.

## Opening the blueprint chat

The blueprint chat is available from the blueprint page. Open it from the side panel. {/* VERIFY: confirm exact location and entry point of the blueprint chat */}

The chat scrolls beside the blueprint, so you can watch sections update as you talk to it.

<img src="https://mintcdn.com/archie-e998dbf6/eiHdGPkQDkoCG39-/features/blueprint/blueprint-chat-side-panel.png?fit=max&auto=format&n=eiHdGPkQDkoCG39-&q=85&s=4ddd61772e00486822ebf71919052ddc" alt="Blueprint chat open in the side panel" width="820" height="1380" data-path="features/blueprint/blueprint-chat-side-panel.png" />

## What it does well

* **Multi-section changes** — "drop the messaging module, simplify the user types to just admin and customer, switch from Stripe to Lemon Squeezy."
* **Refinements** — "the checkout module should support guest checkout."
* **Asking questions** — "what does the admin user type include right now?"
* **Trying alternatives** — "show me what this would look like with a marketplace structure instead of a single-tenant app."

## How to phrase changes

Describe what you want, not what to do step-by-step. The chat understands the blueprint structure and will edit the right sections. Examples:

* Good: "Make this an internal tool — drop the public marketing pages."
* Good: "Add a billing dashboard for admins."
* Avoid: "Open the modules card. Click the Marketing module. Click delete." (verbose; not necessary)

## Conversation history

The chat keeps a history of your conversation. You can scroll back, pick up where you left off, or start a new conversation thread. {/* VERIFY: confirm whether multiple threads are supported per project */}

## When direct edit is better

If you are doing a small, surgical change (rename a module, tweak a description), just edit the section directly. The chat is for changes that touch several places at once.

## FAQ

<AccordionGroup>
  <Accordion title="Does the chat run a build?">
    No. The chat edits the blueprint. Builds are explicit — you trigger them from the build scope bar.
  </Accordion>

  <Accordion title="Will the chat lose my place if I refresh?">
    No. The chat reconnects automatically. Conversation history persists across reloads.
  </Accordion>

  <Accordion title="What if the chat's change is wrong?">
    Tell it. The chat is conversational — "no, keep the messaging module, just simplify it" is fine.
  </Accordion>
</AccordionGroup>