v1.4.0-beta.5

Added

• Activity: see what you did per day, per week or over any range. A new page under Upcoming in the sidebar (⌘⇧T). It opens on a day: a strip from Monday to Sunday picks one, then you see the day in short (a few lines by Haiku), your sessions, turns, time, commits, pull requests and cost, when you worked, and what you did per project. Week shows the same numbers and lists for the whole week, with each session once, and Range does that from a date till another date or till today, for up to 62 days. The title and actions stay at the top as you scroll, and a bar under them keeps the days and the numbers. Click a session for what it did, and open it from there. Sessions from your other computers count too. Projects shows the time per project: click one to see only its sessions. Copy for standup gives you the last day you worked, today, this week or your range as Markdown or plain text, for that project if you picked one, and Export… saves the day, the week or the range as CSV or Markdown. Home has a Yesterday card with the day in short. Turn the summaries off in Settings › Conversation. Nothing leaves your computer apart from that summary.
• Activity's bars show how much you did, not how many sessions. Each day's bar is a score against your typical day, the median of your days with sessions in the 4 weeks before. It stacks the time Claude worked, your turns, and your commits and pull requests, each in its own colour. A dashed line marks a typical day, and the label under a bar is the time worked. Hover a day for its score and what went into it, with its sessions and cost. With a project picked, its bars show its share of a normal day.
• Skim the conversation. A finished turn now has less to read: Claude's messages between tool calls fold into the summary line, and a line above the reply says what changed (+42 −7 · 3 files · 2 tests fail · 4m 12s). Nothing is rewritten. Switch back to Full in Settings › Conversation or from the command palette.
• Fade the less important sentences with Haiku. Under a long reply, Seshboard asks once whether you want to try it. Haiku reads your message and the reply, and picks the sentences to keep. The rest fade, and failures, skipped work and questions always stay. Show all text compares the two, and Turn off or Settings › Conversation stops it. It uses your plan, and the tokens show as Skim highlights in Usage. GitHub Copilot's sessions ask separately and use the cheapest model on your Copilot account.
• Start and continue OpenAI Codex sessions. Add a Codex profile in Settings › Profiles (Seshboard offers it when it finds Codex CLI) and the sessions you ran in Codex CLI or the Codex extension show in the sidebar with Codex's mark, in search and on your phone. Start new ones from New session, the queue, schedules and triggers, and continue any of them from the message box, with Codex's own models and effort. The modes work as with Claude: Ask before edits asks before every edit, Accept edits lets edits in the project folder through, Plan mode works read-only and asks Codex to plan first, and Auto mode keeps going without asking, inside the project folder. Codex signs in with its own login (codex login). Delete moves a session's file to the Trash.
• More for Codex sessions. Fork from a reply, edit a message and send it again, ask about the session, rename it, compact its context and see its MCP servers, skills and hooks in Tools, as with Claude. Its 5-hour and weekly limits show under the message box, on Home and in Usage.
• Go through all of a reply's images, and copy them. Full size, ← and → and the strip below now go through every image Claude returned in the reply, not only those from one tool call. Press ⌘C, click Copy or right-click an image to copy it, in the conversation too.

Changed

• New session uses the width of the window: projects on the left, the message box in the middle, and the project's sessions and defaults on the right, without scrolling.
• Home is as wide as New session. On a large screen Home now grows just as far, with the same margins, so nothing jumps when you go from one to the other.
• At the focus limit, New session says so in one line above the box, and Start reads Add to queue (⌘↩). Start anyway is in its menu, unless your limit is Strict.

Fixed

• file:/// links in Claude's replies work. Clicking one did nothing. It now opens the file as any file link does, as Settings › Conversation › Clicking a file link says. On Windows, links to a path such as E:/repos/notes.md work too.

v1.4.0-beta.4

Added

• Activity: see what you did per day, per week or over any range. A new page under Upcoming in the sidebar (⌘⇧T). It opens on a day: a strip from Monday to Sunday picks one, then you see the day in short (a few lines by Haiku), your sessions, turns, time, commits, pull requests and cost, when you worked, and what you did per project. Week shows the same numbers and lists for the whole week, with each session once, and Range does that from a date till another date or till today, for up to 62 days. The title and actions stay at the top as you scroll, and a bar under them keeps the days and the numbers. Click a session for what it did, and open it from there. Sessions from your other computers count too. Projects shows the time per project: click one to see only its sessions. Copy for standup gives you the last day you worked, today, this week or your range as Markdown or plain text, for that project if you picked one, and Export… saves the day, the week or the range as CSV or Markdown. Home has a Yesterday card with the day in short. Turn the summaries off in Settings › Conversation. Nothing leaves your computer apart from that summary.
• Activity's bars show how much you did, not how many sessions. Each day's bar is a score against your typical day, the median of your days with sessions in the 4 weeks before. It stacks the time Claude worked, your turns, and your commits and pull requests, each in its own colour. A dashed line marks a typical day, and the label under a bar is the time worked. Hover a day for its score and what went into it, with its sessions and cost. With a project picked, its bars show its share of a normal day.
• Skim the conversation. A finished turn now has less to read: Claude's messages between tool calls fold into the summary line, and a line above the reply says what changed (+42 −7 · 3 files · 2 tests fail · 4m 12s). Nothing is rewritten. Switch back to Full in Settings › Conversation or from the command palette.
• Fade the less important sentences with Haiku. Under a long reply, Seshboard asks once whether you want to try it. Haiku reads your message and the reply, and picks the sentences to keep. The rest fade, and failures, skipped work and questions always stay. Show all text compares the two, and Turn off or Settings › Conversation stops it. It uses your plan, and the tokens show as Skim highlights in Usage. GitHub Copilot's sessions ask separately and use the cheapest model on your Copilot account.
• Go through all of a reply's images, and copy them. Full size, ← and → and the strip below now go through every image Claude returned in the reply, not only those from one tool call. Press ⌘C, click Copy or right-click an image to copy it, in the conversation too.

Changed

• New session uses the width of the window: projects on the left, the message box in the middle, and the project's sessions and defaults on the right, without scrolling.
• At the focus limit, New session says so in one line above the box, and Start reads Add to queue (⌘↩). Start anyway is in its menu, unless your limit is Strict.

Fixed

• file:/// links in Claude's replies work. Clicking one did nothing. It now opens the file as any file link does, as Settings › Conversation › Clicking a file link says. On Windows, links to a path such as E:/repos/notes.md work too.

