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 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 premium requests (what is left this month, and when they reset) in place of Claude's plan limits, and so do its card on Home and a Copilot session's footer: a ring that fills as they are used, with the details on hover and Usage a click away. Plan usage stays Claude Code's. Copilot stays hidden until you add a Copilot profile. On Windows, Copilot CLI installed with npm is found too. (#199)
• Another computer's sessions work like your own. In a session from another computer:
  • Quote text you select, or right-click a message to quote it. The quote goes into that session's message box.
  • Read under a finished reply opens reading mode, with Reply with quote and Ask about this. ⌘⌥R (Ctrl+Alt+R on Windows and Linux) reads the last reply.
  • The catch-up shows over the conversation.
  • Changes lists what isn't committed there, with each file's diff, and Commit commits it there. It doesn't push.
  • Ask about this session asks Claude on that computer.
  • Click a step to see its diff or what it ran, and its output.
  • Find in the conversation with ⌘F, and Jump to latest when you scroll up.
  • Mark as read, Mark as unread and Copy last reply are in the ⋯ menu.
  • Run a pipeline is in the ⋯ menu. A run's steps sit under the session in the sidebar, and its card has Continue, Run this step again, Skip, Stop and Push.
  • New session there has Queue for later.
  • You get notifications when one of its sessions needs you or finishes. A click opens the session.
• Quote in the remote app. On your phone, Quote under a reply puts it in the message box as a quote. Select text in the conversation or in Read, and tap the Quote pill under it to quote only that.
• See in the Dock when Claude is working (macOS). While a session works, the empty jacks in Seshboard's Dock icon light up one after another and a pulse of light runs along the cables, in whichever app icon you picked. With Reduce motion on, the jacks stay lit instead. Turn it off in Settings › Theme › App icon › Show when Claude is working.
• Keep awake until done. Turn it on for a session in its ⋯ menu, or with Keep awake until done in the command palette, and the computer doesn't sleep until the session is done: its turn, its background tasks (shell commands, subagents and workflows) and what waits in Up next. It turns off by itself then. Unlike the Keep awake setting, it also works on battery on a Mac. A pill above the message box shows it is on; click it to stop. (#241)
• Pick the session from VS Code, or start a new one. The VS Code companion now asks where to add a selection or a file instead of adding it to the session you have open: that session is first, so Enter still adds to it, then New session and the workspace's other sessions. Seshboard: New Session in VS Code opens New session on the workspace folder, and Add File to Seshboard in the editor's right-click menu adds the file you have open. To add straight to the open session as before, turn on seshboard.addToOpenSession in VS Code.
• Pick the model and effort new sessions start with. Settings › General › New sessions now has Global model and Global effort, next to Global permission mode. They apply where a session's project and Claude profile set none, also to sessions started from a link or your phone, and a project's or profile's Global default names them. As with the permission mode, a project follows its profile's model and effort, or you pick Global default to skip the profile's. Leave them on Claude Code's default to keep what Claude Code picks.
• Remote keeps a log, and says when it turns a device away. Remote now writes who connected, who it refused and why (for example a device you revoked that still tries), and when it makes an address wait, to remote.log. Open it from Settings › Remote › Advanced. When an address waits after refused attempts, the status card says so, and Unblock lets everyone on it in again without restarting Seshboard.
• Name and colour your other computers. In Settings › Remote › Other computers, Rename gives a paired computer a name of its own here (clear it to go back to the name it gives itself), and Colour picks its colour. Its chips in the sidebar and the Computers strip, the badge on its projects and the line over its sessions use that colour, so two computers no longer look the same. Only this computer sees them; the other one keeps its own name.
• A page for each of your other computers. Open on a paired computer in Settings › Remote › Other computers shows what is going on there: what needs you, with the longest wait to answer right on the page, what is working, and its recent sessions by project. Mine and All on the page switch the same filter as its chip in the sidebar. The line under its name says which Seshboard version it runs. When it is offline, the page shows the last list it sent, dimmed.
• Choose the notifications of each computer. In Settings › Remote › Other computers, the bell on a paired computer's row picks which of its notifications show here: All (needs you, finished and failed), Only mine (all of them, but only for sessions you started there or acted on from this computer), Needs you (only when a session waits for you) or Off. Its sessions still show in the sidebar. When it isn't All, the bell says which.
• On a shared computer, its chip in the sidebar switches between your sessions and everyone's. Settings › Remote now only sets which notifications it sends. Right-click a paired computer's chip in the Computers strip, or click the ▾ that shows on hover, to pick Mine or All, kept for each computer. While Mine is on, a person shows after the computer's name. Mine shows the sessions you started there from this computer, and the ones you sent a message to, answered or resumed from here. The chip's menu says how many it hides, and a search still finds them. In All, other people's sessions say who started them, after the branch. Only mine notifications use the same sessions. The strip stays on one line: every chip has the same quiet background with the name in the computer's colour, and the chips that don't fit fold into +N.
• Run another computer's pipelines from here. In New session with Run on set to a paired computer, Run as lists the pipelines that computer has for the project. Pick one and Run pipeline starts it there, with your prompt as its task, and opens its run here. A run started from New session on another computer is in the sidebar too, with its steps under it: open it to follow the steps, Continue, Push or Stop, or write in it to give the run a session of its own. Done on a run, or on the session a run started from, takes its steps with it. Your phone could already do this.
• See what a trigger started, from anywhere. A session or a pipeline run that a trigger started now has its bolt on another computer and on your phone too, and says which trigger started it under its header ("Started by CI fails on main · CI #4512"), with a link to the CI run or the issue. A run that goes on without stopping for you says so there too.
• Your answers stay in the conversation. When Claude asks you a question, the question and what you answered now stay in the conversation after you answer, with the options you picked marked and anything you typed yourself. Before, it folded into a line that said "Asked you a question".
• Update another computer from here. Settings › Remote shows each computer's version, and updates an older one from here, right away or once its sessions are idle. Each row now has the notifications choice, Open and ⋯ (Rename, Colour, Check for updates, Update to…, Copy its address, Reconnect and Remove), with Update when that computer is behind. It shows up even before that computer has seen the new version, as long as this Mac knows about it. Whoever is on the other computer gets a notification that says who started the update.

