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 Agents tab on Activity now uses persisted run history as its foundation. That means work started directly from Codex, Claude Code, Mistral Vibe or OpenCode appears alongside runs launched inside Pekan, and the history survives an app restart. The completed-run count in Since your last visit now opens the records behind that count instead of leading to an empty tab when Pekan did not own the original process.
Full noteCo-authored by AI · Human-reviewed and published by Pekan
Approval handling used to be decided once, when a session started, and that was that. If you began a conversation on automatic approval and then reached the part where the agent starts changing files, tightening up meant throwing away the session and the transcript with it. The session header now carries a small Approval mode control with two options, Ask each time and Auto approve, showing which one is live and letting you switch at any point.
Full noteCo-authored by AI · Human-reviewed and published by Pekan
A long agent session used to give a finished file read exactly as much room on screen as the answer you were waiting for. Tool calls now earn their space. A call that is still pending or running stays open, because that is the live work. A call that failed stays open too, since an error is the one thing nobody should have to click to find. A call that simply succeeded folds into a single row showing its status, what it did, a short result summary, and the time, so scrolling back through a long turn is reading a list rather than wading through output.
Full noteCo-authored by AI · Human-reviewed and published by Pekan
List view used to open sorted by task ID, oldest first. On a project with a few hundred tasks that meant the top of the list was whatever you created first, which is almost never what you want to look at. It now opens sorted by a new Latest activity column, most recent first, so the work that is actually moving is the work you see.
Full noteCo-authored by AI · Human-reviewed and published by Pekan
Pekan now has an Agent panel: a real conversation with a coding agent, running on your machine, docked on the right of the project workspace. Ask a question, watch the answer arrive word by word, see the plan it is following, approve or refuse the tools it wants to use, and read the changes it proposes as diffs you can open in the Files panel beside it. The panel sits next to the existing Files and Diff panel rather than replacing it, so you can keep a file open while the conversation continues. Both panels open, close and resize on their own, and each remembers its own width between sessions.
Full noteCo-authored by AI · Human-reviewed and published by Pekan
Agent activity, and every panel that slides in from the right edge of the window, now carries a proper Close button in its own header. Until now the Agent activity drawer was pinned to the very top of the window, which put its small close icon directly underneath the Windows minimize, maximize and close buttons. Those buttons are drawn by the operating system on top of the app, so the panel's own control was both hard to see and impossible to click: aiming for it hit the button that quits Pekan instead. The only reliable way out was the Escape key, which is not something a panel should require you to know.
Full noteCo-authored by AI · Human-reviewed and published by Pekan
Pekan now ships with its first active end-user licence agreement and publishes matching legal pages for the website. The exact approved EULA text is stored as a versioned source, bundled into the desktop app, included beside portable builds, and shown by the Windows installer. Privacy, website terms, licence details, and the EULA are linked from the website footer and from Help in the app. These pages are ready for direct access but intentionally remain excluded from search indexing while the surrounding website design and content are still being prepared for launch.
Full noteCo-authored by AI · Human-reviewed and published by Pekan
Actions that are authorized to change files can now do so when they run against your own project checkout. Until now the permission profile handed to the agent was decided by whether the run used an isolated worktree, not by whether the action was allowed to make changes. Turning isolation off therefore produced a run that had been confirmed as a mutating action but was given a read-only profile, so every attempt to write a file was refused, and because these runs have no terminal for anyone to answer a prompt at, the agent discovered this only after working through the whole task. It reported that it was blocked and left nothing behind.
Full noteCo-authored by AI · Human-reviewed and published by Pekan
Pekan now has a proper mechanism for putting legal documents in front of you and recording what you answered. It handles three genuinely different things, and keeps them apart. An agreement, such as a licence, is something you accept before using the app. A notice, such as a revised privacy policy, is something you are told about without being asked to agree; it appears as a banner you can dismiss, and Pekan keeps working the whole time. An optional permission is off unless you switch it on, never bundled into an agreement, and switched back off by the same single control that turned it on.
Full noteCo-authored by AI · Human-reviewed and published by Pekan
Stage all files now asks Git to stage the repository as a whole instead of turning every visible status row into an explicit path. This matters for projects where Pekan's managed .mcpekan directory is ignored but still contains a tracked file such as AGENTS.md. Git can update that tracked file normally while leaving ignored runtime files alone, so one ignored directory no longer prevents unrelated modifications, deletions, renames, and new files from reaching the index.
Full noteCo-authored by AI · Human-reviewed and published by Pekan
The Capture local AI usage option now explains exactly what saving it will do. When capture is enabled, Pekan stores provider-reported token aggregates and active working time, then updates its managed agent instructions and supported provider hooks. Prompt and response content is never captured. When capture is disabled, the explanation changes immediately so it is clear that saving removes Pekan's managed telemetry instructions and hooks while retaining telemetry records already stored in the project.
Full noteCo-authored by AI · Human-reviewed and published by Pekan
Until now, telemetry for an ordinary terminal session depended entirely on a provider lifecycle hook firing at the end. That works when the provider decides a session is over promptly. It works badly when it does not: a Codex thread can sit open for half an hour after the useful work stopped, and a killed process never fires its hook at all. The result was runs that arrived late, or never, and no honest measure of how long an agent actually worked.
Full noteCo-authored by AI · Human-reviewed and published by Pekan
The SHA256SUMS.txt published with each release was written with Windows line endings, which the standard sha256sum tool cannot read: it treats the invisible carriage return as part of the filename, looks for a file that does not exist, and reports that no file was verified. If you verify downloads from WSL, Git Bash, or a Mac, that is what you would have seen.
Full noteCo-authored by AI · Human-reviewed and published by Pekan
The 0.183.0 release shipped a checksums file that named the installer with spaces, as Pekan Setup 0.183.0.exe. GitHub rewrites spaces in a downloaded file's name to dots, so what you actually got was Pekan.Setup.0.183.0.exe. The checksum itself was correct, but the verification command in the release notes pointed at a filename that did not exist on your disk, so following the instructions gave you a file-not-found error rather than a matching hash.
Full noteCo-authored by AI · Human-reviewed and published by Pekan
Pekan Desktop is in a private alpha for invited testers, and it is distributed as a direct download rather than through an app store. Alongside the Windows installer there is now a portable ZIP, so you can unpack the app to a folder and run it without an installer at all. Every release publishes SHA-256 checksums for both files, and you can verify what you downloaded before you run it with a single Get-FileHash command, which the release notes spell out.
Full noteCo-authored by AI · Human-reviewed and published by Pekan
Every place in Pekan where an AI agent generates content now says so, names the provider, and gives you a plain-language line about what that run can see, right in the launch dialog, before you confirm, not buried behind a details toggle you have to know to open. Breaking a task down, drafting a project plan and refining a Triage capture all show the same disclosure, and the review screens for those proposals now carry a clear AI-generated marker while you edit them, matching what task cards and comments already showed.
Full noteCo-authored by AI · Human-reviewed and published by Pekan
Pekan Desktop now draws a hard line between the app window and the rest of the web. The window loads one thing, the board it serves on your own machine, and it will not navigate anywhere else. Links that used to open in a second app window, a link in a task description, a pull request, an attachment you asked to see in a new tab, now open in your normal browser instead, where they belong. Nothing you click disappears, it just arrives in the right place, with your bookmarks, your extensions and your session already there.
Full noteCo-authored by AI · Human-reviewed and published by Pekan
Pekan Desktop now builds as a Microsoft Store package alongside the existing direct download. The Store edition is free, unlimited and entirely local: it keeps your board, your projects and your agent runs on your own machine, and it never asks you to create an account. Microsoft signs, hosts and updates it, so installing and staying current takes no more thought than any other Store app.
Full noteCo-authored by AI · Human-reviewed and published by Pekan
Triage refinement now treats an explicit attachment read failure as stronger evidence than an agent's later claim that it analyzed the file. During the final installed-provider image validation, Codex reported that its Windows sandbox helper could not open the supplied icon, but still returned a plausible proposal naming the icon in analyzedFiles. The proposal looked convincing because it inferred likely visual details, even though the provider log proved that the image tool had failed.
Full noteCo-authored by AI · Human-reviewed and published by Pekan
Automatic agent usage capture no longer depends on the folder where a session happens to finish. Claude Code, Codex, and Mistral Vibe can now end at the project root, inside a nested app or package, or in an isolated worktree created by Pekan, and the same project recorder is resolved safely. This fixes missing telemetry and module-not-found diagnostics after an agent changes directories during its work.
Full noteCo-authored by AI · Human-reviewed and published by Pekan