Conversations

Split your build work into focused threads — in both the App Builder and the Agent Builder

Both the App Builder and the Agent Builder support multiple conversations per app or agent. Instead of building, refactoring, and fixing things in one ever-growing thread, you split the work into focused conversations — one per feature, screen, or refinement pass — and switch between them at any time.

Open the Conversations tab in the builder panel (next to Properties / Design) to see them all.

Why multiple conversations help

• Focused context — the AI works best when the recent history is relevant to what you're doing now. A dedicated conversation for "checkout flow" or "tighten the sales agent's instructions" stays on-topic and doesn't drag in unrelated decisions from earlier.
• Cheaper, faster turns — shorter histories mean smaller prompts, lower credit usage, and quicker responses.
• Easy to resume — come back days later and pick up exactly where you left off on a specific area, without scrolling past unrelated chatter.
• Safer experimentation — try a risky refactor or a rewrite of an agent's instructions in a new conversation; if it doesn't pan out, the rest of your work stays untouched.

What you'll see

The Conversations tab lists every conversation for the current app or agent, grouped by:

• Current instance — conversations on the ERP.net instance you're connected to right now. Click any of them to switch.
• Other instances — conversations bound to a different instance. They're shown for reference; to open one, switch to that instance from the top bar first.
• Archived — hidden by default; toggle Show archived to see them.

For each conversation you get the title, instance, when it was created, and when it was last updated, plus badges for the current one and any that are still running.

Why does my conversation look empty? If you open a builder project and the conversation appears blank, check whether you switched the connected ERP.net instance. Each instance has its own set of conversations, and changing the instance automatically creates or swaps to the matching conversation for that instance. Open the Conversations tab to confirm which instance the current conversation belongs to, and switch back to the original instance if you want to see the previous history.

Actions

• New conversation — top-right button. Starts an empty conversation for the same app or agent on your current instance, and drops you straight into the Design view so you can start typing right away.
• Switch — click any conversation row on the current instance to open it.
• Archive — from the row menu (⋯). Hides the conversation from the default view; the data is kept and you can restore it any time.
• Restore — toggle Show archived, then choose Restore from the row menu.

You can't archive the conversation you're currently in — open another one first.

How it differs between the two builders

The mechanics are the same; the grain of a conversation is different.

• In the App Builder — one conversation per feature, screen, or sub-project of the app: "Layout & navigation", "Customers list", "Customer detail page", "Bulk import". Each conversation builds and refines a slice of the app.
• In the Agent Builder — one conversation per round of design work on the agent: "Initial setup", "Tighten the instructions", "Add calendar capability", "Rework the greeting". The latest design conversation for an agent reopens automatically when you come back to it.

In both cases, switching instances automatically swaps to the matching conversation for that instance (or starts a clean one if none exists yet).

Example: building a small CRM app

A typical App Builder flow with four parallel conversations:

1. "Layout & navigation" — set up the page structure, sidebar, theme.
2. "Customers list" — wire up the customers table, search, and filters.
3. "Customer detail page" — single-record view, related orders, edit form.
4. "Bulk import" — a one-off conversation for a CSV import screen.

Each conversation keeps its own back-and-forth with the AI. When you ask the customers-list conversation to "make the status column sortable", it doesn't get distracted by an earlier debate about the navigation icons.

When the bulk import is shipped and you don't expect to touch it for a while, archive that conversation to keep the list tidy. If a bug comes back later, restore it and the full history is still there.

Example: refining a Sales Pipeline agent

A typical Agent Builder flow over a couple of weeks:

1. "Initial setup" — create the agent, pick the base agent, write the first instructions and greeting.
2. "Tighten Q4 focus" — rework the instructions to prioritise high-value deals and stalled opportunities.
3. "Add calendar capability" — turn on calendar access and adjust instructions for booking follow-ups.
4. "Polish the welcome screen" — refine the greeting message and quick-action buttons.

Each conversation is a focused design session. Archive the ones that are clearly done; reopen any of them later if you want to revisit a decision.

Tips

• Name conversations clearly — rename early so the list stays scannable as it grows.
• One concern per conversation — resist the urge to dump everything into one thread; split as soon as you start a noticeably different task.
• Archive aggressively — anything finished and stable can be archived. Nothing is deleted.
• Pair with Version History — conversations split the work, versions snapshot the state. Together they give you fast iteration and instant rollback.

Related

• App Builder Overview
• Managing Apps
• Agents Overview
• Creating Agents
• Conversations & History — the same concepts for regular agent chats