v1.4.0-beta.3

Added

• Activity: see what you did per day, per week or over any range. A new page under Upcoming in the sidebar (⌘⇧T). It opens on a day: a strip from Monday to Sunday picks one, then you see the day in short (a few lines by Haiku), your sessions, turns, time, commits, pull requests and cost, when you worked, and what you did per project. Week shows the same numbers and lists for the whole week, with each session once, and Range does that from a date till another date or till today, for up to 62 days. The title and actions stay at the top as you scroll, and a bar under them keeps the days and the numbers. Click a session for what it did, and open it from there. Sessions from your other computers count too. Projects shows the time per project: click one to see only its sessions. Copy for standup gives you the last day you worked, today, this week or your range as Markdown or plain text, for that project if you picked one, and Export… saves the day, the week or the range as CSV or Markdown. Home has a Yesterday card with the day in short. Turn the summaries off in Settings › Conversation. Nothing leaves your computer apart from that summary.
• Skim the conversation. A finished turn now has less to read: Claude's messages between tool calls fold into the summary line, and a line above the reply says what changed (+42 −7 · 3 files · 2 tests fail · 4m 12s). Nothing is rewritten. Switch back to Full in Settings › Conversation or from the command palette.
• Fade the less important sentences with Haiku. Under a long reply, Seshboard asks once whether you want to try it. Haiku reads your message and the reply, and picks the sentences to keep. The rest fade, and failures, skipped work and questions always stay. Show all text compares the two, and Turn off or Settings › Conversation stops it. It uses your plan, and the tokens show as Skim highlights in Usage. GitHub Copilot's sessions ask separately and use the cheapest model on your Copilot account.

v1.4.0-beta.2

Added

• Activity: see what you did per day, per week or over any range. A new page under Upcoming in the sidebar (⌘⇧T). It opens on a day: a strip from Monday to Sunday picks one, then you see the day in short (a few lines by Haiku), your sessions, turns, time, commits, pull requests and cost, when you worked, and what you did per project. Week shows the same numbers and lists for the whole week, with each session once, and Range does that from a date till another date or till today, for up to 62 days. The title and actions stay at the top as you scroll, and a bar under them keeps the days and the numbers. Click a session for what it did, and open it from there. Sessions from your other computers count too. Projects shows the time per project: click one to see only its sessions. Copy for standup gives you the last day you worked, today, this week or your range as Markdown or plain text, for that project if you picked one, and Export… saves the day, the week or the range as CSV or Markdown. Home has a Yesterday card with the day in short. Turn the summaries off in Settings › Conversation. Nothing leaves your computer apart from that summary.
• Skim the conversation. A finished turn now has less to read: Claude's messages between tool calls fold into the summary line, a line above the reply says what changed (+42 −7 · 3 files · 2 tests fail · 4m 12s), and less important sentences in the reply fade. Nothing is rewritten: failures, skipped work, questions, numbers and code never fade, and Show all text restores a reply. Switch back to Full in Settings › Conversation or from the command palette.

v1.4.0-beta.1

Added

• Activity: see what you did per day or per week. A new page under Upcoming in the sidebar (⌘⇧T). It opens on a day: a week strip picks one, then you see the day in short (a few lines by Haiku), your sessions, turns, time, commits, pull requests and cost, when you worked, and what you did per project. Week shows all of that for the last seven days, with each session once. The title and actions stay at the top as you scroll, and a bar under them keeps the days and the numbers. Click a session for what it did, and open it from there. Sessions from your other computers count too. Projects shows the time per project: click one to see only its sessions. Copy for standup gives you the last day you worked, today or this week as Markdown or plain text, for that project if you picked one, and Export… saves the day or the week as CSV or Markdown. Home has a Yesterday card with the day in short. Turn the summaries off in Settings › Conversation. Nothing leaves your computer apart from that summary.
• Skim the conversation. A finished turn now has less to read: Claude's messages between tool calls fold into the summary line, a line above the reply says what changed (+42 −7 · 3 files · 2 tests fail · 4m 12s), and less important sentences in the reply fade. Nothing is rewritten: failures, skipped work, questions, numbers and code never fade, and Show all text restores a reply. Switch back to Full in Settings › Conversation or from the command palette.

v1.3.0

Added

