Skip to content

Focus limit

AI makes starting work easy, and every session you start is one more thing to keep up with. The focus limit helps you not start more than you can follow: you choose how many sessions you want going at once, and Seshboard asks before you go over. Why it helps: The AI chaos beast in your head.

The focus limit counter in the sidebar footer showing 2 / 3, with its popover listing the sessions that count, each with its state and an Open buttonThe focus limit counter in the sidebar footer showing 2 / 3, with its popover listing the sessions that count, each with its state and an Open button
  • Turn it on in Settings → Focus with the Focus limit switch.
  • In the command palette: Focus limit: turn on, Focus limit: turn off and Focus limit: set limit… (pick from 1 session to 10 sessions).
  • Change limit in the line New session shows at the limit opens Settings → Focus.
Settings on the Focus section: the Focus limit switch, Sessions at the same time with minus and plus buttons, When you reach it with Nudge and Strict, Count terminal and IDE sessions, and Count sessions on other computersSettings on the Focus section: the Focus limit switch, Sessions at the same time with minus and plus buttons, When you reach it with Nudge and Strict, Count terminal and IDE sessions, and Count sessions on other computers

A session counts while it’s on your mind:

  • Claude is Working on it;
  • it Needs you: a permission or a question;
  • it finished something you haven’t read yet (Unread).

Reading the result or marking the session done frees its place. Stopped sessions never count. By default only sessions you started or continued in Seshboard count; turn on Count terminal and IDE sessions to also count Claude Code running in your terminal or editor. Sessions on computers you paired count too (they are on by default); turn off Count sessions on other computers to leave them out. A computer that is offline doesn’t count.

While the limit is on, a counter at the bottom of the sidebar shows how many sessions are going, such as 2 / 3:

Counter Means
Neutral Under the limit
Yellow At the limit
Pink Over the limit

Click it to see which sessions count: needs you first, each with its project, its state (“Needs you · 12m”, “Working”, “Done, not read yet”) and Open. In the minimal sidebar rail the counter shows as 2/3 and its list opens to the right.

When you are at the limit, New session says so in one line above the message box: “3 of 3 sessions going. Your focus limit. Start puts this in the queue.” The sessions that count are under Going now on the right, each with how long it has been going. Click one to open it.

Start then reads Add to queue (Command, ReturnControl, Enter). Your prompt goes to the queue, waiting for A free slot: it doesn’t wait for its project to be free too, so it can start while another session works there. Turn on Start by itself next to Wait for and it starts as soon as a slot frees.

What else you can do depends on how strict you set the limit:

  • Nudge (the default): Start anyway is in Start’s ▾ menu. The other ways of starting work ask first, “Start a 4th session?”, with Add to queue, Start anyway and Cancel.
  • Strict: there is no Start anyway. The question says “Finish one first”, with Open for a session that needs you, Add to queue and Cancel. Finish, read or mark a session done first.

Escape or Cancel closes the question and keeps your prompt where it was. The question never starts anything over the limit without you saying so.

Every way of starting work goes through the same question:

  • starting a session in New session or from the command palette;
  • starting a queued item (there the queue button says Keep it queued);
  • a message that brings back a session that doesn’t count right now;
  • forking a session;
  • a project action that sends Claude a prompt;
  • opening Claude in the terminal.

Answering a session that already counts, stopping Claude, marking a session done, reviewing changes and committing are never held up.

A queued item that starts by itself never asks, since nobody may be there to answer. At the limit it waits, and its row says “waits for a free slot (focus limit)”. It starts when a slot frees: when you read, mark done or stop a session. It doesn’t also wait for its project to be free.

A scheduled run doesn’t ask either. At the limit it goes to the queue as an item that starts by itself, and starts when a slot frees, even while another session works in its project. A session a trigger starts does the same, on top of the trigger’s own At once limit.

In Settings → Focus:

  • Focus limit: on or off.
  • Sessions at the same time: 1 to 10, 3 to start with. Working, waiting for you, or finished but not read yet.
  • When you reach it: Nudge asks first. Strict waits until you finish, settle or stop one.
  • Count terminal and IDE sessions: also count live Claude Code sessions started outside Seshboard.
  • Count sessions on other computers (on by default): also count sessions that are working, need you or are unread on computers you paired.