Tabbed Sessions
Run multiple AI agents in parallel as tabs in the chat sidebar.
Headline feature
Tabs are how Agent Console handles multi-session work. Each tab is an independent agent session with its own scroll position, mode, and model — you switch between them without losing context.
Why tabs
AI agents work asynchronously. Tell one to research a topic, another to fix a bug, a third to draft documentation. Tabs let you keep all three open, switch among them while they work, and come back when each is ready.
Status icons on each tab tell you at a glance which agent needs attention.

The tab bar
The tab bar appears at the top of the chat sidebar. Each tab shows:
Label — generated for each new chat; how it's generated is configurable (see Tab titles below). Editable any time via right-click rename. The active tab widens to show its full title, capped to the sidebar width so the title and close button always stay in view; inactive tabs stay short. Hover any tab to see its full title.
Status icon — shows what the tab needs from you. Hover it for a short description.
Icon Meaning Warning triangle (pulsing) Needs your approval – the agent paused on a tool call Crossed circle Something went wrong Circle with !Stopped early while you were away – the agent hit a length or step limit, declined to continue, or the send failed Speech bubble with !Your last message failed and its error is still shown below the chat. Close the error or send again to clear it Tick Finished while you were away Spinner Working Dashed circle (slowly turning) Connecting to the agent Dot in a circle Ready for your next message. A brand-new tab shows this too, because it connects as soon as you send Moon Asleep to save memory, or reopened and not yet woken (see Sleeping tabs) Empty circle Not connected yet The tick and the circle with
!only appear on a tab you weren't looking at when the reply ended – a background tab, or any tab while Obsidian was in the background. They clear as soon as you switch to the tab, come back to the window, or send again. Stopping a reply yourself never leaves a mark. A failed message you've already seen shows the speech bubble instead, for as long as its error is on screen – even on a sleeping tab.Close button (×) — appears on hover
A + button on the right of the tab bar opens a new tab.
A ˅ chevron beside it opens a dropdown listing every tab — including any scrolled out of view. Each entry shows the tab's status icon – the same one the tab itself shows (see the table above). The active tab's name is in bold. Because it shows all sessions at once, it's the quickest way to spot which one is stuck or finished when many tabs are open.

Vertical tabs
See which chat needs you without opening a list. New installs start with vertical tabs, icons only. If you've used Agent Console before, your tabs stay in the top bar until you choose Vertical in Settings → Tabs → Tab display. The tabs move from the top into a narrow column on the right edge of the chat view. Each tab shows only its status icon, so in a narrow sidebar you can see 20 tabs or more at a glance. Choose Horizontal to go back to the top bar. The change takes effect at once and doesn't disturb your open chats.
![]()
- Know which chat you're in – the chat header shows the active chat's title, so you don't have to hover the column to find out.
- See a tab's name – hover a tab. The first one takes a moment; after that, every tab you pass shows its name and status straight away. Press
Escto hide it. - Show names all the time – drag the column's inner edge to make it wider. From about twice its narrow width it shows names, cut off with "…" when they're long; let go below that and it snaps back to icons only. Double-click the edge to switch between icons only and your last width. Your width is kept across restarts.
- Close a tab in one click – when the column is wide enough to show names (about three times its narrow width), hover a tab and click the × that appears at its right end. The × shows only while you hover, so a resting column shows just status and names. In the narrow, icons-only column there's no × – middle-click or right-click instead, or widen the column.
- Everything else works the same – click a tab to switch, middle-click to close it, and right-click for Rename, Rename with AI, Copy link to chat and Close (on the column, "Close to the right" reads "Close below").
+and˅sit at the top of the column. - Keyboard –
Tabto the column, then↑/↓to move between tabs andEnterto switch. PressDelete(orBackspace) to close the tab you're on; focus moves to the tab that takes its place. Holding the key closes just one tab. You can also press the context-menu key orShift+F10and choose Close. The resize edge is aTabstop too:←makes the column wider,→narrower, andEnterswitches between icons only and names.

