Waiso Desk
The Desk is a conversation with your Waiso. You type a question — “why did the import fail?”, “run the campaign flow”, “connect my database” — and the assistant answers from your projects, acting through a fixed set of Waiso tools as you. Everything runs, installs and is stored on your Waiso server; the assistant on your computer only reasons.
- Connect the Desk to your Waiso and sign in
- Ask for answers and actions in plain words
- Read the cards: runs, flows playing live, proposals to confirm
- Know what the assistant can never do on your computer
A conversation that acts
The Desk opens on the fox and one line to ask. A first briefing sums up what happened since you last looked — failed runs, things waiting for you — and every answer that refers to something real comes with a card you can open: a run with its output and logs, a script, a list of schedules, a flow.
A flow card draws your real flow with the same canvas as the web app and plays a run over it live, step by step — even a run started somewhere else while the card is on screen. Its Run button asks for the flow’s inputs inline when it has simple ones.
Get started
- Give your Waiso’s address
On first open, type the address you use in the browser — your company’s Waiso, or the cloud one.
- Sign in to Waiso
Sign in with your Waiso account. The sign-in is kept encrypted by your operating system.
- Sign in to Claude
Press Sign in to Claude and finish in the page that opens; if it shows a code, paste it back in the Desk.
- Ask
Type Which projects do I have? The answer names them, and you go on from there.
Open in detail
Any card can open the real screen of the web app inside the Desk, already signed in. There, the web app’s own chat panels — the script assistant, the e-mail assistant, the scraper chat — become the Desk’s conversation: the same one you were having, now pointed at the screen you see. A code change it proposes appears as a diff in the editor that you accept or reject.
Nothing destructive on its word alone
Reading, running a script and creating a new one happen when you ask. Anything that changes what is live or removes something — saving over a script or flow, publishing, schedules and event triggers, variables, inviting people or changing their access, pushing to Git, deleting — is gathered into one proposal card that lists every action. Only the actions on a card you approved go through; the assistant cannot add one afterwards.
| You ask | What the Desk does |
|---|---|
| “Why did the import fail?” | Reads the run and answers with its card |
| “Run the campaign flow” | Starts it and plays the run on a flow card |
| “Connect my database” | Shows an add-a-database card; you type the password there, never in the chat |
| “Delete the nightly schedule” | Shows a proposal card and waits for your yes |
What it never does, and limits
- The assistant has no terminal, no access to your files and no web browsing. Its only hands are the Waiso tools.
- Secrets never pass through the conversation: passwords go into a card, and the assistant learns only whether it worked.
- Windows only for now, and it needs Claude installed and signed in on the same computer.