What shipped in the desktop app, newest first. Each release keeps a permanent page of its own, and the feed carries the whole note rather than a teaser.
The Agent panel now keeps its session list in an overlay drawer. Open the drawer when you want to switch conversations, then close it to give the active session the full width of the panel. The redesigned list is easier to scan, and the session close action is clearer while staying out of the way during normal work.
Keyboard shortcuts are now customizable. Open Settings and use the new Keyboard Shortcuts section to change the keys for search, workspace actions, the file tree, Diff, task navigation, comments, and terminal clipboard actions. Pekan prevents conflicting combinations in the same context, shows which bindings are custom, and lets you reset one shortcut or restore every default. The shortcut reference in Help updates immediately to match your choices.
Live agent sessions can now be opened in a tab in the main workspace, right next to Files and Diff, instead of living only inside their agent panel. Use the new Open in workspace action on any running session to pop it out; opening the same session again just refocuses its existing tab instead of creating a duplicate, and you can keep as many session tabs open at once as you want. The workspace tab and the agent panel show the exact same live session: new messages, streaming output, approval prompts, and status changes appear in both at the same time. Closing a workspace tab only closes that view, the session itself keeps running in its agent panel exactly as before.
Pekan for macOS is now signed with an Apple Developer ID and notarized by Apple. Downloading the .dmg or .zip and opening Pekan works the normal way now: unzip or mount, drag Pekan into Applications, and launch it.
The Tags and All milestones filters in the Tasks toolbar can now create a new tag or milestone directly, instead of sending you somewhere else to do it. Pick a name, and for tags a color, then the new one becomes the active filter right away, so it's obvious there's nothing in it yet until you tag or link a task to it.
Boards now scale to much larger projects without slowing down. A column that has grown past a couple dozen cards no longer renders every one of them at once: it shows the first batch with a Show more button to reveal the rest, so opening a busy board stays fast. This doesn't affect drag-and-drop or the totals shown in column headers, which still reflect every task, not just what's currently mounted.
Review now covers security risk alongside correctness, quality, and regressions, so the separate Security pass action has been retired. Launching Review checks authentication and authorization boundaries, input validation, secret and credential handling, sensitive data exposure, unsafe command or file access, dependency risk, and misuse of trust or permission boundaries, in addition to everything it already looked at. Findings still land as a task comment with the same severity and evidence you're used to, and stay proportional to the change rather than forcing security commentary onto every task. A saved reference to the old Security pass action fails gracefully instead of breaking.
The public alpha keeps Pekan focused on the parts of the product that are ready to use today. Roadmap planning, Telemetry usage insights, and the broader Intake experience are not yet available in this build, so you won't run into unfinished menu items, search results, links, or documentation pages for them. This gives the team room to keep improving Roadmap planning, make usage insights trustworthy, and rethink Triage as a broader Intake experience before bringing them to everyone.
Ask Pekan can now use your selected local ACP provider as a reasoning layer when the built-in voice router cannot understand a request on its own. This makes the assistant useful beyond task lookup: it can resolve projects and destinations, open the main Pekan pages and project panels, prepare a new terminal, insert a terminal command for review without executing it, or propose starting a visible agent session with workspace access. Potentially destructive actions still stop for explicit confirmation, while unambiguous navigation remains immediate. Settings now lets you choose an installed ACP provider and one of the models that provider actually advertises. Model discovery survives an app restart by restoring the hidden assistant session long enough to load its current configuration.
The global voice control is now a single Ask Pekan entry point instead of a set of modes you had to understand before speaking. Pekan infers whether a request should navigate, search, dictate, or propose a board change from the words themselves. You can ask it to open Settings, Help, Activity, Workflows, Agent Actions, a project view, or a task by its display ID, and you can search tasks without first choosing the right mode. Navigation happens immediately when the destination is unambiguous. If a project or task name could mean more than one thing, Pekan presents a short choice instead of guessing. Board changes remain reviewable before they are applied, and the microphone control now uses clear start and stop states rather than requiring a press-and-hold gesture.
The collapsed Project rail, the vertical strip on the right edge of the Workspace page when the Files/Diff panel is closed, already showed how many files had changed in a linked directory. It now also shows the current Git branch just below that count, so the active branch is visible without reopening the panel. The label sits vertically like the rest of the rail, is truncated so it never widens the fixed-width rail, and carries the full branch name in a tooltip and accessible label for both mouse hover and keyboard focus. Screen readers announce it clearly as the current branch alongside the existing changed-file count.
Resuming an Agent panel session after closing it could leave a stale Action needed permission card on screen even though Auto approve was active and the command had already run, and clicking Deny, Allow once, or Always allow did nothing. The cause was a permission request id that could be reused across a reconnect, which let a later resolution update the wrong, already-settled card instead of the live one. Permission and elicitation request ids are now unique per request rather than per connection, so a resumed session's approvals resolve correctly and the on-screen state always matches what actually happened. The Sessions sidebar's collapse toggle also moved to the right edge of its header, matching every other collapsible panel in the app instead of sitting to the left of the label.
The Pekan documentation now has a dedicated Agent Panel guide for anyone starting or steering a conversational coding session. It walks through installing the Codex ACP or Claude Agent ACP adapter, opening a project-scoped session, choosing read-only or write access, and deciding between reviewing each request and automatic approval. A compact comparison explains when to use the Agent Panel, an Agent Action, or a Workspace terminal, so the differences in interaction, repeatability, and worktree behavior are clear before work begins.
The board's green "working" badge previously only lit up for tasks driven by an Agent Action. A task actively being worked from an Agent panel session, or from a terminal session launched against it, showed no live indicator at all, even while the session or process was genuinely running. This release extends the same live presence signal Agent Actions already publish to both of those surfaces, so the badge and its accompanying identity pill now reflect real work happening anywhere in Pekan, not just one launch path.
The Agent panel composer now offers a microphone control for dictating a message before sending it, reusing the same recording and transcription pipeline that already powers Triage capture rather than building a second one. When the voice add-on is enabled in Settings, a mic button appears beside the attachment control. Clicking it starts recording, visibly indicated on the button itself; clicking again stops the recording and sends it for transcription, while a separate cancel control discards the recording outright without transcribing anything.
Pekan now reads the slash commands a connected ACP provider advertises instead of discarding them. Typing / at the start of the Agent composer opens an accessible, keyboard-navigable picker listing every command the active Codex ACP or Claude ACP session currently offers, along with its description and, where relevant, a hint for the text it expects. Selecting a command inserts it into the composer, adding a trailing space only when the command takes further input, so a command like /compact is left ready to send and one that expects an argument is left ready to type. Typing and sending plain text still works exactly as before: the picker is a shortcut, not a requirement.
You can now line up the next instructions while an Agent session is still working. Sending during an active turn adds the message to a visible first-in, first-out queue instead of interrupting the agent or making you wait at the composer. Each waiting row shows its place in line, keeps its task context and attachments, and can be edited or removed until dispatch begins. The Stop control remains available beside the new queue action, so preparing later work never takes away control of the turn already running.
The Agent and Files/Diff panels can now be toggled without reaching for the mouse. Ctrl+Shift+A (Cmd+Shift+A on macOS) shows or hides the Agent panel, and Ctrl+Shift+E (Cmd+Shift+E) does the same for the Files/Diff panel beside it. Both are app-scoped: they only act while Pekan is focused, and neither registers as a system-wide shortcut, so they never compete with anything else running on the desktop.
The Agent panel now carries its own session list. It is a slim column at the left edge of the panel, about half the visual weight of the Project and Agent sidebars around it, and it lists only the sessions belonging to the project you are in. It is there on the new-session screen and it stays there inside an open conversation, so returning to yesterday's session no longer means pressing the plus button and hoping. The plus button now means exactly what it looks like: start something new.
Agent actions used to force a choice before you opened anything. Running an action from a task menu started a background run, and watching an agent work meant reaching for a separate Terminal command that knew nothing about the action you had in mind. The Agent Action dialog now carries a Launch in terminal checkbox, unchecked by default, so the decision sits next to the provider, the additional instructions and the isolated-worktree option you were already setting.