Tour of the interface
A map of the desktop app window — what each panel does and what each control means.
The desktop app is one window with seven areas plus a wallet badge.
Platforms
macOS
Left
Sidebar and file explorer — profile, projects, tests, modules
Center
Editor — your test file, multiple tabs, / for the command list
Right
Device panel and variables
Bottom
Console — live logs, per-step screenshots, run status
Watch out
The wallet badge is the first thing to check when a run won't start
Prerequisites
Drizz desktop app installed and signed in
A connected device for the device panel and console to populate
Panels
1
Sidebar
Profile, Discover, a link to these docs, update prompts, and the collapsible Drizz Studio panel
2
File explorer
Projects, tests, modules and folders, and the Online / Local toggle
3–4
Editor
The open test file. Multiple tabs, / command hints, autocomplete, per-step status decorators, save and save-as with unsaved-change tracking
5
Device panel
Connected devices, the device picker, app selection, connect and disconnect
6
Variables panel
The variables available to the open file, colored by whether they resolve
7
Console
Live execution log, per-step screenshots, run status banner
8
Wallet badge
DT balance
Two surfaces sit alongside the window layout:
Chat
Describe a test in plain English and have Drizz generate the script
Memory
Org-level context and blocker rules for an app
Editor controls
/ on an empty line
Opens the command palette with autocomplete. The editor shows the hint "Type '/' for Drizz supported commands". The palette is the authoritative command list
Tabs
Several test files open at once. The active tab shows an unsaved-change indicator
Step decorators
A status marker in the gutter on each line during and after a run — passed, failed, running, not yet reached
Module expansion
A CALL line shows the module's body inlined beneath it, indented and read-only. Edits are made in the module file
Command Guidelines
Explain command level particulars and ready to use command examples. Mentions best practice for all commands.
Device panel
Devices available
Pick a device, pick the app under test, connect. The panel shows the connected device, its OS version and its state
No device set up
The panel offers the guided setup wizard
Variables panel
Green
The variable resolves against the selected dataset
Red
The variable does not exist in the selected dataset. That step fails at run time
Console
Live log lines
Step-by-step execution output for the current run
Status banner
Run status and the run's token usage
"Predicted Action drizzing fast ⚡"
The step resolved from cache instead of by Vision AI. It ran in a fraction of the time and cost a fraction of the tokens
Steps you didn't write
Automatic popup dismissal, from blocker rules defined in Memory for your app
Wallet badge
Shows
Remaining DT balance, and DT used by the current run
Vague run-start errors
An exhausted balance can present as a server or availability error. Check this badge first
After a top-up
The badge does not always refresh immediately. Navigate away and back
Reporting a problem
Report Issue bundles logs, recent screenshots and device state and sends them to Drizz support. See Report an issue.
Common mistakes
Hunt through menus for the command list
Press / on an empty line. That palette is the complete list
Ignore a red variable in the variables panel
The run fails on that step. Fix it before you press run
Read a failure from the log alone
The per-step screenshot answers most failures. Open the before-screenshot first
Edit the inlined module body under a CALL
It's read-only. Edit the module itself
Debug a vague "run won't start" error
Check the wallet badge before anything else
Describe a symptom in an email to support
Use Report Issue. It sends the logs, screenshots and device state with it
Next
Last updated: 6 August 2026
Last updated
Was this helpful?