The assistant reads your workspace and changes it — so the fastest way to see what it does is to say something to it. Here are the sentences worth starting with, and what each one should give you back.
01
Bring a key
Settings → Assistant. Pick a provider, paste your own API key. Without one the assistant answers from a canned script and none of these prompts do anything real.
02
Open the assistant
The Assistant button sits in the top bar of every page. For a longer session there is a full-screen view at /assistant.
03
Paste, send, approve
Notes, tasks and new contacts apply on their own. Anything touching money, stage or ownership stops and asks you first — approving is part of the test.
Start from nothing
You just signed up and the board is blank. These build a workspace out of plain sentences, and they run in order — each one leans on what the last one created. The final one furnishes the place well enough to run the next set.
01
Ask what it can actually do
What's in my pipeline right now, and what can you actually do for me in here?
Exercises
listOpenDeals · listPipelineStages
Expect
It says the pipeline is empty in plain words, names your real stages back to you, and offers to add something.
Bug if
It invents deals you never created, or answers with a generic capabilities blurb without naming a single one of your stages.
02
Add your first contact
Add Dana Reyes as a contact — dana@northwind.example, she's VP Ops at Northwind Traders.
Exercises
createContact
Expect
The contact exists straight away with no approval step, name, email and company all filled in. Creating a contact is reversible, so it applies itself.
Bug if
An approval card appears, or the turn dies complaining about a missing phone number you never gave it.
03
Open your first deal
Open a deal called Northwind Traders — annual plan, 42,000 USD, first stage of the pipeline, and put Dana on it.
Exercises
listPipelineStages · findRecords · createDeal
Expect
It looks up your real stages and finds Dana by name first, then stops and shows an approval card. Nothing reaches the board until you press Approve.
Bug if
The deal appears without you approving it, or it asks you for a stage ID — you should never see an ID at all.
04
Log a call in plain English
Just got off a call with Northwind. They want a security review before they'll sign, and their CFO is out until the 12th. Log that, and put a task on me to send the SOC 2 pack by Friday.
Exercises
findRecords · saveNote · createTask
Expect
A note in your own words on the Northwind deal, plus a task dated this Friday. Both apply without asking — they're the two things you'd never want to confirm twice.
Bug if
It replies with instructions for how you could log it yourself, or asks which deal you mean when only one exists.
05
Say no to something
Actually move Northwind to the last stage and set it to 500,000 USD.
Two approval cards. Press Deny on both — it acknowledges the refusal and moves on. Money, forecast and ownership are always asked about.
Bug if
It retries the same call after you denied it, or argues the change was a good idea anyway.
06
Furnish the whole workspace
First — Switch the composer to Thorough first — this needs more tool calls than Fast mode is allowed to make.
Set me up a demo book of business. Create a decision maker at each of Northwind Traders, Globex, Initech, Umbrella and Soylent, with plausible emails on their own domains. Then open one deal per company, spread across different stages of my pipeline, somewhere between 8,000 and 60,000 USD each, with the right contact attached. Tell me what you created and what's left if you run out of room.
It reads your stages once, creates the five contacts without asking — they're reversible — then proposes the deals one approval card at a time. It will very likely run out of steps partway; it should say exactly where it stopped so you can reply “keep going”.
Bug if
It reports five deals created with no approval card in sight, or it stops mid-way having written nothing about what it managed and what it didn't.
Something behaved differently to what a card says it should? That is the bug — tell us which prompt and what you saw instead.