Changed

• The old addresses stop working. The remote app only connects from seshboard.app now, so a phone still paired on switchboard.struyfconsulting.com has to pair again. VS Code companions up to 0.2.0 no longer find Seshboard: update the extension.
• Sessions look calmer: panels are set apart by their background instead of lines, and headers only show a line while something scrolls under them.
• No Mark as read in the catch-up. The catch-up no longer has a Mark as read button or the U key: a session you look at is marked read after a few seconds by itself (Settings › Sessions › Mark as read after).
• The sidebar footer's count of running Claude Code processes says "2 running" instead of "2 open", now that "open" counts the sessions you haven't finished.
• Sessions on another computer have the new message box. A session there and New session there now look and work like they do here: the box, with the profile, model, effort and mode chips on the tray under it (and the session's cost on the right), folding the same way in a narrow pane. New session there has the route strip on top, with Where, the branch and the Worktree switch.
• The message box is bigger, with the model, effort, mode and profile on a tray under it, together with context and usage.
• The working line under a reply shows the patch panel from the app icon, its free jacks lighting up in turn, like the Dock. It takes the colours of your theme: its light is the theme's accent, and the themes named after an app icon have that icon's cables.
• Claude Code sessions started by Seshboard use the seshboard entrypoint label instead of inheriting their launcher's label.
• Show or hide a pipeline's steps from its quick actions. Hover a pipeline's row, on this computer or another one, and the first button opens or closes its steps, so the arrow no longer moves away under the pointer.

Fixed

• The / menu stays open when you type right after clicking away. It could close by itself a moment after it opened, and Return then sent what you typed as a message.
• Terminals open when you start Seshboard from a Store PowerShell. On Windows, they failed with "Cannot create process, error code: 5".
• With Reduce motion on, things no longer show in the wrong place for a moment. The selection toolbar could appear in the corner of the window first, and its buttons could miss a click right after it showed.
• Code blocks in another computer's sessions work like your own. They are the same size, with syntax colours, a copy button and Preview | Source for Markdown. Run stays on that computer.
• Seshboard installs on Windows on Arm. On an Arm PC the installer finished without putting Seshboard.exe in place, so its shortcuts showed "Missing Shortcut".
• A session opens at the end with Reduce motion on. With Reduce motion turned on in your system settings, a conversation could stop a little short of its last lines when you opened it.
• The terminal stays in the window. With the catch-up open or in a narrow split pane, the terminal under a session could run past the bottom of the window and hide its last lines. It now gets shorter to fit.
• A pipeline waits for a step's background work. When Claude ended a step's turn with a command or an agent still running in the background, the next step (or Push) started while Claude was still working in the folder. The run now goes on once that work is done.
• Push shows what it would push now. Its commit message, files and branch were written once and kept, even after a step committed, switched branch or changed files, so it could show "0 files" next to six changed ones. They are written again when the folder changed. When Push fails, the run says why, here and on another computer. With nothing to commit, Push sends the branch's commits and opens the pull request without a message.
• Dropdowns show long names in full. A dropdown's list, such as the pipeline picker in a trigger, was a fixed width and cut long names off. It now widens to fit them.
• GitHub Copilot's answers in Auto mode show as its reply. In Auto mode, Copilot often ends a turn with its answer in a "task complete" step instead of a message, and Seshboard showed that step as a tool card with its raw input. The answer now shows as Copilot's reply.
• Project actions show up in GitHub Copilot sessions. A Copilot session that was new, or whose file doesn't name its folder, had no actions above the message box and none in the ⋯ menu. It now takes its project from the folder Copilot runs in.
• Long GitHub Copilot sessions can be pinned, archived and renamed again. A Copilot session whose history starts partway through (after autopilot kept it going) showed as "New session", with Rename, Pin, Archive and Delete greyed out. It now shows with your last prompt as its title, in its project, with every action.
• A long session title no longer makes New session scroll sideways. In Pick up in, a title too long for the row is now cut off with an ellipsis instead of widening the view.
• Terminal text no longer spreads its letters out. In a terminal drawn without WebGL, rows drawn while the terminal was hidden could keep an extra space after every letter ("r e a d y i n 8 5 4 m s"). The terminal now notices and draws them again with normal spacing.
• A computer with an old pairing no longer locks your phone out. A Seshboard on another computer that was paired before this Mac's Remote key changed (the move to Seshboard made a new one) kept trying every minute, and after a few tries Remote turned away everything on that network, your phone too. It is now told to pair again and stops, and paired devices always get in, even while Remote turns a network away. Pairing a new device from that network still waits, or use Unblock. Pairing a computer again in Settings › Other computers now replaces its old entry instead of adding a second one.
• Keep awake keeps Seshboard itself awake on a Mac. With the display off, macOS could still slow Seshboard down while Keep awake held sleep off, which can drop phones connected through Remote. Keep awake now keeps Seshboard out of App Nap too.
• No more ghost agents. An agent that Claude tried to send a message to after it finished, and that could not be woken up again (for example because its worktree was removed), no longer stays under Active in the Agents panel.
• Large app icons work as project icons. A PNG over 200 KB, such as a 1024-pixel app icon, is now scaled down instead of turned away, both when you pick it with Choose image… and when Seshboard finds it in the folder. It also finds Resources/AppIcon.png, where Swift and Xcode projects keep theirs. An image that can't be used now says why instead of doing nothing.
• Quote over selected text works again. Clicking Quote (or Remember this…, or Reply with quote in reading mode) on the toolbar over a selection closed the toolbar and did nothing. It now puts the selection in the message box.
• A branch name can't run a command in a project action. A ${branch} (or another value) written inside single quotes in an action now stays text, whatever the name holds.
• Revoke cuts a phone off at once. A phone revoked while it was still connecting can no longer get one last request through.
• Ask about this session only reads. Claude could get git to write a file from an Ask by putting the option in quotes. That is refused now, like any other change.
• Importing a memory named "memory" no longer hangs. A memory whose name became memory (a # Memory heading, or one in another script) made the import never finish and the app stop responding. It is saved as memory-2.md now.
• Allow shows what it approves. On the phone, a permission prompt shows the whole command, every line of it, instead of only the first. A prompt that doesn't fit the one line of a card on Home, or of a notification, opens its session to be answered there. A request too long to show in full says so on the computer and on the phone.
• A cloned repository asks before its first session, however you start it. The question about the hooks and MCP servers a cloned repository brings came only from Start in the clone form. Now nothing of Claude Code runs in the repository until it is answered, also when you start from the palette or another window.
• A repository can't freeze Seshboard with a linked file. Its .seshboard.json, package.json or Claude Code settings are read only when they are small, ordinary files. Saving shared settings never copies a file from elsewhere into the repository.
• On Windows, a repository's own git.exe or gh.exe never runs. Seshboard now always starts the git and GitHub CLI installed on your PATH.
• On Windows, a network path in a reply or an HTML preview no longer sends your login. Seshboard only looks at files on this computer's drives, so a \\server\share path can't make it connect to another computer.
• A large HTML file previews at once. A page with many unclosed tags no longer takes minutes to open, an image named many times counts toward the page's limit each time, and the preview's security policy always applies.
• Nested Markdown blocks no longer freeze the window. A Markdown block inside a Markdown block's preview shows as its source.
• Large rule files load at once. A rule or memory file whose frontmatter has a very long list no longer takes seconds to read.
• A mod draws only inside its own frame. A box a mod places freely stays in its band or pane, and never covers the line that names the mod.
• On Windows, seshboard with a folder name that has & in it no longer runs part of the name as a command when the folder doesn't exist.
• A pull request's base branch can't make git write a file. A base starting with - in a session's gh pr create is ignored when Seshboard lists the commits of a linked session.
• Approving a shared action approves what you saw. If the project's .seshboard.json changes while the approval dialog is open, nothing is approved and you're asked to check again. A shared prompt that becomes a shell command, or starts running in new worktrees, needs approval again too. Shared actions you approved before ask once more.
• Files that are links stay untouched. A MEMORY.md that is a link is no longer written through. Saving shared settings, and copying ignored files such as .env into a new worktree, never write through a link the repository holds.
• Undo after archiving on a phone works only on that phone. Another paired phone can't bring the session or run back.
• A phone stops getting a session's messages once it leaves its list, for example when the session is archived.
• Pairing a device is tied to its QR code. A phone that scanned an earlier code, or one shown before you closed the dialog, can't pair with the current one.
• On the phone, drafts and Ask answers stay with their computer. With more than one computer paired, a draft or an answer never shows on another computer's session.
• Installing the seshboard command on a Mac writes the commands directly with the administrator's password, instead of copying them from a temporary folder.
• Theme colours with long runs of spaces are refused at once, instead of slowing down a theme import.