Skip to content

Model, effort and mode

Pick how a session runs: which account it uses, which model, how much Claude thinks, and when it stops to ask you. Under the message box sits a row of quiet chips: the Claude profile, the model, the effort and the permission mode. They show only the value (“Personal”, “Opus 4.5”, “Medium”, “Auto”); hover one for its full meaning, such as “Effort: Medium”. The same row is in New session, in the command palette’s New session step and in every session.

New session with the model chip's menu open above the message box, listing Default model and the models Claude Code offers, each with a short descriptionNew session with the model chip's menu open above the message box, listing Default model and the models Claude Code offers, each with a short description
  • In New session, under the message box. The chips start from the project’s defaults.
  • In a session, under its message box. Changes apply while the session runs.
  • In the command palette, with a session open: Change model…, Change effort… and Change permission mode….

Click a chip to open its menu above it. The image and attach buttons come first in the row, then a thin line, then the chips.

With more than one Claude profile, the first chip is the profile, as its colour dot and name. In New session you can pick another profile for one session; the menu marks the project’s own as “(project)” and the default as “(default)”.

A running session keeps its profile. Its chip shows the profile and links to Manage profiles…; start a new session to use another one. With a single profile the chip is hidden.

The model chip lists Default model (what Claude Code would pick) and the models your Claude Code offers, each with a short description. The chip shows the name without “Claude”, such as “Opus 4.5”.

Auto comes first in the menu: Haiku reads your prompt when the session starts and picks the model for you. See Auto model.

A session of another agent, such as GitHub Copilot or Codex, lists that agent’s own models. See Other agents.

When your main model is overloaded or unavailable, Claude Code can switch to a fallback model instead of making you wait, so a busy Opus doesn’t stop your work. It is off by default.

Set it where you set the model for new sessions:

The project’s choice comes first, then the profile’s, then the global one. It covers every Claude Code session Seshboard starts: from New session, the queue, schedules, triggers, pipeline steps and the orchestrator’s sessions.

Claude Code tries the main model again on each turn. When a turn ran on the fallback, the model chip shows both, such as Opus → Sonnet.

When Claude refuses and Claude Code moves the session to the fallback model, the conversation says so: “Claude switched this session to Sonnet after a refusal”. The refused reply is taken back, and the model chip shows the model in use now. Without a fallback model, the line reads “Claude refused and no fallback model was available”.

How much Claude thinks before it answers. The chip shows three bars that fill with the level:

Choice Bars
Default What Claude Code would pick
Low one
Medium two
High three
Extra high three, in the accent colour
Max three, in the accent colour

In a session the effort chip shows only when the model has an effort setting.

The word ultrathink in a message to Claude Code runs that one turn at extra high effort, without changing the session’s effort. The message box colours the word, so you see it took.

To add it without typing, choose Ultrathink this turn in the effort chip’s menu. The chip then says Ultrathink, and the word goes with your next message only. Choose it again to take it back before you send. If the message has the word already, it isn’t added twice.

Ultrathink is Claude Code’s. Sessions of other agents don’t have it.

On a model that has it, a lightning bolt sits in the row. Click it to turn on fast mode: Opus runs up to 2.5x faster, at a higher price per token. On a Claude subscription it always bills to usage credits. Hover the bolt to see what it does and what it costs.

  • In a session, it applies to that session. Turning it on later reads the conversation again at the full fast rate, so it costs least at the start of a session.
  • In New session, it also applies to the first message.
  • It is off every time you start or resume a session.

You can also run Turn on fast mode and Turn off fast mode in the command palette, or type /fast, /fast on or /fast off in the message box.

When fast mode can’t run, the session goes on at standard speed and the bolt’s tooltip says why, such as being out of usage credits. If it hits its rate limit, it pauses until it comes back.

Fast mode is for Claude Code sessions. Your usage marks the sessions and models with fast mode turns.

The mode decides when Claude stops to ask before it acts. The menu, under the heading Permissions, offers four modes:

Mode Chip What it means
Ask before edits Ask first Approve every edit and command. The default.
Accept edits Accept edits File edits apply, commands still ask.
Plan mode Plan Claude reads and plans, and makes no changes. It shows you the plan to approve.
Auto mode Auto Claude only asks when it matters.

Each mode has a dot in the chip: green for Ask first, blue for Accept edits, grey for Plan and yellow for Auto. A session started in another mode elsewhere (such as bypassing permissions) shows that mode in the menu too, but Seshboard never offers it.

Press Shift, TabShift, Tab in the message box to switch mode. Like the Claude Code CLI, it cycles through Ask before edits, Accept edits and Plan mode. Pick Auto mode from the menu.

A new session starts in the first mode that is set:

  1. The project’s own default mode, on its Settings tab.
  2. The default mode of its Claude profile.
  3. Global permission mode in Settings › General: Ask before edits unless you change it, or with Remember last the mode you picked last.

The session can still change it, with the chip or Shift, TabShift, Tab.

What the cards look like when Claude asks: Permissions and questions.

When the row runs out of room, it never cuts a chip off. It steps through fixed levels instead:

  1. The profile shows only its dot.
  2. The model drops its version (“Opus” instead of “Opus 4.5”).
  3. Effort shows only its bars.
  4. The mode shows only its dot.

The model, effort and mode shrink last, because they say the most about how a session runs. The fast mode bolt keeps its place in the row at every level.

The label and tooltip keep the full value at every level. This happens in narrow windows and when two sessions are side by side.

New session starts from the project’s defaults for model, effort and mode, then from the defaults of its Claude profile, and from Claude Code’s own defaults for whatever both leave unset. A change in New session applies to that one prompt: the next one starts from the defaults again.

To keep your choices for the project, choose Save as project default in the Where menu of the route strip, or run Save as project default in the command palette. You can also set them on the project’s Settings tab. Quick questions keep their own choices, apart from your projects.

The defaults live on each project’s Settings tab. Profiles are in Settings → Profiles.