About Piper

In one line. Piper is the assistant you can open from any page of the platform — ask it a question, ask it to make one small change, or describe a whole solution and let it build it for you. You’ll be able to. Know what Piper will and won’t do before you type your first ask: when it answers straight away, when it asks for your go-ahead first, how to pause and pick a build back up, how to ask for a prototype only, and where its answers come from. Where this lives. The assistant button in the top navigation bar, open from every page. It reads the project you’re currently viewing, so you rarely need to tell it which one you mean.

What Piper does

Piper does a few different things, and it’s worth knowing which one you’re asking for:

It answers questions — about the platform in general, and about your own project specifically (how many documents came in today, which agents you’ve built, why a run failed). For your own project it reads the real data behind the question; it does not guess.
It makes one small change at a time — “add a user”, “create an agent called X”, “add a page called Overview”. Each of these is one thing, made one way, and Piper tells you exactly what it’s about to do before it does it.
It builds a whole solution — when you describe something bigger (what it should do, the kind of documents involved, start to finish), Piper can put together everything a real solution needs — its data, its agents, its pages — as one guided build.
It makes an HTML prototype, and only a prototype, when that’s what you ask for. Say “just a prototype” or “only a mock-up” and Piper makes one you can open as a link — it does not go on to build the real thing behind it unless you then ask it to.

How to ask

Ask the way you’d brief a colleague, in plain language: say what you want, not how to configure it. Piper works out the rest, and asks you anything it still needs to know before it acts.

For a whole solution, Piper first has a short conversation with you to fill in what it needs, then shows you a plan of what it intends to build, in your own words, before it makes anything at all.

The one go-ahead

Piper never changes anything until you say yes, and tells you first, in one sentence, exactly what it’s about to do.

For a single change — “Add a page called Overview to this project” — Piper states the change and waits for a yes or a no. Say yes, and it makes the change. If it asks once more to be sure, say yes again and it goes ahead.
For a whole solution, the same rule holds at the scale of the whole build: Piper shows you the plan, you say yes, and the build then runs end to end, with its steps appearing as it goes. If it asks you to confirm the start once more, say yes again.

A build can still pause on its own partway through, to show you something it has produced so far — the requirements it wrote, say, or a prototype — and wait for you to look it over. Saying yes there continues that same build; it never starts a second one.

Stop and resume a build

While a build is running, say stop or pause: Piper finishes the step it is on and then waits, rather than stopping mid-step.

To pick it back up, say continue or resume — this also works if the build was interrupted by something outside your control. Piper carries on from the last step that finished: the steps already done are kept, and nothing already made is made twice.

If a build is instead waiting for you to review something it already produced, tell Piper to go ahead, or ask for a change first — either way, it’s the same build continuing, never a second one.

Where its answers come from

When Piper explains the platform rather than changing something, it grounds what it says in two places: this Academy — the guide you’re reading right now — and the platform’s own technical reference material, generated from the product itself. When it draws on one of these, it can tell you so.

For a question about your own project, Piper prefers what it can read there over anything a guide says in general: a count, a name or a status comes from your project’s own data, never from a guess.

Where to go next

E4 · Chat & search experience — the chat surfaces Piper shares its controls with.
E6 · Pages & cards — ask Piper to build or adjust a page.
G1 · Access & roles — where an administrator configures the assistant.