• Fast mode. On a model that has it, the lightning bolt under the message box turns on fast mode for that session, up to 2.5x faster at a higher price per token. On a Claude subscription it always bills to usage credits. Its tooltip says what it does and costs, and why it isn't running if it can't, such as being out of credits. Also on New session, so the first message runs fast too, in the command palette and with /fast. It is off every time you start or resume a session.
• Home uses the whole window: a start box, lanes for what needs you, what's working and what to review, then your projects and usage. Type a project's name and what Claude should do, then press Return to open New session with both filled in, or press ⌘1 to ⌘9 to pick a project. A To review card opens its session with the catch-up. Profiles without sessions today fold into one line each.
• To review and Open. The sidebar now says what is still yours instead of grouping by day: To review has the finished sessions you haven't read, Open the ones you read but haven't marked done, newest first. Today, Yesterday and Earlier are gone; each row still shows its age. A session with an unsent message or a queued prompt stays listed however old it is, here, in VS Code and on your phone, so it never slips into Done. On your phone the list has the same sections.
• Go through your sessions one by one. The sidebar footer counts what is open ("7 open"). Click it to open the first session to review with its catch-up. Skip (S) goes on to the next one, To review first, then Open, and leaves the one you skipped as it was. Done (E) goes on to the same next one. The catch-up says where you are ("2 of 7"), and when there is nothing left you're back Home.
• Archive is now Done. What you finished, and what went quiet, sits in Done under the list. Each row says why: "Done" when you marked it, or "Inactive 3 days" when it went quiet, and those are dimmed so they don't look finished by you. Mark a session done with the checkmark on its row, E, a middle-click, its menu or its catch-up; Reopen brings it back. Settings › Sessions, Manage sessions, the command palette and your phone say Done too. The keys didn't change.
• A note on what's left. Give a session one line, such as "push after review" or "waiting on Jan": press N on its row or in its catch-up, or pick Note… in its menu or the command palette. It shows under the title in the sidebar (in the tooltip with the compact style), and search finds it. A catch-up that needs something from you offers Use as note to put that there in one click. Done keeps the note but doesn't show it.
• Loose ends. A session that left something behind has a small marker on its row: files not committed, commits not pushed, a pull request with failing checks, or one closed without merging (and a queued prompt). Hover it to see what. Such a session never goes to Done by itself after the days you set. Marking it done yourself still works, and the toast says what's left ("3 files not committed"). Seshboard looks when a turn ends, when you come back to the window, and every few minutes.
• A merged pull request moves its session to Done. When the pull request of a session merges, the session goes to Done and its row says "Merged #123". You get one toast for them the next time you're in Seshboard, with Undo. A session that is pinned, working, waiting for you, open in Seshboard, active since the merge or with loose ends left stays where it is, and one you reopen stays open. Turn it off in Settings › Sessions › Move to Done when its pull request merges.
• Remind me later. Press L on a session (or several), in its catch-up, its menu or the command palette, and pick In 1 hour, This evening, Tomorrow, Monday or a time of your own, with an optional note. The session leaves the list until then, then comes back under Reminders, above To review, with a notification ("Reminder: …"), and stays there until you open it. One that came due while Seshboard was closed says when it was for. If Claude needs you, fails or starts working in it, it comes back at once. Upcoming has a Reminders filter, with Edit, Remind now and Cancel, and its sidebar row counts them. Settings › Notifications can turn reminder notifications off, or count them in the app icon's badge. In catch-up, L goes on to the next session, as Skip does.
• Quick start from anywhere. Press ⌃⌥Space in any app to start a session: pick a project, type the task, and it runs in the background without bringing Seshboard forward. ⌘↩ starts it and opens Seshboard, and ⌘K has more: start in a new worktree, change the model, mode or profile, attach the clipboard, or add it to Later instead. What needs you is listed on top, and Esc keeps what you typed for five minutes. On Windows and Linux the shortcut is Ctrl+Alt+Space. Change it, or turn off starting in the background, in Settings › General › Quick start.
• Defaults for GitHub Copilot sessions. A Copilot profile now has New session defaults in Settings › Profiles, as Claude profiles do: its model and effort (from Copilot's own models), its permission mode and its workspace (current folder or a new worktree). A project on a Copilot profile sets the same in its Settings. New session starts Copilot sessions with them. The global model and effort in Settings › General are Claude's, so Copilot sessions without a model start on Copilot's default; the global permission mode applies to both.
• Copilot CLI updates, like Claude Code's. With a GitHub Copilot profile, Settings › About shows GitHub Copilot CLI too: the version you have, whether a newer one is out, and Update. A toast says when a new version is available, as it does for Claude Code. Seshboard uses the new version the next time it opens.
• Seshboard lives in the menu bar too. It lights up while sessions work, shows what needs you with Allow right there, and starts new work in the background. Right-click it for Open Seshboard, New session…, Pause notifications and Quit. On Windows it's in the notification area; on Linux it's a menu. Settings › General › Menu bar turns it off, keeps Seshboard running when you close the window, and (on a Mac) hides the Dock icon while no window is open.
• Getting started with GitHub Copilot. When Seshboard finds Copilot CLI, Profiles offers to add it. Adding a Copilot profile skips sign-in when you're already signed in, and ends with ways to start using it. New session says what it turned off when you switch to Copilot.
• GitHub Copilot sessions. Add a GitHub Copilot profile in Settings › Profiles (now Profiles, with Claude Code and Copilot ones) and pick it in New session, or link a project to it, to start a Copilot session in Seshboard, with Copilot's models (and Copilot Fusion: its tiers, such as Fusion Standard and Fusion Max, are in the model menu after Auto, with a recent Copilot CLI), its permission prompts as cards, and its replies as they stream. Copilot runs with your own Copilot CLI and the profile's login: Seshboard never asks for a token, and the profile's Sign in runs Copilot's own sign in. Two Copilot accounts can be two profiles, as with Claude. Sessions you started in Copilot CLI or in VS Code show up too when Show sessions from other apps is on (Settings › Sidebar), and you can continue them here. Each session's row and header show whose it is with the Claude or Copilot mark, the profile chip under the message box shows the mark in the profile's colour, and a working session says who is working ("GitHub Copilot is working"). The permission modes are the same as Claude's (Ask before edits, Accept edits, Plan mode and Auto mode): in Auto mode, Copilot runs as its autopilot and doesn't ask before commands, and switching to it allows the requests already waiting. Its slash commands are there too, in the message box, and so are its MCP servers, agents and skills in Tools, Compact, Up next, Send now and steering while it works, and its context and premium requests under the message box. On your phone, New session can start a Copilot session too (pick the Copilot profile in Options), and so can New session on another paired computer (Run on), with Copilot's own models and modes, in a worktree or on a branch there. A session open in Copilot CLI in a terminal shows as working there, and Seshboard waits until it is closed before continuing it. Fork, Edit and resend, Rewind, Rename and Delete work for Copilot sessions too, through Copilot's own tools: Rewind takes the conversation back to before your message with the files Copilot changed, and puts the message back in the box; Rename shows in Copilot CLI too; Delete moves the session to the Trash, and archived Copilot sessions are cleaned up like Claude Code's. A Copilot model that takes an effort level gets the effort chip, and its background commands and agents show in the background tasks pill, with Stop. Add to queue, Schedule… and Start when… work with a Copilot profile too: the queued item, the scheduled run or the triggered session starts Copilot with its model, effort and mode. A Copilot session can start in a new worktree or on another branch too, from New session, the queue, a schedule or a trigger, as a Claude Code session does, with the project's setup actions before its first message. A pipeline step can run with Copilot too (Runs with in the step, once you have a Copilot profile), with Copilot's models and modes; a read-only step only reads, and a step forks only a step of the same tool. Linking sessions with @ works in a Copilot session too: the linked session's brief (and an attached issue) goes with your message, as it does for Claude. Files and lines you add from the VS Code companion, by drag and drop or with @ reach Copilot as attachments, so it reads them as Claude does. Copilot's su...

v1.3.0-beta.20

Added

• Home uses the whole window: a start box, lanes for what needs you, what's working and what to review, then your projects and usage. Type a project's name and what Claude should do, then press Return to open New session with both filled in, or press ⌘1 to ⌘9 to pick a project. A To review card opens its session with the catch-up. Profiles without sessions today fold into one line each.
• To review and Open. The sidebar now says what is still yours instead of grouping by day: To review has the finished sessions you haven't read, Open the ones you read but haven't marked done, newest first. Today, Yesterday and Earlier are gone; each row still shows its age. A session with an unsent message or a queued prompt stays listed however old it is, here, in VS Code and on your phone, so it never slips into Done. On your phone the list has the same sections.
• Go through your sessions one by one. The sidebar footer counts what is open ("7 open"). Click it to open the first session to review with its catch-up. Skip (S) goes on to the next one, To review first, then Open, and leaves the one you skipped as it was. Done (E) goes on to the same next one. The catch-up says where you are ("2 of 7"), and when there is nothing left you're back Home.
• Archive is now Done. What you finished, and what went quiet, sits in Done under the list. Each row says why: "Done" when you marked it, or "Inactive 3 days" when it went quiet, and those are dimmed so they don't look finished by you. Mark a session done with the checkmark on its row, E, a middle-click, its menu or its catch-up; Reopen brings it back. Settings › Sessions, Manage sessions, the command palette and your phone say Done too. The keys didn't change.
• A note on what's left. Give a session one line, such as "push after review" or "waiting on Jan": press N on its row or in its catch-up, or pick Note… in its menu or the command palette. It shows under the title in the sidebar (in the tooltip with the compact style), and search finds it. A catch-up that needs something from you offers Use as note to put that there in one click. Done keeps the note but doesn't show it.
• Loose ends. A session that left something behind has a small marker on its row: files not committed, commits not pushed, a pull request with failing checks, or one closed without merging (and a queued prompt). Hover it to see what. Such a session never goes to Done by itself after the days you set. Marking it done yourself still works, and the toast says what's left ("3 files not committed"). Seshboard looks when a turn ends, when you come back to the window, and every few minutes.
• A merged pull request moves its session to Done. When the pull request of a session merges, the session goes to Done and its row says "Merged #123". You get one toast for them the next time you're in Seshboard, with Undo. A session that is pinned, working, waiting for you, open in Seshboard, active since the merge or with loose ends left stays where it is, and one you reopen stays open. Turn it off in Settings › Sessions › Move to Done when its pull request merges.
• Remind me later. Press L on a session (or several), in its catch-up, its menu or the command palette, and pick In 1 hour, This evening, Tomorrow, Monday or a time of your own, with an optional note. The session leaves the list until then, then comes back under Reminders, above To review, with a notification ("Reminder: …"), and stays there until you open it. One that came due while Seshboard was closed says when it was for. If Claude needs you, fails or starts working in it, it comes back at once. Upcoming has a Reminders filter, with Edit, Remind now and Cancel, and its sidebar row counts them. Settings › Notifications can turn reminder notifications off, or count them in the app icon's badge. In catch-up, L goes on to the next session, as Skip does.
• Quick start from anywhere. Press ⌃⌥Space in any app to start a session: pick a project, type the task, and it runs in the background without bringing Seshboard forward. ⌘↩ starts it and opens Seshboard, and ⌘K has more: start in a new worktree, change the model, mode or profile, attach the clipboard, or add it to Later instead. What needs you is listed on top, and Esc keeps what you typed for five minutes. On Windows and Linux the shortcut is Ctrl+Alt+Space. Change it, or turn off starting in the background, in Settings › General › Quick start.
• Defaults for GitHub Copilot sessions. A Copilot profile now has New session defaults in Settings › Profiles, as Claude profiles do: its model and effort (from Copilot's own models), its permission mode and its workspace (current folder or a new worktree). A project on a Copilot profile sets the same in its Settings. New session starts Copilot sessions with them. The global model and effort in Settings › General are Claude's, so Copilot sessions without a model start on Copilot's default; the global permission mode applies to both.
• Copilot CLI updates, like Claude Code's. With a GitHub Copilot profile, Settings › About shows GitHub Copilot CLI too: the version you have, whether a newer one is out, and Update. A toast says when a new version is available, as it does for Claude Code. Seshboard uses the new version the next time it opens.
• Seshboard lives in the menu bar too. It lights up while sessions work, shows what needs you with Allow right there, and starts new work in the background. Right-click it for Open Seshboard, New session…, Pause notifications and Quit. On Windows it's in the notification area; on Linux it's a menu. Settings › General › Menu bar turns it off, keeps Seshboard running when you close the window, and (on a Mac) hides the Dock icon while no window is open.
• Getting started with GitHub Copilot. When Seshboard finds Copilot CLI, Profiles offers to add it. Adding a Copilot profile skips sign-in when you're already signed in, and ends with ways to start using it. New session says what it turned off when you switch to Copilot.
• GitHub Copilot sessions. Add a GitHub Copilot profile in Settings › Profiles (now Profiles, with Claude Code and Copilot ones) and pick it in New session, or link a project to it, to start a Copilot session in Seshboard, with Copilot's models (and Copilot Fusion: its tiers, such as Fusion Standard and Fusion Max, are in the model menu after Auto, with a recent Copilot CLI), its permission prompts as cards, and its replies as they stream. Copilot runs with your own Copilot CLI and the profile's login: Seshboard never asks for a token, and the profile's Sign in runs Copilot's own sign in. Two Copilot accounts can be two profiles, as with Claude. Sessions you started in Copilot CLI or in VS Code show up too when Show sessions from other apps is on (Settings › Sidebar), and you can continue them here. Each session's row and header show whose it is with the Claude or Copilot mark, the profile chip under the message box shows the mark in the profile's colour, and a working session says who is working ("GitHub Copilot is working"). The permission modes are the same as Claude's (Ask before edits, Accept edits, Plan mode and Auto mode): in Auto mode, Copilot runs as its autopilot and doesn't ask before commands, and switching to it allows the requests already waiting. Its slash commands are there too, in the message box, and so are its MCP servers, agents and skills in Tools, Compact, Up next, Send now and steering while it works, and its context and premium requests under the message box. On your phone, New session can start a Copilot session too (pick the Copilot profile in Options), and so can New session on another paired computer (Run on), with Copilot's own models and modes, in a worktree or on a branch there. A session open in Copilot CLI in a terminal shows as working there, and Seshboard waits until it is closed before continuing it. Fork, Edit and resend, Rewind, Rename and Delete work for Copilot sessions too, through Copilot's own tools: Rewind takes the conversation back to before your message with the files Copilot changed, and puts the message back in the box; Rename shows in Copilot CLI too; Delete moves the session to the Trash, and archived Copilot sessions are cleaned up like Claude Code's. A Copilot model that takes an effort level gets the effort chip, and its background commands and agents show in the background tasks pill, with Stop. Add to queue, Schedule… and Start when… work with a Copilot profile too: the queued item, the scheduled run or the triggered session starts Copilot with its model, effort and mode. A Copilot session can start in a new worktree or on another branch too, from New session, the queue, a schedule or a trigger, as a Claude Code session does, with the project's setup actions before its first message. A pipeline step can run with Copilot too (Runs with in the step, once you have a Copilot profile), with Copilot's models and modes; a read-only step only reads, and a step forks only a step of the same tool. Linking sessions with @ works in a Copilot session too: the linked session's brief (and an attached issue) goes with your message, as it does for Claude. Files and lines you add from the VS Code companion, by drag and drop or with @ reach Copilot as attachments, so it reads them as Claude does. Copilot's subagents show what they did, under their card and in Agents (in the ⋯ menu), as Claude's do. Ask about this session works in a Copilot session too, on the computer and on your phone: a throwaway copy of the session answers with tools that only read, nothing reaches the conversation, and the answer costs a premium request or so. A Copilot slash command that answers in words stays in the conversation after a restart, where you ran it. Usage shows a Copilot profile's prem...

v1.3.0-beta.19

Added

• Home uses the whole window: a start box, lanes for what needs you, what's working and what to review, then your projects and usage. Type a project's name and what Claude should do, then press Return to open New session with both filled in, or press ⌘1 to ⌘9 to pick a project. A To review card opens its session with the catch-up. Profiles without sessions today fold into one line each.
• To review and Open. The sidebar now says what is still yours instead of grouping by day: To review has the finished sessions you haven't read, Open the ones you read but haven't marked done, newest first. Today, Yesterday and Earlier are gone; each row still shows its age. A session with an unsent message or a queued prompt stays listed however old it is, here, in VS Code and on your phone, so it never slips into Done. On your phone the list has the same sections.
• Go through your sessions one by one. The sidebar footer counts what is open ("7 open"). Click it to open the first session to review with its catch-up. Skip (S) goes on to the next one, To review first, then Open, and leaves the one you skipped as it was. Done (E) goes on to the same next one. The catch-up says where you are ("2 of 7"), and when there is nothing left you're back Home.
• Archive is now Done. What you finished, and what went quiet, sits in Done under the list. Each row says why: "Done" when you marked it, or "Inactive 3 days" when it went quiet, and those are dimmed so they don't look finished by you. Mark a session done with the checkmark on its row, E, a middle-click, its menu or its catch-up; Reopen brings it back. Settings › Sessions, Manage sessions, the command palette and your phone say Done too. The keys didn't change.
• A note on what's left. Give a session one line, such as "push after review" or "waiting on Jan": press N on its row or in its catch-up, or pick Note… in its menu or the command palette. It shows under the title in the sidebar (in the tooltip with the compact style), and search finds it. A catch-up that needs something from you offers Use as note to put that there in one click. Done keeps the note but doesn't show it.
• Loose ends. A session that left something behind has a small marker on its row: files not committed, commits not pushed, a pull request with failing checks, or one closed without merging (and a queued prompt). Hover it to see what. Such a session never goes to Done by itself after the days you set. Marking it done yourself still works, and the toast says what's left ("3 files not committed"). Seshboard looks when a turn ends, when you come back to the window, and every few minutes.
• A merged pull request moves its session to Done. When the pull request of a session merges, the session goes to Done and its row says "Merged #123". You get one toast for them the next time you're in Seshboard, with Undo. A session that is pinned, working, waiting for you, open in Seshboard, active since the merge or with loose ends left stays where it is, and one you reopen stays open. Turn it off in Settings › Sessions › Move to Done when its pull request merges.
• Remind me later. Press L on a session (or several), in its catch-up, its menu or the command palette, and pick In 1 hour, This evening, Tomorrow, Monday or a time of your own, with an optional note. The session leaves the list until then, then comes back under Reminders, above To review, with a notification ("Reminder: …"), and stays there until you open it. One that came due while Seshboard was closed says when it was for. If Claude needs you, fails or starts working in it, it comes back at once. Upcoming has a Reminders filter, with Edit, Remind now and Cancel, and its sidebar row counts them. Settings › Notifications can turn reminder notifications off, or count them in the app icon's badge. In catch-up, L goes on to the next session, as Skip does.
• Quick start from anywhere. Press ⌃⌥Space in any app to start a session: pick a project, type the task, and it runs in the background without bringing Seshboard forward. ⌘↩ starts it and opens Seshboard, and ⌘K has more: start in a new worktree, change the model, mode or profile, attach the clipboard, or add it to Later instead. What needs you is listed on top, and Esc keeps what you typed for five minutes. On Windows and Linux the shortcut is Ctrl+Alt+Space. Change it, or turn off starting in the background, in Settings › General › Quick start.
• Defaults for GitHub Copilot sessions. A Copilot profile now has New session defaults in Settings › Profiles, as Claude profiles do: its model and effort (from Copilot's own models), its permission mode and its workspace (current folder or a new worktree). A project on a Copilot profile sets the same in its Settings. New session starts Copilot sessions with them. The global model and effort in Settings › General are Claude's, so Copilot sessions without a model start on Copilot's default; the global permission mode applies to both.
• Copilot CLI updates, like Claude Code's. With a GitHub Copilot profile, Settings › About shows GitHub Copilot CLI too: the version you have, whether a newer one is out, and Update. A toast says when a new version is available, as it does for Claude Code. Seshboard uses the new version the next time it opens.
• Seshboard lives in the menu bar too. It lights up while sessions work, shows what needs you with Allow right there, and starts new work in the background. Right-click it for Open Seshboard, New session…, Pause notifications and Quit. On Windows it's in the notification area; on Linux it's a menu. Settings › General › Menu bar turns it off, keeps Seshboard running when you close the window, and (on a Mac) hides the Dock icon while no window is open.
• Getting started with GitHub Copilot. When Seshboard finds Copilot CLI, Profiles offers to add it. Adding a Copilot profile skips sign-in when you're already signed in, and ends with ways to start using it. New session says what it turned off when you switch to Copilot.
• GitHub Copilot sessions. Add a GitHub Copilot profile in Settings › Profiles (now Profiles, with Claude Code and Copilot ones) and pick it in New session, or link a project to it, to start a Copilot session in Seshboard, with Copilot's models (and Copilot Fusion: its tiers, such as Fusion Standard and Fusion Max, are in the model menu after Auto, with a recent Copilot CLI), its permission prompts as cards, and its replies as they stream. Copilot runs with your own Copilot CLI and the profile's login: Seshboard never asks for a token, and the profile's Sign in runs Copilot's own sign in. Two Copilot accounts can be two profiles, as with Claude. Sessions you started in Copilot CLI or in VS Code show up too when Show sessions from other apps is on (Settings › Sidebar), and you can continue them here. Each session's row and header show whose it is with the Claude or Copilot mark, the profile chip under the message box shows the mark in the profile's colour, and a working session says who is working ("GitHub Copilot is working"). The permission modes are the same as Claude's (Ask before edits, Accept edits, Plan mode and Auto mode): in Auto mode, Copilot runs as its autopilot and doesn't ask before commands, and switching to it allows the requests already waiting. Its slash commands are there too, in the message box, and so are its MCP servers, agents and skills in Tools, Compact, Up next, Send now and steering while it works, and its context and premium requests under the message box. On your phone, New session can start a Copilot session too (pick the Copilot profile in Options), and so can New session on another paired computer (Run on), with Copilot's own models and modes, in a worktree or on a branch there. A session open in Copilot CLI in a terminal shows as working there, and Seshboard waits until it is closed before continuing it. Fork, Edit and resend, Rewind, Rename and Delete work for Copilot sessions too, through Copilot's own tools: Rewind takes the conversation back to before your message with the files Copilot changed, and puts the message back in the box; Rename shows in Copilot CLI too; Delete moves the session to the Trash, and archived Copilot sessions are cleaned up like Claude Code's. A Copilot model that takes an effort level gets the effort chip, and its background commands and agents show in the background tasks pill, with Stop. Add to queue, Schedule… and Start when… work with a Copilot profile too: the queued item, the scheduled run or the triggered session starts Copilot with its model, effort and mode. A Copilot session can start in a new worktree or on another branch too, from New session, the queue, a schedule or a trigger, as a Claude Code session does, with the project's setup actions before its first message. A pipeline step can run with Copilot too (Runs with in the step, once you have a Copilot profile), with Copilot's models and modes; a read-only step only reads, and a step forks only a step of the same tool. Linking sessions with @ works in a Copilot session too: the linked session's brief (and an attached issue) goes with your message, as it does for Claude. Files and lines you add from the VS Code companion, by drag and drop or with @ reach Copilot as attachments, so it reads them as Claude does. Copilot's subagents show what they did, under their card and in Agents (in the ⋯ menu), as Claude's do. Ask about this session works in a Copilot session too, on the computer and on your phone: a throwaway copy of the session answers with tools that only read, nothing reaches the conversation, and the answer costs a premium request or so. A Copilot slash command that answers in words stays in the conversation after a restart, where you ran it. Usage shows a Copilot profile's prem...

v1.3.0-beta.18

Added

• Home uses the whole window: a start box, lanes for what needs you, what's working and what to review, then your projects and usage. Type a project's name and what Claude should do, then press Return to open New session with both filled in, or press ⌘1 to ⌘9 to pick a project. A To review card opens its session with the catch-up. Profiles without sessions today fold into one line each.
• To review and Open. The sidebar now says what is still yours instead of grouping by day: To review has the finished sessions you haven't read, Open the ones you read but haven't marked done, newest first. Today, Yesterday and Earlier are gone; each row still shows its age. A session with an unsent message or a queued prompt stays listed however old it is, here, in VS Code and on your phone, so it never slips into Done. On your phone the list has the same sections.
• Go through your sessions one by one. The sidebar footer counts what is open ("7 open"). Click it to open the first session to review with its catch-up. Skip (S) goes on to the next one, To review first, then Open, and leaves the one you skipped as it was. Done (E) goes on to the same next one. The catch-up says where you are ("2 of 7"), and when there is nothing left you're back Home.
• Archive is now Done. What you finished, and what went quiet, sits in Done under the list. Each row says why: "Done" when you marked it, or "Inactive 3 days" when it went quiet, and those are dimmed so they don't look finished by you. Mark a session done with the checkmark on its row, E, a middle-click, its menu or its catch-up; Reopen brings it back. Settings › Sessions, Manage sessions, the command palette and your phone say Done too. The keys didn't change.
• A note on what's left. Give a session one line, such as "push after review" or "waiting on Jan": press N on its row or in its catch-up, or pick Note… in its menu or the command palette. It shows under the title in the sidebar (in the tooltip with the compact style), and search finds it. A catch-up that needs something from you offers Use as note to put that there in one click. Done keeps the note but doesn't show it.
• Loose ends. A session that left something behind has a small marker on its row: files not committed, commits not pushed, a pull request with failing checks, or one closed without merging (and a queued prompt). Hover it to see what. Such a session never goes to Done by itself after the days you set. Marking it done yourself still works, and the toast says what's left ("3 files not committed"). Seshboard looks when a turn ends, when you come back to the window, and every few minutes.
• A merged pull request moves its session to Done. When the pull request of a session merges, the session goes to Done and its row says "Merged #123". You get one toast for them the next time you're in Seshboard, with Undo. A session that is pinned, working, waiting for you, open in Seshboard, active since the merge or with loose ends left stays where it is, and one you reopen stays open. Turn it off in Settings › Sessions › Move to Done when its pull request merges.
• Remind me later. Press L on a session (or several), in its catch-up, its menu or the command palette, and pick In 1 hour, This evening, Tomorrow, Monday or a time of your own, with an optional note. The session leaves the list until then, then comes back under Reminders, above To review, with a notification ("Reminder: …"), and stays there until you open it. One that came due while Seshboard was closed says when it was for. If Claude needs you, fails or starts working in it, it comes back at once. Upcoming has a Reminders filter, with Edit, Remind now and Cancel, and its sidebar row counts them. Settings › Notifications can turn reminder notifications off, or count them in the app icon's badge. In catch-up, L goes on to the next session, as Skip does.
• Quick start from anywhere. Press ⌃⌥Space in any app to start a session: pick a project, type the task, and it runs in the background without bringing Seshboard forward. ⌘↩ starts it and opens Seshboard, and ⌘K has more: start in a new worktree, change the model, mode or profile, attach the clipboard, or add it to Later instead. What needs you is listed on top, and Esc keeps what you typed for five minutes. On Windows and Linux the shortcut is Ctrl+Alt+Space. Change it, or turn off starting in the background, in Settings › General › Quick start.
• Defaults for GitHub Copilot sessions. A Copilot profile now has New session defaults in Settings › Profiles, as Claude profiles do: its model and effort (from Copilot's own models), its permission mode and its workspace (current folder or a new worktree). A project on a Copilot profile sets the same in its Settings. New session starts Copilot sessions with them. The global model and effort in Settings › General are Claude's, so Copilot sessions without a model start on Copilot's default; the global permission mode applies to both.
• Copilot CLI updates, like Claude Code's. With a GitHub Copilot profile, Settings › About shows GitHub Copilot CLI too: the version you have, whether a newer one is out, and Update. A toast says when a new version is available, as it does for Claude Code. Seshboard uses the new version the next time it opens.
• Seshboard lives in the menu bar too. It lights up while sessions work, shows what needs you with Allow right there, and starts new work in the background. Right-click it for Open Seshboard, New session…, Pause notifications and Quit. On Windows it's in the notification area; on Linux it's a menu. Settings › General › Menu bar turns it off, keeps Seshboard running when you close the window, and (on a Mac) hides the Dock icon while no window is open.
• Getting started with GitHub Copilot. When Seshboard finds Copilot CLI, Profiles offers to add it. Adding a Copilot profile skips sign-in when you're already signed in, and ends with ways to start using it. New session says what it turned off when you switch to Copilot.
• GitHub Copilot sessions. Add a GitHub Copilot profile in Settings › Profiles (now Profiles, with Claude Code and Copilot ones) and pick it in New session, or link a project to it, to start a Copilot session in Seshboard, with Copilot's models (and Copilot Fusion: its tiers, such as Fusion Standard and Fusion Max, are in the model menu after Auto, with a recent Copilot CLI), its permission prompts as cards, and its replies as they stream. Copilot runs with your own Copilot CLI and the profile's login: Seshboard never asks for a token, and the profile's Sign in runs Copilot's own sign in. Two Copilot accounts can be two profiles, as with Claude. Sessions you started in Copilot CLI or in VS Code show up too when Show sessions from other apps is on (Settings › Sidebar), and you can continue them here. Each session's row and header show whose it is with the Claude or Copilot mark, the profile chip under the message box shows the mark in the profile's colour, and a working session says who is working ("GitHub Copilot is working"). The permission modes are the same as Claude's (Ask before edits, Accept edits, Plan mode and Auto mode): in Auto mode, Copilot runs as its autopilot and doesn't ask before commands, and switching to it allows the requests already waiting. Its slash commands are there too, in the message box, and so are its MCP servers, agents and skills in Tools, Compact, Up next, Send now and steering while it works, and its context and premium requests under the message box. On your phone, New session can start a Copilot session too (pick the Copilot profile in Options), and so can New session on another paired computer (Run on), with Copilot's own models and modes, in a worktree or on a branch there. A session open in Copilot CLI in a terminal shows as working there, and Seshboard waits until it is closed before continuing it. Fork, Edit and resend, Rewind, Rename and Delete work for Copilot sessions too, through Copilot's own tools: Rewind takes the conversation back to before your message with the files Copilot changed, and puts the message back in the box; Rename shows in Copilot CLI too; Delete moves the session to the Trash, and archived Copilot sessions are cleaned up like Claude Code's. A Copilot model that takes an effort level gets the effort chip, and its background commands and agents show in the background tasks pill, with Stop. Add to queue, Schedule… and Start when… work with a Copilot profile too: the queued item, the scheduled run or the triggered session starts Copilot with its model, effort and mode. A Copilot session can start in a new worktree or on another branch too, from New session, the queue, a schedule or a trigger, as a Claude Code session does, with the project's setup actions before its first message. A pipeline step can run with Copilot too (Runs with in the step, once you have a Copilot profile), with Copilot's models and modes; a read-only step only reads, and a step forks only a step of the same tool. Linking sessions with @ works in a Copilot session too: the linked session's brief (and an attached issue) goes with your message, as it does for Claude. Files and lines you add from the VS Code companion, by drag and drop or with @ reach Copilot as attachments, so it reads them as Claude does. Copilot's subagents show what they did, under their card and in Agents (in the ⋯ menu), as Claude's do. Ask about this session works in a Copilot session too, on the computer and on your phone: a throwaway copy of the session answers with tools that only read, nothing reaches the conversation, and the answer costs a premium request or so. A Copilot slash command that answers in words stays in the conversation after a restart, where you ran it. Usage shows a Copilot profile's prem...

v1.3.0-beta.17

Added

• Home uses the whole window: a start box, lanes for what needs you, what's working and what to review, then your projects and usage. Type a project's name and what Claude should do, then press Return to open New session with both filled in, or press ⌘1 to ⌘9 to pick a project. A To review card opens its session with the catch-up. Profiles without sessions today fold into one line each.
• To review and Open. The sidebar now says what is still yours instead of grouping by day: To review has the finished sessions you haven't read, Open the ones you read but haven't marked done, newest first. Today, Yesterday and Earlier are gone; each row still shows its age. A session with an unsent message or a queued prompt stays listed however old it is, here, in VS Code and on your phone, so it never slips into Done. On your phone the list has the same sections.
• Go through your sessions one by one. The sidebar footer counts what is open ("7 open"). Click it to open the first session to review with its catch-up. Skip (S) goes on to the next one, To review first, then Open, and leaves the one you skipped as it was. Done (E) goes on to the same next one. The catch-up says where you are ("2 of 7"), and when there is nothing left you're back Home.
• Archive is now Done. What you finished, and what went quiet, sits in Done under the list. Each row says why: "Done" when you marked it, or "Inactive 3 days" when it went quiet, and those are dimmed so they don't look finished by you. Mark a session done with the checkmark on its row, E, a middle-click, its menu or its catch-up; Reopen brings it back. Settings › Sessions, Manage sessions, the command palette and your phone say Done too. The keys didn't change.
• A note on what's left. Give a session one line, such as "push after review" or "waiting on Jan": press N on its row or in its catch-up, or pick Note… in its menu or the command palette. It shows under the title in the sidebar (in the tooltip with the compact style), and search finds it. A catch-up that needs something from you offers Use as note to put that there in one click. Done keeps the note but doesn't show it.
• Loose ends. A session that left something behind has a small marker on its row: files not committed, commits not pushed, a pull request with failing checks, or one closed without merging (and a queued prompt). Hover it to see what. Such a session never goes to Done by itself after the days you set. Marking it done yourself still works, and the toast says what's left ("3 files not committed"). Seshboard looks when a turn ends, when you come back to the window, and every few minutes.
• A merged pull request moves its session to Done. When the pull request of a session merges, the session goes to Done and its row says "Merged #123". You get one toast for them the next time you're in Seshboard, with Undo. A session that is pinned, working, waiting for you, open in Seshboard, active since the merge or with loose ends left stays where it is, and one you reopen stays open. Turn it off in Settings › Sessions › Move to Done when its pull request merges.
• Remind me later. Press L on a session (or several), in its catch-up, its menu or the command palette, and pick In 1 hour, This evening, Tomorrow, Monday or a time of your own, with an optional note. The session leaves the list until then, then comes back under Reminders, above To review, with a notification ("Reminder: …"), and stays there until you open it. One that came due while Seshboard was closed says when it was for. If Claude needs you, fails or starts working in it, it comes back at once. Upcoming has a Reminders filter, with Edit, Remind now and Cancel, and its sidebar row counts them. Settings › Notifications can turn reminder notifications off, or count them in the app icon's badge. In catch-up, L goes on to the next session, as Skip does.
• Quick start from anywhere. Press ⌃⌥Space in any app to start a session: pick a project, type the task, and it runs in the background without bringing Seshboard forward. ⌘↩ starts it and opens Seshboard, and ⌘K has more: start in a new worktree, change the model, mode or profile, attach the clipboard, or add it to Later instead. What needs you is listed on top, and Esc keeps what you typed for five minutes. On Windows and Linux the shortcut is Ctrl+Alt+Space. Change it, or turn off starting in the background, in Settings › General › Quick start.
• Defaults for GitHub Copilot sessions. A Copilot profile now has New session defaults in Settings › Profiles, as Claude profiles do: its model and effort (from Copilot's own models), its permission mode and its workspace (current folder or a new worktree). A project on a Copilot profile sets the same in its Settings. New session starts Copilot sessions with them. The global model and effort in Settings › General are Claude's, so Copilot sessions without a model start on Copilot's default; the global permission mode applies to both.
• Copilot CLI updates, like Claude Code's. With a GitHub Copilot profile, Settings › About shows GitHub Copilot CLI too: the version you have, whether a newer one is out, and Update. A toast says when a new version is available, as it does for Claude Code. Seshboard uses the new version the next time it opens.
• Seshboard lives in the menu bar too. It lights up while sessions work, shows what needs you with Allow right there, and starts new work in the background. Right-click it for Open Seshboard, New session…, Pause notifications and Quit. On Windows it's in the notification area; on Linux it's a menu. Settings › General › Menu bar turns it off, keeps Seshboard running when you close the window, and (on a Mac) hides the Dock icon while no window is open.
• Getting started with GitHub Copilot. When Seshboard finds Copilot CLI, Profiles offers to add it. Adding a Copilot profile skips sign-in when you're already signed in, and ends with ways to start using it. New session says what it turned off when you switch to Copilot.
• GitHub Copilot sessions. Add a GitHub Copilot profile in Settings › Profiles (now Profiles, with Claude Code and Copilot ones) and pick it in New session, or link a project to it, to start a Copilot session in Seshboard, with Copilot's models (and Copilot Fusion: its tiers, such as Fusion Standard and Fusion Max, are in the model menu after Auto, with a recent Copilot CLI), its permission prompts as cards, and its replies as they stream. Copilot runs with your own Copilot CLI and the profile's login: Seshboard never asks for a token, and the profile's Sign in runs Copilot's own sign in. Two Copilot accounts can be two profiles, as with Claude. Sessions you started in Copilot CLI or in VS Code show up too when Show sessions from other apps is on (Settings › Sidebar), and you can continue them here. Each session's row and header show whose it is with the Claude or Copilot mark, the profile chip under the message box shows the mark in the profile's colour, and a working session says who is working ("GitHub Copilot is working"). The permission modes are the same as Claude's (Ask before edits, Accept edits, Plan mode and Auto mode): in Auto mode, Copilot runs as its autopilot and doesn't ask before commands, and switching to it allows the requests already waiting. Its slash commands are there too, in the message box, and so are its MCP servers, agents and skills in Tools, Compact, Up next, Send now and steering while it works, and its context and premium requests under the message box. On your phone, New session can start a Copilot session too (pick the Copilot profile in Options), and so can New session on another paired computer (Run on), with Copilot's own models and modes, in a worktree or on a branch there. A session open in Copilot CLI in a terminal shows as working there, and Seshboard waits until it is closed before continuing it. Fork, Edit and resend, Rewind, Rename and Delete work for Copilot sessions too, through Copilot's own tools: Rewind takes the conversation back to before your message with the files Copilot changed, and puts the message back in the box; Rename shows in Copilot CLI too; Delete moves the session to the Trash, and archived Copilot sessions are cleaned up like Claude Code's. A Copilot model that takes an effort level gets the effort chip, and its background commands and agents show in the background tasks pill, with Stop. Add to queue, Schedule… and Start when… work with a Copilot profile too: the queued item, the scheduled run or the triggered session starts Copilot with its model, effort and mode. A Copilot session can start in a new worktree or on another branch too, from New session, the queue, a schedule or a trigger, as a Claude Code session does, with the project's setup actions before its first message. A pipeline step can run with Copilot too (Runs with in the step, once you have a Copilot profile), with Copilot's models and modes; a read-only step only reads, and a step forks only a step of the same tool. Linking sessions with @ works in a Copilot session too: the linked session's brief (and an attached issue) goes with your message, as it does for Claude. Files and lines you add from the VS Code companion, by drag and drop or with @ reach Copilot as attachments, so it reads them as Claude does. Copilot's subagents show what they did, under their card and in Agents (in the ⋯ menu), as Claude's do. Ask about this session works in a Copilot session too, on the computer and on your phone: a throwaway copy of the session answers with tools that only read, nothing reaches the conversation, and the answer costs a premium request or so. A Copilot slash command that answers in words stays in the conversation after a restart, where you ran it. Usage shows a Copilot profile's prem...