Models & tiers
Webbee Code runs on three coding brain tiers — Smart, SuperSmart and UltraSmart. Switch with /model or Ctrl+B, and your choice is remembered per repository.
Webbee Code doesn't lock you to one brain. It runs on a coding brain tier, and you pick the tier that fits the job — a quick fix and a week-long refactor don't need the same horsepower (or the same cost).
The three tiers
| Tier | You type | What it's for |
|---|---|---|
| Smart | webbeesmart | The default. Fast and economical — everyday coding, fixes, questions about your project, routine edits. |
| SuperSmart | supersmart | A step up in reasoning for gnarlier work — tricky bugs, refactors that span files, design decisions. |
| UltraSmart | ultrasmart | Maximum reasoning for the hardest problems — deep architectural work, subtle bugs that resist everything else. |
Smart is the default. If you never touch /model, that's what you're running.
The names you type are always lowercase (webbeesmart, supersmart, ultrasmart); the pretty labels — Smart, SuperSmart, UltraSmart — are what Webbee shows back to you.
Switching tiers
Two ways, whichever fits your hands:
/model <tier>— switch straight to one, e.g./model ultrasmart.- Ctrl + B — cycle through them: Smart → SuperSmart → UltraSmart → back to Smart. This is the tier twin of Shift + Tab, which cycles modes.
Run /model with no argument and Webbee tells you which tier you're on right now, plus the list you can switch to.
Every switch is confirmed two ways so a change never slips past you: a one-line note lands in the transcript (🎛️ model tier → UltraSmart), and the tier segment in the toolbar under your input box shows the new name, gently shimmering so it's alive rather than static.
Switching mid-turn doesn't hijack the work already running — the new tier takes effect from your next turn. Let the current one finish (or press Esc), then continue on the new brain.
Your choice sticks — per repository
Webbee Code remembers the tier for the repository you're in. Put a big refactor on UltraSmart, close the terminal, come back tomorrow — that repo is still on UltraSmart, while your other projects stay on whatever you left them on.
That's deliberate: the tier is a property of the work, not of your terminal. It's remembered locally on your machine, and if that memory is ever lost, Webbee simply falls back to the platform default — nothing breaks.
Want to hand the choice back to the platform? Switching back to webbeesmart puts you on the standard default.
Tiers, cost and your plan
You pay per turn from your own credits as Webbee works, so a heavier tier costs more per turn than a lighter one. That's the whole trade: reach for UltraSmart when the problem earns it, and stay on Smart for the everyday.
Two habits keep this comfortable:
/cost(or/usage) — tokens and credits spent in this session, any time you want to check.- Drop back down when the hard part is done. Nothing forces you to finish a task on the tier you started it on.
Webbee Code needs a paid plan (Pro or higher) — see Install. If your credits run low mid-task, Webbee pauses and tells you instead of failing, then picks up where it left off once you top up.
Modes are a different thing
Tiers and modes are two independent choices, and it's worth not mixing them up:
- Tier (
/model, Ctrl+B) — how much brain Webbee uses. - Mode (
/mode, Shift+Tab) — how much freedom it has: ask before writing (default), think-only (plan), or self-approve (autopilot).
Both are remembered per repository, and you can combine them freely — UltraSmart in plan mode is a great way to get a serious opinion before anyone touches a file.