<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>SuDuo changelog</title>
    <link>https://suduo.dev/changelog/</link>
    <description>What changed in each SuDuo release.</description>
    <language>en</language>
    <lastBuildDate>Wed, 07 Oct 2026 00:00:00 GMT</lastBuildDate>
    <atom:link href="https://suduo.dev/changelog/rss.xml" rel="self" type="application/rss+xml"/>
    <item>
      <title>SuDuo 0.10.0</title>
      <link>https://suduo.dev/changelog/#v0.10.0</link>
      <guid isPermaLink="true">https://suduo.dev/changelog/#v0.10.0</guid>
      <pubDate>Wed, 07 Oct 2026 00:00:00 GMT</pubDate>
      <description>&lt;p&gt;Adds requirement priorities and files in comments, makes attachments a plain list again, and keeps project folder links apart for each server.&lt;/p&gt;
&lt;h3 id=&quot;added&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Requirement priority: urgent, high, medium, low or none (the default). Set it when creating a requirement, on the requirement page, on a board card or in the list. Board columns and the list sort by priority by default (then by last update); you can switch back to last updated, and filter by priority. It needs a server on 0.10.0 or later.&lt;/li&gt;
&lt;li&gt;Files in comments: attach files or paste screenshots in the comment box. They’re uploaded when you send, belong to that comment, and can be saved as attachments of the requirement. A comment can be just files. It needs a server on 0.10.0 or later.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Attachments are one list again, newest first: the place for the final PRD, third-party material, screenshots and archives. When files overlap, the newer one wins. Publishing new confirmed versions has stopped; earlier confirmed versions stay readable under “Past confirmed versions”, and older clients can still publish to the server.&lt;/li&gt;
&lt;li&gt;The requirement tools Codex uses no longer publish confirmed versions; sessions that still call them get a reply saying the tool has been retired.&lt;/li&gt;
&lt;li&gt;Requirements accept the same file types as room files (archives, videos, logs and more), up to 100 attachments each.&lt;/li&gt;
&lt;li&gt;Project folder links are kept per server. Moving to another server no longer leaves your folders tied to the old server’s projects, and you can unlink a folder without reaching the server.&lt;/li&gt;
&lt;li&gt;One folder can be linked to several projects. When you choose a folder that other projects already use, SuDuo tells you which ones instead of refusing.&lt;/li&gt;
&lt;li&gt;Project sessions remember which project they belong to (local database migration 018), so sessions and requirement context follow the project even when projects share a folder.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;upgrading&quot;&gt;Upgrading&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Upgrade the server first, then each client. Settings → About shows a hint while the two versions differ; a 0.10.0 client hides priorities and files in comments until the server supports them.&lt;/li&gt;
&lt;li&gt;Cloud: &lt;code&gt;git fetch --tags &amp;amp;&amp;amp; git checkout v0.10.0&lt;/code&gt;, then &lt;code&gt;sudo ./scripts/suduo-cloud.sh upgrade&lt;/code&gt;. It backs up first; database migrations 014 (priority) and 015 (comment files) run when the service starts. If &lt;code&gt;server/.env&lt;/code&gt; still has the attachment extension list or the limit of 20 attachments that earlier versions wrote there unchanged, the script comments them out so the new defaults apply; values you changed are kept. See &lt;a href=&quot;https://github.com/Im-Sue/suduo-workbench/blob/main/cloud/DEPLOYMENT.md&quot;&gt;cloud/DEPLOYMENT.md&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Client from source: &lt;code&gt;git fetch --tags &amp;amp;&amp;amp; git checkout v0.10.0&lt;/code&gt;, &lt;code&gt;pnpm install&lt;/code&gt;, then &lt;code&gt;pnpm start&lt;/code&gt;. Local database migration 018 runs when the local service starts; your existing folder links are kept and tied to the server you’re connected to.&lt;/li&gt;
&lt;li&gt;Desktop app: install the 0.10.0 installer from this release over the old version (on macOS, quit SuDuo from the menu bar first and replace it in Applications). Your data is kept.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;known-limitations&quot;&gt;Known limitations&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;The desktop app is a trial: it isn’t signed yet (see the &lt;a href=&quot;https://github.com/Im-Sue/suduo-workbench/blob/main/client/README.md#desktop-app-trial&quot;&gt;client guide&lt;/a&gt; for opening it the first time) and doesn’t update itself. The Intel Mac and Windows packages haven’t been tested on real hardware yet.&lt;/li&gt;
&lt;li&gt;Codex can’t post comments with files yet.&lt;/li&gt;
&lt;li&gt;The cloud has no administrator or invitation system: anyone who can reach it can register. Keep it on a private network or VPN, or behind a reverse proxy with access control.&lt;/li&gt;
&lt;/ul&gt;
</description>
    </item>
    <item>
      <title>SuDuo 0.9.0</title>
      <link>https://suduo.dev/changelog/#v0.9.0</link>
      <guid isPermaLink="true">https://suduo.dev/changelog/#v0.9.0</guid>
      <pubDate>Wed, 07 Oct 2026 00:00:00 GMT</pubDate>
      <description>&lt;p&gt;Adds a desktop app for macOS and Windows, as a trial. Download it from this release and open it; you don’t need Node.js, pnpm or git. Running from source still works.&lt;/p&gt;
&lt;h3 id=&quot;added&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Desktop app (trial) for macOS 13.5+ (Apple silicon and Intel) and Windows 10 / 11 (x64). The installers are attached to this release; see the &lt;a href=&quot;https://github.com/Im-Sue/suduo-workbench/blob/main/client/README.md#desktop-app-trial&quot;&gt;client guide&lt;/a&gt;.
&lt;ul&gt;
&lt;li&gt;It includes the local service, the Codex CLI version SuDuo is tested with (0.159.2) and Node.js. It uses your &lt;code&gt;~/.codex&lt;/code&gt;, so an existing Codex sign-in or model setup works as it is.&lt;/li&gt;
&lt;li&gt;Closing the window keeps SuDuo running in the menu bar (macOS) or the notification area (Windows), so sessions keep going and Agents you share in rooms keep responding. Quit from that icon or with ⌘Q; if sessions are in progress, SuDuo asks first.&lt;/li&gt;
&lt;li&gt;If the local service stops unexpectedly, SuDuo restarts it. If it can’t start, the window says why, shows where the log is and offers to run diagnostics.&lt;/li&gt;
&lt;li&gt;Opened from Finder on macOS, it reads your login shell’s environment, so commands Codex runs in your project find the same tools as in your terminal.&lt;/li&gt;
&lt;li&gt;It keeps its own data (&lt;code&gt;~/Library/Application Support/SuDuo Desktop&lt;/code&gt; on macOS, &lt;code&gt;%LOCALAPPDATA%\SuDuo Desktop&lt;/code&gt; on Windows) and listens on port 8790, so it can run next to a source run.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Diagnostics accept any Node.js 24 from 24.10.0 on, matching what SuDuo requires. Before, any version other than 24.10.0 was reported as a failure.&lt;/li&gt;
&lt;li&gt;&lt;code&gt;pnpm start&lt;/code&gt; says when its port is used by the SuDuo desktop app and leaves it alone.&lt;/li&gt;
&lt;li&gt;Commands that Codex runs no longer inherit the local service’s own &lt;code&gt;SUDUO_*&lt;/code&gt; settings (only &lt;code&gt;SUDUO_LOCALE&lt;/code&gt; is passed on), so running SuDuo’s scripts inside a Codex session doesn’t pick up the running service’s port or data folder.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;fixed&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Image attachments in the requirement side panel couldn’t be opened. They now open in a preview, and PDFs and other previewable files open in a new tab. Clicking a file’s name works as well as the preview button, here and on the requirement page.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;upgrading&quot;&gt;Upgrading&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;No database changes, on the server or on your computer.&lt;/li&gt;
&lt;li&gt;Cloud: &lt;code&gt;git fetch --tags &amp;amp;&amp;amp; git checkout v0.9.0&lt;/code&gt;, then &lt;code&gt;sudo ./scripts/suduo-cloud.sh upgrade&lt;/code&gt;. The cloud has no functional changes in this release; upgrading keeps the version hint in Settings → About quiet.&lt;/li&gt;
&lt;li&gt;Client from source: &lt;code&gt;git fetch --tags &amp;amp;&amp;amp; git checkout v0.9.0&lt;/code&gt;, &lt;code&gt;pnpm install&lt;/code&gt;, then &lt;code&gt;pnpm start&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Desktop app: install it from this release. It starts with its own data: connect to your team’s server, sign in and choose your project folders again. Requirements and rooms are on the server, so they’re all there; sessions from a source run stay in the source run.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;known-limitations&quot;&gt;Known limitations&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;The desktop app isn’t signed yet.
&lt;ul&gt;
&lt;li&gt;macOS: the first time you open each version, macOS says it can’t verify the developer. Click &lt;strong&gt;Done&lt;/strong&gt;, then &lt;strong&gt;Open Anyway&lt;/strong&gt; under &lt;strong&gt;System Settings → Privacy &amp;amp; Security&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Windows: SmartScreen may say “Windows protected your PC”; click &lt;strong&gt;More info&lt;/strong&gt;, then &lt;strong&gt;Run anyway&lt;/strong&gt;. Some antivirus programs may flag it.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;The desktop app doesn’t update itself yet. Download the new version: on macOS quit SuDuo from the menu bar and replace it in Applications; on Windows run the new installer.&lt;/li&gt;
&lt;li&gt;The Intel Mac and Windows packages were built and tested automatically on GitHub’s machines but haven’t been tested on real hardware yet.&lt;/li&gt;
&lt;li&gt;There’s no ChatGPT sign-in inside the app yet: use an existing Codex sign-in, an API key under Settings → Model service, or sign in with the bundled Codex from a terminal (see the client guide).&lt;/li&gt;
&lt;li&gt;The cloud has no administrator or invitation system: anyone who can reach it can register. Keep it on a private network or VPN, or behind a reverse proxy with access control.&lt;/li&gt;
&lt;/ul&gt;
</description>
    </item>
    <item>
      <title>SuDuo 0.8.0</title>
      <link>https://suduo.dev/changelog/#v0.8.0</link>
      <guid isPermaLink="true">https://suduo.dev/changelog/#v0.8.0</guid>
      <pubDate>Mon, 05 Oct 2026 00:00:00 GMT</pubDate>
      <description>&lt;p&gt;Adds an English interface. SuDuo’s own text (the interface, what it tells Codex, command-line output) now comes in English and Chinese; what people write and Codex’s answers are never translated.&lt;/p&gt;
&lt;h3 id=&quot;added&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;English interface. Switch it under Settings → Appearance → Language; by default SuDuo follows your system language. Only SuDuo’s own text changes: what people write (requirements, comments, room messages, file names) and Codex’s answers are shown as written, never translated.&lt;/li&gt;
&lt;li&gt;The instructions SuDuo gives Codex (requirement card, rules, tool descriptions and tool results) are written in the session’s language, chosen when the session is created. SuDuo asks Codex to reply in the language you write in, whatever the interface language.&lt;/li&gt;
&lt;li&gt;Command-line output (&lt;code&gt;pnpm start&lt;/code&gt;, &lt;code&gt;pnpm run doctor&lt;/code&gt;, local service startup errors and &lt;code&gt;suduo-cloud.sh&lt;/code&gt;) follows the system language. Set &lt;code&gt;SUDUO_LOCALE=zh-CN&lt;/code&gt; or &lt;code&gt;SUDUO_LOCALE=en&lt;/code&gt; to choose; with &lt;code&gt;sudo&lt;/code&gt;, put it after &lt;code&gt;sudo&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;If your browser’s language isn’t Chinese, the interface switches to English after you upgrade&lt;/strong&gt;, because the language follows your system by default. Choose 简体中文 under Settings → Appearance → Language to switch back. New sessions created while the interface is in English give Codex English instructions; existing sessions don’t change.&lt;/li&gt;
&lt;li&gt;The requirement list view shows icons for the materials, comments and sessions column headers, so they fit in both languages.&lt;/li&gt;
&lt;li&gt;System text that other people see is stored as a type with parameters, so each person sees it in their own language: shared agent run reasons and progress (cloud database migration 013), @everyone mentions, the last message shown for a room, and runtime notices in a session.&lt;/li&gt;
&lt;li&gt;The last message shown in a requirement’s room section now matches the room itself: an agent appears without its device name, and attachments read like “[Image]” or “[File] spec.pdf and 2 more”.&lt;/li&gt;
&lt;li&gt;The checkpoint name in the “Restore to before this turn?” dialog now matches the environment panel.&lt;/li&gt;
&lt;li&gt;Cloud error messages are in English; the client still shows its own message for each error code, in your language.&lt;/li&gt;
&lt;li&gt;Local sessions remember their language (local database migration 017); existing sessions stay Chinese.&lt;/li&gt;
&lt;li&gt;Dates older than yesterday in the session list, the overview timeline and the checkpoint list now read like the rest of the app (for example 9月27日, or 2025年9月27日 for earlier years, instead of 09-27).&lt;/li&gt;
&lt;li&gt;A publish note that happens to read exactly like the automatic “published version” comment is now shown as a note in the activity feed.&lt;/li&gt;
&lt;li&gt;Git checkpoints that SuDuo writes now end with a &lt;code&gt;SuDuo-Checkpoint:&lt;/code&gt; line, so SuDuo recognises them whatever language their title is in. Older checkpoints are still recognised.&lt;/li&gt;
&lt;li&gt;Cloud: comments that SuDuo writes when a confirmed version is published without a note are now stored as a type with parameters (database migration 012), so every client can show them in its own language.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;upgrading&quot;&gt;Upgrading&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Upgrade the cloud first, then each client. Settings → About shows a hint while the two versions differ.&lt;/li&gt;
&lt;li&gt;Cloud: &lt;code&gt;git fetch --tags &amp;amp;&amp;amp; git checkout v0.8.0&lt;/code&gt;, then &lt;code&gt;sudo ./scripts/suduo-cloud.sh upgrade&lt;/code&gt;. It backs up first; database migrations 012 and 013 run when the service starts. See &lt;a href=&quot;https://github.com/Im-Sue/suduo-workbench/blob/main/cloud/DEPLOYMENT.md&quot;&gt;cloud/DEPLOYMENT.md&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Client: &lt;code&gt;git fetch --tags &amp;amp;&amp;amp; git checkout v0.8.0&lt;/code&gt;, &lt;code&gt;pnpm install&lt;/code&gt;, then &lt;code&gt;pnpm start&lt;/code&gt;. It rebuilds, and local database migration 017 runs when the local service starts.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;known-limitations&quot;&gt;Known limitations&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;There is no installer yet; run the client from source.&lt;/li&gt;
&lt;li&gt;The cloud has no administrator or invitation system: anyone who can reach it can register. Keep it on a private network or VPN, or behind a reverse proxy with access control.&lt;/li&gt;
&lt;/ul&gt;
</description>
    </item>
    <item>
      <title>SuDuo 0.7.0</title>
      <link>https://suduo.dev/changelog/#v0.7.0</link>
      <guid isPermaLink="true">https://suduo.dev/changelog/#v0.7.0</guid>
      <pubDate>Fri, 02 Oct 2026 00:00:00 GMT</pubDate>
      <description>&lt;p&gt;The first public release. SuDuo is now source-available under the &lt;a href=&quot;https://github.com/Im-Sue/suduo-workbench/blob/main/LICENSE&quot;&gt;PolyForm Noncommercial License 1.0.0&lt;/a&gt;; companies can start right away and register within 30 days (see &lt;a href=&quot;https://github.com/Im-Sue/suduo-workbench/blob/main/COMMERCIAL.md&quot;&gt;COMMERCIAL.md&lt;/a&gt;).&lt;/p&gt;
&lt;h3 id=&quot;cloud&quot;&gt;Cloud&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;One-command self-hosting on Ubuntu / Linux with Docker: &lt;code&gt;cloud/scripts/suduo-cloud.sh install&lt;/code&gt; builds from source, generates the secrets and starts PostgreSQL and the service.&lt;/li&gt;
&lt;li&gt;&lt;code&gt;upgrade&lt;/code&gt; backs up first, &lt;code&gt;backup&lt;/code&gt; / &lt;code&gt;restore&lt;/code&gt; keep the database and the file volumes consistent, and &lt;code&gt;restore&lt;/code&gt; backs up the current data first and starts the checked-out version, so rolling back is “check out the previous tag, then restore”.&lt;/li&gt;
&lt;li&gt;&lt;code&gt;--mirror cn&lt;/code&gt; builds with mirrors that are reachable in mainland China.&lt;/li&gt;
&lt;li&gt;The health check reports the product version.&lt;/li&gt;
&lt;li&gt;New deployment guide in English and Chinese: &lt;a href=&quot;https://github.com/Im-Sue/suduo-workbench/blob/main/cloud/DEPLOYMENT.md&quot;&gt;cloud/DEPLOYMENT.md&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;client&quot;&gt;Client&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;pnpm start&lt;/code&gt; checks the environment, builds when needed, starts the local service and opens the browser on macOS (Apple silicon and Intel) and Windows 10 / 11. &lt;code&gt;Ctrl+C&lt;/code&gt; stops it cleanly.&lt;/li&gt;
&lt;li&gt;Settings → About shows the cloud’s version and a hint when it differs from the client.&lt;/li&gt;
&lt;li&gt;Settings → About shows the license and how to register commercial use.&lt;/li&gt;
&lt;li&gt;Default local data directory on macOS is now &lt;code&gt;~/Library/Application Support/SuDuo&lt;/code&gt; (it was &lt;code&gt;~/.local/share/suduo&lt;/code&gt;; SuDuo tells you if it finds data in the old place).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;fixes&quot;&gt;Fixes&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Without &lt;code&gt;CODEX_HOME&lt;/code&gt; set, the local service pointed Codex at a directory inside the repository that does not exist, so Codex could not start. It now uses &lt;code&gt;~/.codex&lt;/code&gt; and creates it when missing.&lt;/li&gt;
&lt;li&gt;On Windows, Codex now starts even when the repository path contains spaces.&lt;/li&gt;
&lt;li&gt;Pressing &lt;code&gt;Ctrl+C&lt;/code&gt; in a terminal no longer kills the local service before it finishes shutting down.&lt;/li&gt;
&lt;li&gt;The self-check no longer fails just because SuDuo itself is running.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;known-limitations&quot;&gt;Known limitations&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;The interface is in Chinese only; English is in progress.&lt;/li&gt;
&lt;li&gt;There is no installer yet; run the client from source.&lt;/li&gt;
&lt;li&gt;The cloud has no administrator or invitation system: anyone who can reach it can register. Keep it on a private network.&lt;/li&gt;
&lt;/ul&gt;
</description>
    </item>
  </channel>
</rss>
