# From One Sentence to a Running Agent with Quick Build

**URL:** <https://community.solace.com/t/from-one-sentence-to-a-running-agent-with-quick-build/4957>\
**Category:** Solace Agent Mesh\
**Created:** [November 16, 2026, 6:51pm UTC](https://community.solace.com/t/from-one-sentence-to-a-running-agent-with-quick-build/4957 "2026-11-16T18:51:40Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tamimi](https://yyz1.discourse-cdn.com/solace/user_avatar/community.solace.com/tamimi/32/2190_2.png) [@Tamimi](https://community.solace.com/u/Tamimi)\
**Post date:** [November 16, 2026, 6:51pm UTC](https://community.solace.com/t/from-one-sentence-to-a-running-agent-with-quick-build/4957/1 "2026-11-16T18:51:40Z")

</div>

I wanted to see how far Quick Build in Solace Agent Mesh gets on a single prompt, so I asked it for a loading-dock scheduling agent for a fictional freight company.

You’ll find it under **Builder** \> **Quick Build**. I typed:

```plaintext
Create an agent named dock-scheduler that helps Northwind Freight warehouse
staff book and reschedule loading-dock appointments. It should ask for the
warehouse, carrier, date and time window, confirm the booking back in a short
summary, and refuse requests outside 6 AM to 10 PM.

```

About 20 seconds later I had a build plan: one agent component, shown both in the chat and on the canvas with a **Draft** badge.

 ![The Quick Build plan card with the Dock Scheduler agent in Draft](https://canada1.discourse-cdn.com/solace/original/2X/9/9024257cb139d946e4cfbac151cf0d71b64e27db.jpeg)

If the plan is off, keep chatting and it updates in place. Mine was fine, so I selected **Build & Activate**. The node went from **Draft** to **Creating** to **Active** in under a minute, with generated instructions covering bookings, reschedules and the 6 AM to 10 PM rule.

 ![The agent Active on the canvas after Build & Activate](https://canada1.discourse-cdn.com/solace/original/2X/6/69cbfe9d0108f79ff981175e67ae908cb858e345.jpeg)

Then **Switch to Test Mode**. Your build conversation is kept, and the input changes to **Testing: dock-scheduler**. I asked it to book dock 3 at the Reno warehouse for a carrier tomorrow between 2 and 3 PM and got back a tidy confirmation table.

 ![Test mode reply from the dock-scheduler agent](https://canada1.discourse-cdn.com/solace/original/2X/2/2df5b015d20a9d773cd24e221e65dbb0000691a1.jpeg)

**The gotcha.** The reply also said there was “a minor glitch generating the reference number”. The generated instructions promise a booking reference, but the agent has no tool or connector behind it, so it can’t actually book anything or mint an ID. Quick Build did exactly what I asked for; I just asked for an agent with nothing to act on. Test mode is where that shows up, so use it before you share the agent. The fix is to describe the system it should talk to (a connector, a webhook, a toolset) in the next turn of the same build.

Also worth knowing: the build is a saved conversation you can reopen from **Recent Chats** , and removing a component from the plan doesn’t undeploy it.

Docs:

- [Quick Build (Experimental)](https://docs.solace.com/Agent-Mesh/Framework/building/quick-build.htm)
- [Creating Agents](https://docs.solace.com/Agent-Mesh/Framework/building/agents/index.htm)

You can try the same prompt yourself if you [download the Solace Agent Mesh desktop app](https://solace.com/products/agent-mesh/); Quick Build is in the Builder menu.

What’s the first thing you’d ask Quick Build to make, and did the first plan get it right?