Reordering tabs by dragging works in the top bar only.
What's new after an update
When you update Agent Console, a small What's new card appears once at the top of the chat view – not once per tab. For this release it offers Try vertical tabs, which moves your tabs into the column straight away, and Switch back to top tabs to undo it. The button always matches your current setting, even after a restart. Click × to dismiss the card; it stays gone in every chat view until the next update with something new. To see it again, run Show what's new from the command palette. New installs start on vertical tabs already, so they don't get the card.

Creating tabs
Three ways:
- + button at the right of the tab bar — opens a new tab with the active tab's agent
- Right-click the + to pick a different agent for the new tab (agent picker)
- Command palette → "New tab" — same as the + button
Each new tab starts connecting to a fresh agent session immediately, so pasted text is ready to send without typing an extra character first. The tab inherits the active note as context if Active note as default context is enabled.
Switching tabs
- Click a tab to switch
- Hotkeys — assign in Settings → Hotkeys:
Focus next chat view(recommendCmd/Ctrl + ])Focus previous chat view(recommendCmd/Ctrl + [)
- Keyboard — press
Tabto reach the tab bar. It lands on the current tab, which shows a focus ring. Use←/→to move between tabs (it wraps around), andHome/Endto jump to the first or last tab. Moving the focus doesn't switch tabs. PressEnterorSpaceto open the focused tab, orShift + F10to open its menu. - Scroll position is preserved — each tab remembers where you left it
Reordering tabs
Drag a tab along the tab bar to reorder. The order persists for the session.
Tab titles
Get a useful tab name without thinking about it. Settings → Agent Console → Tabs → Session title controls how each new chat is labeled:
- Suggested by the agent in its first reply (default) — the agent reads your first message and proposes a short title, which appears as soon as its reply starts. Until then the tab shows a preview of your first message, so the tab is never blank. If your agent doesn't propose one, the preview just stays.
- Generated from your first message — the tab is named from the start of your first message. No agent involvement.
- Agent name and timestamp — the tab keeps the plain "agent + time" name it opens with and never changes on its own.
You can rename any tab yourself at any time (see below) — a manual rename always wins and is never overwritten by a suggestion. The chat header shows the same title for the chat you're in.

Renaming tabs
Right-click a tab → Rename. Names must be unique within the session (duplicate rename is rejected). Names persist across reloads if the session was saved.
Rename with AI
Get a fresh title for where the conversation is now — not just where it started. Right-click a tab → Rename with AI, or run Rename current tab with AI from the command palette. The tab's agent reads a short summary of the chat and proposes a title; a small ✨ pulses on the tab while it works.

- The request runs off to the side — your conversation and its saved history are not changed, and you can keep chatting while it runs.
- If you rename the tab yourself before the title comes back, your name wins.
- If another open tab already has that name, the new title gets a number, like
Fix scroll jitter (2). - The title is saved to session history, the same as a manual rename.
- Use it when the automatic title didn't show up, or when the chat has moved on to a different topic.
- It's greyed out for agents that can't close a side conversation, such as Kiro CLI on the V2 engine. On those agents each request would leave a second copy of the agent's tools running until you closed the tab. The automatic titles still work.
Linking to a tab's chat
Right-click a tab → Copy link to chat to copy a link that brings you back to this chat from any note. See Chat Links.
Closing tabs
- Close button (×) on the tab — visible on hover
- Middle-click the tab
- Right-click → Close — same as ×
- Vertical tabs: hover a tab and click its × (when names show), or press
Deleteon a focused tab — see Vertical tabs - Right-click → Close Others — closes every tab except this one
- Right-click → Close to the Right — closes all tabs to the right of this one
You can close every tab, including the last one. Closing the final tab clears the workspace to a blank landing screen (below) instead of being blocked — the same way closing the last tab in a browser lands you on a new-tab page. Right-click the only open tab and Close is available there too.
The blank landing screen
Close the last tab and the chat sidebar shows a neutral landing screen — a launcher, not a dead end. Nothing is running; you start a new chat whenever you're ready:
- Type a prompt and send — starts a new chat on your default agent and sends the message, just like typing in a normal composer.
- Fire a quick prompt — any quick prompt that matches the note you're on starts a new chat and runs it.
- New chat / New chat with an agent — start an empty chat on your default agent, or pick the agent first.
- Open session history — browse your saved chats and reopen any of them in a fresh tab.
Bring notes along. The landing has the same note bar as a normal chat. Pin the note you're working on with the + button (or mention others with @), and the notes you pin come along into the new chat as its starting context — so the agent has them from the very first message.
Nothing connects on its own — the landing just waits for you. Restart Obsidian while you're on the landing and it comes back to the landing, not a surprise new session.
Changed your mind about closing? The Reopen closed session tab command (see Commands) brings back the chat you just closed — including the last one — with its full conversation.

Confirm before closing the whole panel
Closing a single tab is easy to undo, but closing the whole panel — Cmd/Ctrl + W while the panel is focused — tears down every open chat at once, including any agents still running. To prevent losing several sessions to one accidental keystroke, Agent Console asks first:
Close Agent Console? You have 3 open chats. Closing this panel will close all of them.
[Cancel] [Close panel]

The prompt appears only when the panel has 2 or more open chats. With a single chat, Cmd/Ctrl + W closes immediately — there's nothing ambiguous to confirm.
Turn it off under Settings → Tabs → "Confirm before closing multiple chats" (on by default).
Scope
This guards the keyboard close (Cmd/Ctrl + W) — the path that most often fires by accident. Closing the panel from the pane menu still closes immediately; reopen recently closed chats from Session history.
Per-tab state
Each tab independently tracks:
- Agent process and session ID
- Mode and model
- Scroll position
- Input text — a half-typed prompt you haven't sent survives switching tabs, closing and reopening the panel, and restarting Obsidian
- Attached files (images, notes)
- Permission queue (pending tool-call approvals)
Switching tabs preserves all of this.
Queue your next message
You don't have to wait for the agent to finish before lining up your next message. While a tab is streaming a reply, type your next message and press Enter — it gets queued and sends automatically the moment the turn finishes. Keep your train of thought moving instead of waiting for the cursor. While the agent is working, the empty composer hints this: "Queue a message – hit Enter to send when {agent} is done."

- One at a time. You can queue exactly one message per tab. While a message is queued the composer locks and shows a Queued — sends when the agent finishes banner with Send now, Edit, and Delete buttons. Send now stops the current reply and sends the queued message right away. Edit brings the message back into the composer so you can adjust it and queue again; Delete discards it and gives you an empty composer. (Edit recovers, Delete removes — the message is never lost just by editing.)
- It waits for a clean finish. A queued message only sends when the reply finishes normally. If the reply ends in an error, or you stop it, the message is not sent. Instead the composer unlocks and your text stays in it as a normal draft, so you can edit it and send it yourself.
- It's safe to lose your place. A queued message is really just your composer text with a "send this next" flag. If you close and reopen the panel, or restart Obsidian, the text comes back as a normal editable draft (the auto-send flag doesn't survive, because the turn it was waiting on is gone). Nothing sends behind your back after a restart.
- Stop still works. The Stop button keeps cancelling the live turn while a message is queued — queuing never takes away your ability to interrupt the agent. Stopping turns the queued message back into a draft.
Text only for now — staged image attachments aren't queued in this version.
Completion notifications
Turn on System notifications in settings to get a notification when an agent finishes a reply — useful when several tabs are working at once and Obsidian is in the background. (Notifications stay quiet while Obsidian is focused.)
- The notification names the tab. The title is the tab's name, so you can tell which conversation just finished without opening Obsidian and scanning the tab bar.
- Click it to jump straight there. Clicking the notification brings the right vault window to the front and switches to that exact tab.
Tab error recovery
If a tab crashes (rare; usually due to an agent process error), the tab shows an error boundary with a Retry button. Click Retry to reset just that tab without affecting others.
Sidebar placement (left or right)
Agent Console lives in the sidebar — dockable on the left or right. Multiplexing happens through in-panel session tabs, not separate editor panes. Choose the side under Settings → Agent Console → Display → Sidebar side.
Each sidebar pane manages its own tabs independently. Open Agent Console in both the left and right sidebars and each keeps its own set of tabs, restoring them separately across restarts.
Broadcast commands
Control multiple tabs at once from the command palette:
| Command | Description |
|---|---|
| Broadcast prompt | Copy the active tab's input text and images to all other tabs |
| Broadcast send | Send messages in all tabs simultaneously |
| Broadcast cancel | Cancel ongoing operations in all tabs |
TIP
Broadcast send is useful for comparing how different agents respond to the same prompt. Pair it with Broadcast prompt to set up the same question across tabs.
A tab that already holds a queued message is skipped by both Broadcast prompt and Broadcast send (overwriting or double-queuing a committed message would lose it), and the skip is reported in the command's summary notice. Broadcast cancel cancels the live turns; any queued message becomes a normal draft in its tab rather than firing into the cancelled turn.
Persistence across restarts
Open tabs survive an Obsidian restart. When you quit and reopen, each sidebar pane brings back its own tabs — same order, same active tab, each tab's conversation visible right away. Turn this off under Settings → Tabs → "Restore tabs on startup" (on by default). Panes restore independently; split views don't merge into one.
Reopen the panel and pick up where you left off
You don't have to restart Obsidian to get your tabs back. Closed the Agent Console panel? Open it again the normal way — the ribbon icon or the Open chat command — and your last set of tabs comes back: every tab, the one you had active, each conversation, and any unsent draft. Opening the panel resumes where you left off, the same way relaunching Obsidian does.
When you actually want a clean slate, choose Open new view (in the tab-bar ⌄ menu, or the command of the same name) — that opens a fresh, empty panel and never pulls back old tabs. So "open" resumes and "new" starts fresh, with no overlap. Prefer everything fresh? Turn off Settings → Tabs → "Restore tabs on startup" and every open starts empty.
Unsent drafts come back too
A half-typed prompt you never sent is restored with its tab. Whether you switch to another tab, close and reopen the panel, or restart Obsidian, the text you were composing is waiting in the composer when you come back — re-typing a long prompt from scratch is exactly the kind of rework this avoids. The draft clears the moment you send it. (Staged image attachments aren't part of the draft yet — text only.)
Reload history that wasn't saved locally
Once in a while a restored tab can't find its saved messages on disk – rare, but it can happen if a write was interrupted while Obsidian was closing. When that happens the tab no longer comes back blank. It shows a short note, "History for this tab is not stored locally," with a Reload from agent button. Click it and the agent replays the earlier conversation, so your history comes back. Nothing reconnects on its own – the reload happens only when you ask for it.
When chats connect
A chat you deliberately create starts connecting immediately. That includes a new tab, New chat, Open new view, and Fork. You can paste a prompt into a fresh tab and send it directly – there is no extra “wake-up” keystroke.
Chats brought back for reading stay disconnected until you interact. This includes tabs restored after a restart or panel reopen, Reopen closed session tab, and Restore from session history. Their saved conversation is visible right away; typing or sending reconnects the agent. If the previous session is gone – the agent restarted or it expired – the tab starts a new session, and your next message brings the earlier conversation along so the agent can continue. A one-time notice says the agent's internal state was not recovered. Very long chats are trimmed to the most recent messages.
Switching the agent for an existing tab also waits for interaction. It rebinds the tab without starting another session, so your next typed or sent message connects to the agent you picked.
Sleeping tabs
Keep lots of tabs open without slowing your computer down. A tab you haven't used for an hour, while you work in another tab, goes to sleep: its agent stops to free memory. An agent with its tools can use several hundred megabytes, so a long day with many tabs adds up.
A sleeping tab shows a small moon instead of its usual dot. Hover it to see "Asleep to save memory." Tabs that come back after you restart Obsidian or reopen the panel, and chats you reopen (a closed tab, or a chat restored from session history), show the moon too. That includes the tab you're looking at, because its agent hasn't picked the conversation back up yet. The conversation stays on screen. Start typing or send a message and the tab wakes up in the same conversation, after a short "connecting" moment. A tab that went to sleep while Obsidian was open wakes with the model, effort and mode it had, even if you picked others in another tab meanwhile. A tab reopened after a restart keeps its mode. Picking a model or mode on a sleeping tab wakes it first, then applies your choice.

A tab never goes to sleep while it's the tab you're looking at, or while something is going on in it: a reply streaming, a permission question, a queued message, a running terminal, an AI rename, or text in the message box.
See also
- Session history — browse past sessions, restore any in a new tab
- Commands & Hotkeys — full list of keyboard shortcuts