How to use the Workbench panels.

The Workbench is a dock of panels that open around the centered chat, so proof sits beside the conversation. This guide shows how to open a panel, where it docks, and which panel to reach for — so you, Toad, and agents inspect the same evidence.

workbench — files

Open a panel from the dock

While you talk to Toad, open the panel you need from the Workbench dock. You don't leave the conversation to do it — the chat stays centered, and the panel comes to you.

It docks beside the chat

The panel opens alongside the conversation, not over it (the screenshot shows the Files panel docked open). Proof and discussion stay side by side, and Toad and the agents can inspect the very same rendered page or file you see. Panels are on-demand, so dismiss one once the proof is captured and re-open it any time the next step needs it.

Reach for the panel that fits the step

Use Preview for visual QA on a local page, Files and Git to read the source and review changes, and Terminal to run a focused check or script. Add Search, Problems, Schedule, Cost, or Review as the work calls for them. The chat itself lives in Studio; the Workbench is the proof that sits next to it.

Run the full GitHub flow via the gh CLI

Branches, PRs, and merges run through the gh CLI from the Git panel. Each task gets its own worktree, and finished work is integrated back to main automatically — so parallel agents don't trip over each other. You review the change in the panel before it lands, and the per-task worktrees keep concurrent agents from colliding on the same files.

Schedule jobs and loops

From the Schedule panel, set up one-shot or recurring jobs and loops so routine work runs on a cadence without you kicking it off each time. It's the same dock, so a scheduled job's output lands right beside the conversation that set it up.

Panel reference

Every Workbench panel at a glance — open whichever one the current step needs.