Using Webbee Code

Once you're signed in, using Webbee Code feels like chatting with Webbee — except it's right there in your terminal, working on your files.

The dock

At the bottom of your terminal you'll see the dock: a bordered input box, pinned in place. That's where you type. Webbee's replies and its work — reading files, proposing edits, running tools — scroll above the dock in your normal terminal scrollback, so you always have the input right where you left it.

Just type what you want and press Enter. Ask a question, describe a change, or point Webbee at a problem, and it goes to work.

Working a task to completion

When you give Webbee Code a task, it works it through to the end on its own — reading, editing, running, and checking its own work across as many steps as the job needs. You don't have to keep nudging it to continue.

It stops when one of three things happens:

• The task is done — Webbee wraps up and hands you the result.
• You stop it — press Esc any time (see Stopping a turn).
• Your credits run low — Webbee pauses instead of failing, and tells you. Top up your balance and it picks up where it left off.

You pay per turn from your own credits as it works, so a longer task costs more than a quick one. Need a single short run instead? Start Webbee with --once for one bounded turn.

Modes

Webbee Code runs in one of three modes. Switch any time with Shift + Tab — the ❯ prompt and the toolbar change colour, so you always know which one you're in.

• Default (cyan) — the balanced mode. Webbee reads freely and asks you before it writes a file or does anything destructive. You approve each change. This is where you'll spend most of your time.
• Plan (purple) — think-only. Webbee reads and reasons but makes no changes at all — write actions are declined automatically, so you get its plan and analysis without it touching your files. Great for "what would you do here?" before you commit to anything.
• Autopilot (yellow) — hands-off. Webbee approves its own actions and keeps going without stopping to ask. It's the fastest way to work, but it acts on its own — use it when you trust the task. (That's why it's yellow: proceed with care.)

Anything that spends money still needs your explicit approval in the browser, in every mode — autopilot never releases a payment on its own.

Slash commands

Type a command starting with / to control your session:

Stopping a turn

Changed your mind mid-task? You can stop Webbee while it's working:

• Esc — a graceful stop.
• Ctrl-C — interrupt a running turn.

Either way, it genuinely stops the work in progress — the same way the stop button works in the panel — so you can correct course and try again without waiting for it to finish.

Consent keeps you in control

Webbee Code runs the same extension arsenal as the panel, under the same guardrails. The rules are simple and always on:

• Reads run freely. Webbee can look at your files and connected tools whenever it needs to.
• Writes ask first. Before it changes a file, Webbee shows you exactly what it will do and waits for your OK.
• Money and destructive actions need explicit approval. Anything that spends or can't be undone stops and asks you before it runs.

So you can let Webbee explore and think freely, while every real change stays a decision you make. When you want to review what happened after the fact, run /steps to walk through the agent's work one step at a time.