Operator console
Manage is the operator console.
Manage holds the durable settings that should not clutter the chat. This guide shows you how to create a workspace and set its permission mode, then maps the rest of the console — dashboard, proposals, memory, accounts, cost, and themes.
At a glance
- Manage is where the durable settings live — the things that should not clutter the chat in Studio.
- Create a workspace and set its permission mode here; both are per-workspace, not global.
- One console covers the dashboard, proposals, memory, accounts, cost, and themes.
- New workspaces default to the edit permission mode — read plus safe file writes.
manage — dashboard

Dashboard with workspace status and attention queue
manage — accounts

Accounts, API keys, local models, defaults, and health
What's in the console
The console is a set of pages down the left. Each one owns a durable slice of the operator's setup, so nothing important has to live in the chat scrollback.
DashboardOverview and attention queue
WorkspaceList, board, and repo status
ProposalsPlans and changes awaiting decision
MemoryApproved facts and curator findings
AccountsProvider credentials and catalog — full detail in the Accounts guide
Agent SettingsRole routing and defaults
CostSpend and budget tracking
SettingsWorkspace, global, and diagnostics
Create a workspace
A workspace is one project CrazyToad works on. On first run the New workspace modal opens for you; later, open it from the workspace sidebar. Exactly one workspace is active at a time.
- Pick a template — start blank or from a preset.
- Name it — the workspace name is the only required field.
- Choose where the code lives — point at a folder or clone a repo.
- Create it — CrazyToad sets up the workspace and makes it active.
Workspace nameRequired, max 80 characters, e.g. auth-rewrite
Project pathAbsolute folder path, e.g. C:\Users\you\Desktop\app — use Browse… or + New on Desktop. Must be absolute or it is rejected
Clone a git repo insteadRepository URL such as https://github.com/owner/repo.git, then Clone
What are we building?A one-paragraph pitch that becomes the workspace description
Tech stack + constraintsLanguages, frameworks, and rules the agents must respect
Goals + done stateWhat finished looks like for this workspace
NoteQuick start needs only a name and defaults the folder to your Desktop. Full setup is worth it when you want CrazyToad to understand the project up front.
Set the permission mode
Each workspace's permission mode decides how much an agent may do without asking — set it in Manage → Settings → Permissions. New workspaces default to edit; the five modes form a ladder from read-only to unrestricted.
ObserveRead-only commands only — ls, cat, grep, git status / diff / log
SuggestRead-only; plans and proposes changes but writes nothing
Edit (default)Read-only plus write and file commands — mkdir, cp, mv, git add / commit / checkout
AutoEdit plus shell tooling — npm / pnpm / yarn / bun install, test, run, plus tsc, node, make, cargo, python
FullAny executable and network access, with no workspace boundary
WarningEvery mode shares a global deny: it blocks sudo, rm -rf /, git push --force, package publishing, and reads of secrets such as ~/.ssh and ~/.aws — even in full.