Every version. Every fix.

SynaBun 2.1.0 adds downloadable release verification reports, improves automated package publishing, and changes Windows clipboard images to explicit paste.

✨ New

• Release verification reports — Desktop downloads and the npm package are checked with VirusTotal before publication. Release notes include analysis dates, engine results, file hashes and links to the reports. These results describe the scans and do not guarantee that a download is safe.

🛠 Fixed

• Automated npm publishing — The npm package is published from the prepared release and verified against the scanned package before desktop downloads become available. This helps keep package installation and desktop updates on the same release.

⚙️ Changed

• Explicit clipboard image paste on Windows — Focus the whiteboard and press Ctrl+V to add a clipboard image. Background clipboard monitoring has been removed; screenshot files in the watched folder still appear automatically. This change addresses a suspected source of antivirus alerts, but resolution of the reported Kaspersky detection has not been confirmed.

virustotal.json · virustotal.md · npm-virustotal.json · npm-virustotal.md · VERIFICATION-SHA256SUMS

VirusTotal verification

Match the exact file and SHA-256. Results describe engine detections and coverage at the analysis date, not a guarantee of safety. Website results describe URL reputation, not a vulnerability audit.

Review for https://synabun.ai/ (4e7e38b578a4c2323f8bf3eca21250c7036d6b07b64c97ab7f4e1acaa44fc5bf), evidence e44c4f2ae9fac906e53b69845250467f1de629ef01596dd48332c12d80093763: Release owner (danilokhury); Owner explicitly authorized publication after disclosure of the isolated Bfore.Ai URL reputation finding (1 malicious, 58 harmless, 34 undetected engines). All release packages have no detections. This exception does not establish that the URL finding is a false positive.; reference https://www.virustotal.com/gui/url/4e7e38b578a4c2323f8bf3eca21250c7036d6b07b64c97ab7f4e1acaa44fc5bf; expires 2026-10-30T19:39:50.279Z.

VirusTotal verification

Match the exact file and SHA-256. Results describe engine detections and coverage at the analysis date, not a guarantee of safety. Website results describe URL reputation, not a vulnerability audit.

2.0.12 makes Skills Studio easier to install from, test and maintain, keeps dispatched workers running through a server restart, and adds a guided tour of the workspace. It also moves OpenCode support to OpenCode 2 and makes the 3D memory map the default for everyone.

✨ New

• Skill health and local usage — Skills Studio shows local evidence of skill use in Claude Code, Codex and OpenCode runs, with native invocations distinguished from inferred reads. Optional periodic checks report integrity and eligibility changes to the Assistant.
• A guided workspace tour — The help button opens a tour on SynaBun's own whiteboard, with pointing arms, handwritten labels and steps that follow the workspace. It supports narrow windows, English and Portuguese, and reduced motion. The handwriting font ships with the app.
• Tool lists — Choose the SynaBun tools and external MCP servers available to a session, worker or automation from reusable tool lists. External server choices report why a requested server cannot be used, with provider context to help recover.

🛠 Fixed

• Workers resume after a restart — Dispatched Claude Code, Codex and OpenCode workers can pause during a SynaBun server restart and resume the same run and provider conversation in the same sidepanel tab.
• Server crash recovery — SynaBun restarts a server that crashes and reports the reason. Desktop recovery shows the failure and recovery state, and a stalled Codex title request no longer holds the server open indefinitely.
• MoreLogin attachment and cleanup — Connecting to a MoreLogin profile preserves its native HTTP cache and WebSocket APIs while keeping SynaBun's network guards. Closing a connected browser session also closes the automation tabs SynaBun opened for it, so they do not return on the profile's next start.
• Worker startup and permissions — Codex workers start correctly when external MCP servers are disabled. Protected OpenCode workers receive MCP tools directly with Code Mode disabled, and Codex Plan mode with automatic approvals no longer repeats permission requests in the Assistant.
• Claude Code hooks from the desktop — Hooks work when SynaBun starts from the macOS Dock. Settings shows their actual state and lets you switch them on or off.
• Stopping the intended worker — A request naming one run stops that run. The Assistant's Stop all control requires a second press before it stops every running worker.
• Compact activity and app layout — Activity bubbles use one busy indicator and at most one ellipsis, with long paths and URLs wrapping at separators. Browser tabs and Safari web apps have consistent spacing between the navigation bar and the app frame, and Codex output and tab layout handle narrow panels more reliably.

⚙️ Changed

• Installing approved skills — Review approval and installation have clearer, separate states. Publishing an approved skill presents one install decision with readable runtime targets, and Claude Code, Codex and OpenCode share the drafting, evaluation and installation workflow. Skill checks cover more shell wrappers, asset references and command forms while keeping passive references distinct from executable instructions.
• OpenCode 2 required — OpenCode 1 support is removed. Every launch path checks the installed version before starting and explains how to install OpenCode 2 when needed.
• One memory map — The memory map uses 3D. Saved 2D preferences and old links open in 3D, and the 2D switch and shortcut have been removed from the interface.
• Project test commands — Browser policy permits test runners inside registered code projects and accepts syntax-only Node checks. Commands that execute preloaded code still receive the normal policy checks.

2.0.11 rebuilds Skills Studio around a skill library: every skill in one list, a workspace to edit, test, version and publish it, native skill folders for Claude Code, Codex and OpenCode, a Review queue, and skills drafted by AI from your own sources. SynaBun's memory is also one command away for any MCP client (npx -y synabun mcp), the whole app has a right-click menu, desktop updates show a splash and restart in seconds, and the Schedules window speaks your language.

✨ New

• Skills Studio 2.0 — Skills Studio is now a window with three places: Library, Review and Create. The Library lists every skill once, whichever tool or account reads it, with where it comes from, what Claude Code, Codex and OpenCode each have of it, and a health badge for what needs a look (problems, an update available, a skill defined twice, an old-style install); filters, saved views, search and bulk actions keep it in order. A skill opens in a workspace with Edit, Test, Versions and Publish: the app's code editor, a form and the YAML kept as one document, the problems each runtime would report, a description helper, the skill's files, a Markdown preview with diagrams, versions with diffs and restore, and an install of exactly the plan you see. The window is not modal, docks beside the side panels, fits narrow widths and works fully from the keyboard, in English and Portuguese.
• Native skill folders for Claude Code, Codex and OpenCode — Installing a skill now puts it in each runtime's own skill folder, with a backup, a check after the install and a way back. Skills installed the old way, as Codex prompts or OpenCode commands, can be moved to the native folders from Settings › Skills › Skill folders: you see the plan first, nothing moves until you press Move, and Undo puts every one back. Nothing is moved at start, during an update or by an agent. The Codex panel runs a skill you pick as a Codex skill, and a skill's arguments are filled in the way Claude Code fills them.
• Skills drafted by AI, and a Review queue — Create's AI box drafts a whole skill from your description and up to five sources: a Claude Code, Codex or OpenCode session, a web page, a registered project, memories, a library skill or an imported bundle. One worker writes it in a folder of its own and can only read and write there; the result is checked, comes with test prompts and lands in Review. While it runs you see its steps, the files written so far, the time and the cost, and you can cancel. The SynaBun Assistant creates and improves skills the same way, with its bundled skill-forge workflow. Whatever an AI makes waits in Review and is installed only after you approve it.
• synabun mcp — The npm command now starts SynaBun's MCP server on stdio, for Cursor, Windsurf, Claude Code, Codex or any other MCP client: "command": "npx", "args": ["-y", "synabun", "mcp"], or "command": "synabun", "args": ["mcp"] after npm install -g synabun. It is the same server, with the same memories and data folder, as the one SynaBun registers for your tools. Only the protocol goes to its output, and it stops when the client that started it stops it.
• The official MCP Registry — The npm package now names SynaBun's entry in the official MCP Registry, io.github.danilokhury/synabun, which MCP clients and directories read to find a server and how to start it.
• Clickable follow-ups in the Assistant — When the Assistant ends a turn with options or a question for you, they appear as buttons under its message: one click sends the answer, a set of choices becomes checkboxes with one Send, and Something else… takes you to the composer.
• A countdown to a usage-limit reset — When a provider's usage limit stops the Assistant or one of its workers, a card shows a live countdown to the reset and the local reset time, then Retry now. A worker is retried on the same model.
• A right-click menu for the whole app — A right-click anywhere that has no menu of its own now opens SynaBun's: page actions (Back, Forward, Reload, Copy, Full screen), then what fits what you clicked (selected text, a link, an image, a memory on the map, in the Memory Explorer or on a card, the empty space of the 3D or 2D map, the Focus mode board and its tools), then every panel and tool with its keyboard shortcut. Fields and Shift + right-click keep the browser's menu, and the terminal, the File Explorer's tree, editor tabs and graph cards keep their own. The Menu key and Shift + F10 open it from the keyboard.

🛠 Fixed

• Skills Studio keeps your work — The Studio could erase frontmatter it did not show, mark text typed during a save as saved, save one skill's file under another's name, lose unsaved work on Escape or close, rewrite every line ending of a Windows-style file, write into SynaBun's bundled skill, replace or delete a same-named skill SynaBun never installed, and install an imported bundle unseen. Now an edit changes only the field you touched, a save that would overwrite a change made elsewhere asks first, bundled skills are read-only with Customize a copy, a skill SynaBun did not install is backed up and changed only after you confirm, and an import is checked, scanned and shown to you before anything is written.
• A complete MCP server build — SynaBun now checks that its MCP server is built completely, every module it loads and not only its entry file, and builds it again at install or start when something is missing.

⚙️ Changed

• Desktop updates — Updating the desktop app no longer leaves you without a window: a small splash with the mascot shows at every start and through every step of an update, with a progress bar and Details. Once an update is downloaded, the update button becomes Restart to update (also in the app menu, the File menu and the tray), which installs at once when SynaBun is idle, or when the running work ends. The safety snapshot of your data is prepared ahead in the background and compared with your data at the restart, so the new version opens in seconds instead of minutes on a large memory store, and every database copy in it passes an integrity check. On a Mac the app is without a window for about a second, and dark pages on some Macs no longer show a lighter band across the middle.
• synabun help — synabun help, synabun --help and synabun -h list every command and the data folder in use. Before, they started SynaBun.
• Schedules in your language — The whole Schedules window now follows the app's language: every view, row, editor, dialog and message, schedules described in plain words, and dates and times in your locale. Changing the language with the window open brings you back to the same view.

2.0.10 works with OpenCode 2, adds a Settings › App page for updates and start at login, and opens menus, model lists and Settings at once instead of waiting on the network, most noticeably in the Windows desktop app. It also redesigns the Schedules window, shows every worker the Assistant dispatches at work, and closes a security hole in the Codex panel.

✨ New

• OpenCode 2 — With OpenCode 2 installed, every OpenCode feature in SynaBun failed. SynaBun now works with OpenCode 1 and OpenCode 2 alike: the OpenCode panel, the Assistant's OpenCode brain and workers, schedules, loops and Automation Studio, the code editor's AI autocomplete and session titles. It finds out which one you have and speaks to it accordingly.
• Settings › App — A new page in the SynaBun group of Settings, above About. Updates shows your version and the last check, with Check for updates, Install update and an Automatic updates switch (on by default). With it off, the desktop app still tells you about an update but downloads and installs nothing until you choose Install now, and an npm or Git install no longer checks on its own. Start at login (off by default) works on macOS, Windows and Linux, for the desktop app and for an npm or Git install, and can start SynaBun in the background. The desktop app adds Keep running when the window closes (Windows and Linux) and Hardware acceleration, and Maintenance opens the data or logs folder and restarts SynaBun.
• Workers at work in the Assistant panel — While a worker the Assistant dispatched is queued or running, its card shows a small live scene for the kind of task, its current step and a clock, also after the Assistant's own reply has ended and after a page reload. When the worker finishes, the card says Done, Failed or Stopped.
• Remove a session — Each row of the Assistant's Sessions menu has a remove button. It asks in the row, stops the session's running work and deletes the session; memories made from it are kept.

🛠 Fixed

• Codex panel security — The Codex panel put a model's formatted reply into the page as it was, so HTML in a reply, in a quoted web page or in a file the model read could run inside SynaBun. Every Codex message, and every saved Codex and Claude Code transcript, now goes through the same strict filter as the other panels, and text agents write is escaped in the memory, terminal, whiteboard, Skills and Settings views. The Markdown, diagram, code-highlighting and screenshot libraries now ship with SynaBun instead of loading from a CDN, an SVG opened from the image gallery can no longer run anything, and a link whose scheme is hidden behind a tab, a line break or a character entity is no longer treated as a link to a file.
• OpenCode only stops its own servers — SynaBun now stops an OpenCode server only when it can prove that it started that server itself and that the SynaBun which started it has ended. A server left running by a SynaBun that crashed is cleaned up at the next start, your own OpenCode servers are left alone, and starts that happen at once no longer collide. On Windows, servers started through an npm-installed OpenCode are now tracked too.
• Questions and approvals that wait on you — Open OpenCode questions and permissions are read again after a reconnect or a page reload, so a turn's clock no longer runs while it waits on you, and a sub-agent's question keeps its parent waiting. A Codex approval no longer goes missing after a reload. Claude Code and Codex tabs and worker pills show "needs you" while they wait on a permission, a plan approval or a question, and a worker's card says "waiting for your answer".
• Minimized session pills — A minimized session's pill keeps its running animation for as long as the session works, in every provider: while the Assistant's workers run, while a Claude Code tab's background agents or shells run, after a Codex tab reconnects, and for the Assistant in a terminal tab. The way back from an OpenCode sub-agent now stays visible at every panel width, the Codex queue hint follows the tab on screen, and the Assistant's rack redraws right after a resize.
• Schedules keep what you did not change — Saving a schedule or a group could clear settings you never touched, such as a Codex account or a thinking level set to off, and changing a group's CLI could reset schedules that had changed meanwhile. The editors now save only what you changed, a list that fails to load says so instead of showing up empty, a group's new CLI reaches its schedules, and a day theme can be removed.
• One update dialog at a time — Opening the update dialog again from the badge, a notification or Settings no longer draws a second one over the first.
• A lighter desktop title bar — The desktop app no longer measures its title bar after every change on the page, which cost time on every chunk of streamed text and terminal output.

⚙️ Changed

• Menus, model lists and Settings open at once — Model lists, provider lists, the Assistant's menus and Settings now open from what SynaBun read last and refresh in the background. In the Windows desktop app the Codex model list could take ten seconds, OpenCode's provider list over a second every time, and the whole server could stall for a few seconds; these lists are now read once at launch and kept between starts.
• Assistant sessions are saved with your first message — Opening the Assistant or a new session no longer stores an empty session, so the Sessions menu no longer fills with empty rows, and a session you close without chatting is not kept.
• Schedules — Schedules has its own button in the menubar, and its window is redesigned: views for Up next, All schedules, Needs attention, Paused, Timers and Activity, your groups beside them, search, rows with an on/off switch, the next and last run side by side, and details when you ask for them. Every dropdown in it is the app's own, with full keyboard support. Games and the 3D map's commands moved into the Apps menu.

2.0.9 makes npm installs and updates more reliable, especially on Windows: SynaBun's dependencies are installed in one place at pinned versions, none of them runs its own install script, and the Windows updater closes the SynaBun processes your AI clients started before it replaces the package. A fresh install now starts with no memory categories, Codex on Windows no longer asks for administrator approval when SynaBun starts it, and the Assistant's account menu is easier to read.

✨ New

• Admin sandbox — When SynaBun started Codex on Windows, Codex could ask Windows for administrator approval (a UAC prompt) to set up its elevated sandbox, once for every Codex account, and a scheduled or background run waited on a prompt nobody saw. Codex started by SynaBun now uses the Windows sandbox that needs no administrator approval, which isolates commands less strictly. To use the elevated one, turn on Admin sandbox at the end of the Assistant's permission menu, under Every agent. It is off by default, applies to every agent SynaBun starts and never changes your own Codex settings; Claude Code and OpenCode are not affected.

🛠 Fixed

• npm installs and updates that failed on Windows — An install or update could stop with "Failed to install MCP Server dependencies", or fail because a SynaBun MCP server that an AI client had started still held files of the package open. All of SynaBun's dependencies are now installed together with the package, at the versions the release pins, and SynaBun no longer runs npm when it starts. On Windows the updater first closes the SynaBun processes that AI clients started from the install folder, and tries again when Windows still holds a file.
• Installs that downloaded or compiled extra parts — No dependency runs its own install script during an install or update any more. On Linux x64 an install could download CUDA libraries SynaBun never uses, and on a computer with its own libvips the image library tried to compile itself and failed.

⚙️ Changed

• No memory categories until you need them — A fresh install starts with no categories, so categories you never used, such as the YouTube one, no longer appear. Adding a project creates its five default categories once: a default you delete stays deleted, and starting a session no longer brings it back. A feature such as conversations, plans or ideas creates its own category the first time it saves something. Categories you already have are not changed.
• The Assistant's account menu — ⚙ → Account shows each account on one row with its plan or API key, who is signed in and how much usage is left, with the reset time in words. A signed-out account opens its sign-in, and the account your workers use is in the same menu. The composer's Model menu shows the same rows, and the model chip shows the model with the account's initial, with the account's name in its tooltip.
• Side panel headers stay on one row — In a narrow Claude Code, Codex or OpenCode panel, the session name gets shorter instead of the header wrapping onto a second row, and the whole name shows when you point at it.
• Repairing an npm install — When an npm install needs repairing, the launcher names the command: close SynaBun and every AI client that uses it, then run npm i -g synabun@<version> with your version. A plain npm rebuild -g runs the dependencies' install scripts again, so do not use it.

2.0.8 fixes the Windows installer of 2.0.7, which could not finish on any Windows PC. It now installs in a few minutes, and when something does go wrong it says what and where to look. macOS, Linux and npm installs were not affected.

🛠 Fixed

• The Windows installer of 2.0.7 never finished — On every Windows PC, the 2.0.7 installer unpacked SynaBun, could not check the files it had unpacked, unpacked everything again several times over more than ten minutes and then showed a box that blamed the disk space. One of its scripts could not be read by the PowerShell that comes with Windows, so the check never ran. The 2.0.8 installer finishes. If the 2.0.7 installer is still open on your PC, click Cancel in its box before you start the new one.
• Clear errors when an install cannot finish — The installer never unpacks again by itself. If files are missing or incomplete, it names them and shows how much space the disk has left and where the installation log is: Retry unpacks once more, and Cancel stops and puts back the SynaBun you had. The installation log now also shows what the installer did to close SynaBun and to check the files.
• Leftovers of a failed install — A copy that a failed 2.0.7 install left on your PC is replaced cleanly by the new version.

⚙️ Changed

• Faster Windows installs — Installing over an earlier version moves the old copy aside in one step instead of uninstalling it file by file, the check of the unpacked files takes about a second, and the app carries about 2,300 fewer files for Windows to write and scan.

2.0.7 brings the SynaBun desktop app for macOS, Windows and Linux, with updates that install themselves and a Windows installer that shows every step. SynaBun now finds every installed Claude Code, Codex and OpenCode the same way and installs a missing one with one click, you can sign in from the Claude and Codex panels, and the WhatsApp Assistant can send you files and understand voice notes.

✨ New

• SynaBun desktop app — The installers are now a real desktop app: SynaBun opens in its own window on macOS (Apple Silicon and Intel), Windows x64 and Linux x64, around the same server, runtime and interface as before. The window has SynaBun's own title bar instead of the system's: the window buttons sit at its right end on Windows and Linux, where a button at the left opens the menu, and the traffic lights sit inside it on macOS. Closing the window keeps SynaBun running; the app menu, the Dock or the tray bring it back. npm and Git installs are unchanged.
• Updates that install themselves — The desktop app checks the public releases shortly after it starts and every few hours. A newer version downloads at once. When SynaBun is idle, a one-minute notice with Later counts down, then the update installs, the window reopens as it was and a notice says what it updated to. While work is running it waits, and it also installs when you quit or at the next start. Install now is in the update dialog and the menus. If an update fails, the version you have keeps running, you get a link to download the new one yourself, and it tries again later.
• A Windows installer that shows every step — The installer lists each step as it goes, with the seconds since it started: the check for a running SynaBun, the unpacking with its progress, each part as it is put in place, the shortcuts and the Settings → Apps entry. The uninstaller lists its steps too, and the whole list is saved to a log you can open from the last page. If SynaBun is running, the installer asks once and closes it for you, letting the server shut down cleanly first; it never touches a SynaBun installed with npm or Git. Installing is faster: the files are unpacked straight into place, and the app carries about 6,600 fewer files. An install counts as finished only when every file is in place, and an update that cannot finish leaves the version you have running. Updates from the app stay silent.
• See what the desktop app is doing while it starts — Details on the start screen shows a live log of the start: the checks, the browser download with its progress, the build and the server's first lines. It opens by itself on the first start and when something fails, and keeps the real error. In the setup wizard, Details under Environment Check and Install & Build show the commands that ran with their answers, and what the app came with.
• npm and npx come with the desktop app — They work even when your computer has no Node.js. Your own npm and tools always come first; the bundled ones are only a fallback, and their global installs go to a folder in SynaBun's data folder instead of into the app, unless you set an npm prefix of your own.
• Git Bash for Claude Code on Windows — On a Windows PC without Git for Windows, Claude Code ran its hooks in PowerShell, where SynaBun's hooks do not work. SynaBun now brings its own unchanged copy of Git for Windows and uses it only when your PC has none: the Windows installer carries it, and an npm install on Windows downloads it once and checks it against a pinned checksum before unpacking it. A Git you installed yourself always wins, and Settings → AI connections → Executable paths shows which one Claude Code gets.
• Settings → About — A new last page in Settings shows your version and how SynaBun is installed, with Check for updates and Copy info (version, install type, Node.js, SQLite, the desktop app's Electron and Chromium, your system and the dependency versions; no paths, ports, keys or settings). It also has the project's links, system details and every dependency with its version and license.
• SynaBun finds your Claude Code, Codex and OpenCode — The side panels, Settings and every launcher find each CLI the same way: the path you set in Settings first, then your PATH as a new terminal sees it, then the folders the official installers use. A CLI that is found but does not start shows its real error instead of "not installed".
• One-click install of a missing CLI — When Claude Code, Codex or OpenCode is not installed, its panel shows a banner with Install, which runs the vendor's official installer for your system and shows its progress, next to the manual command and the install guide. The OpenCode panel gets this banner too. Add to PATH makes an installed CLI available to new terminals.
• Sign in from the Claude and Codex panels — /login and the new account button open a sign-in card that drives each CLI's own sign-in: open the sign-in page, finish in your browser, and the panel shows who is signed in. Codex also offers a device code. Tokens stay with Claude Code and Codex, SynaBun stores none, and sign-in cards are never saved into stored chats.
• Auto · most usage left — Claude Code and Codex routes and the composer's model menu can pick the subscription account with the most usage left. Usage windows show beside each account, and an exhausted account falls back to another one of the same provider.
• The WhatsApp Assistant can send you files — Ask for a file on your computer and the Assistant sends it to your WhatsApp chat as a real attachment, with an optional caption: pictures, videos and audio as such, anything else as a document with its name. Files go only to your own chat, files over 100 MB are refused, and SynaBun's own data, your WhatsApp session, your AI tools' settings and keys, and system folders are never sent, whatever path leads to them.
• WhatsApp voice notes — Voice notes and audio messages can now be transcribed on your computer and reach the Assistant as text. Turn on Transcribe voice notes in Settings → Messages → WhatsApp; it uses your own FFmpeg and whisper.cpp with a model you provide, and no audio leaves your computer. The status line says what is missing. A transcribed note is never taken as a command or an approval, and typed commands such as /stop never wait behind one.
• Language and showcase addresses — Adding ?lang=pt-BR to the interface's address opens it in that language for that page only. ?showcase opens it without saving any change to your layout and blurs your memories, sessions, transcripts, terminal output and other personal content, for screenshots and recordings.

🛠 Fixed

• A named Claude profile could run as another account — A side-panel tab on a named Claude profile could run with the credentials SynaBun itself was started with. It now runs only under its own profile.
• Codex could start without SynaBun's tools — The panels, the Assistant, workers, schedules and loops now register SynaBun's MCP connection with Codex when it is missing, without replacing one you connected yourself.
• Terminals did not see newly installed tools — Every new terminal reads the current system PATH, so a CLI installed after SynaBun started is found.
• The MCP server reported version 2.0.0 — It now reports SynaBun's real version.
• The WhatsApp link stopped after a connection error — The link no longer gives up on its own after a stream or connection error from WhatsApp, a burst of reconnects or repeated restarts of the connector. It keeps retrying with your saved session and recovers without Reconnect, and stops only when WhatsApp says the session is no longer valid.
• Answers to WhatsApp got lost when a task moved to another model — When the Assistant continued a task you sent from WhatsApp on another model, its answer did not reach your phone. It now comes back once to the chat that started it.
• The memory search sat under the menu — In the Map view, above all in Portuguese, the search field was drawn under the menu labels and could not be used. It now has its own place in the bar at every width and in every language, and turns into a search icon when there is little room.

⚙️ Changed

• One Assistant budget per session — Five separate caps are replaced by one budget per session, or No limit. The Budget chip next to Project sets it for a new session, and the spend chip, the Budget menu and /budget show how it is shared between Claude Code, Codex and OpenCode and what is left. When one provider's share runs out, the rest is rebalanced.
• The Assistant mascot follows Project and Budget — It looks at the Project and Budget chips you point at, and reacts once when a budget is saved.
• A dispatched run's time limit counts work time only — The limit of a run the Assistant dispatches now runs only while the worker is working. Time in the queue, idle time between follow-ups and time waiting for your answer to a permission or a question no longer use it up, so a late follow-up is not cut off midway. The limit is never below 20 minutes.
• WhatsApp Autonomous stays on until you turn it off — Autonomous no longer ends after 8 hours: it stays on until you lower it in Settings. /pause pauses messages and /stop stops the current task, and neither changes the level. A level that was turned on under the old 8-hour rule comes back as Ask after the update.

SynaBun 2.0.4 lets you set how much testing the Assistant asks of the workers it dispatches, makes browser_screenshot answer instead of hanging when the browser cannot produce an image, and stops asking whether to install SynaBun as an app. It is the first release since 2.0.0.

New

• Test density for the Assistant. A three-bar gauge next to the permission mode in the Assistant's composer sets how much testing dispatched workers are asked to do: None, Light (the default), Standard or Thorough. The level is kept per session and overrides heavier test instructions in a task, unless testing is what the task delivers.
• Automation tabs can open behind your work. With "openTabsInBackground": true in browser-config.json, every tab SynaBun opens in a MoreLogin profile or an attached Chrome opens behind the selected tab, and the window is not brought to the front when a run starts. Off by default.

Fixed

• browser_screenshot could hang until the caller timed out. A capture with no answer in 8 seconds (1.5 when the window is reported minimized) now fails with SCREENSHOT_NOT_PRESENTING, names the phase it stopped in and the window state the browser reported, and puts the tab back at its own size.
• Closing tabs could leave a browser session pointing at a closed page. The switch now picks a tab that is still open.

Changed

• SynaBun no longer asks about installing as an app. In Chrome and Edge the browser's own install dialog opens once, from a click or key press you make anyway: in the setup wizard on a first run, and in SynaBun once setup is complete. Accepted, dismissed or never offered, SynaBun goes on the same way. Apps → Install as App is the way in by hand, and Safari shows its instruction (File → Add to Dock).

Full changelog

Native installers

Check a download against the attached SHA256SUMS.txt. Each installer includes the Node runtime, the local embedding model and the native libraries for its system. Claude Code, Codex, OpenCode and Gemini CLIs are not included; install them separately. There is no 32-bit Windows build.

To update an existing installation, stop the server first (Apps → Stop Server), then replace the app in Applications (macOS), replace the AppImage file (Linux) or run the installer (Windows). Your data is kept.

These builds are unsigned, and the macOS builds are not notarized: macOS and Windows ask for confirmation before opening them. The macOS images were run on Apple Silicon, the Intel image through Rosetta 2; the Linux and Windows installers were checked without being run.

Source commit: 9393942ba8013e6cfd6b5ac2515b14cf51f15139.

SynaBun 2.0 adds a central Assistant for Claude Code, Codex and OpenCode, WhatsApp Link, Memory v2, a rebuilt memory map, optional AI decisions, and redesigned Settings and provider panels. This release adopts plain semantic versioning.

Highlights

• Assistant task routing, budgets and token accounting, with WhatsApp access.
• Hybrid memory retrieval, revision history and a memory map that shows every memory.
• Per-project Style Guide exports, installed rules, and English and Brazilian Portuguese settings.
• Rebuilt Claude Code, Codex and OpenCode panels, faster terminals and browser tools.
• Fixes for WebSocket origin checks, large backups, pre-update snapshots, exact-version updates and session cleanup.
• Temporary Claude chats clean up new plan files even when filesystem timestamps lag the application clock, while preserving plans that existed before the session, including after edits or renames.

Full changelog

Native installers

Verify downloads against the attached SHA256SUMS.txt. The installers include the Node runtime and local embedding model. Claude Code, Codex, OpenCode and Gemini CLIs must be installed separately.

On first launch, confirm installation of the SynaBun PWA in a supported browser. Later launches start or reuse the background server and open that installed PWA. Closing its window leaves the server running; use Apps → Stop Server to stop it. See installation guidance.

These builds are unsigned; macOS builds are not notarized. macOS and Windows may require confirmation to open them. Linux and Windows payloads were statically verified; native execution on those systems was not tested.

Updating from 2026.x

Older date-version installs require one manual update with npm i -g synabun@latest after npm publication completes. From 2.0.0 onward, use the in-app updater.

Source commit: 48a1cecb980dd2338d219238ba2a823d4766e08c.

Everything from 2026.07.20 through 2026.07.33 in one drop. Agents now run in native SynaBun sidepanels instead of terminal PTYs, the Claude sidepanel is a full Agent SDK client, tool profiles are session-scoped, and updates that used to take minutes are back to seconds.

✨ New

• Native automation sidepanels — Claude Code, Codex, and OpenCode loops and schedules run in their native sidepanels instead of terminal PTYs: faster launches, real background execution, correct focus on manual runs.
• Claude Code Agent SDK engine — Full CLI-style sessions in the Claude sidepanel with tool calls, permissions, plan review, multiple tabs, account-safe ownership, and restored sessions.
• Session-scoped MCP profiles — Codex tabs, OpenCode sessions, loops, and schedules can own an isolated tool profile that switches in place without touching another runtime or the default.
• Live Claude model discovery — The model list is read from the installed CLI at runtime instead of two hand-maintained lists that had drifted. Every picker is covered, and xhigh thinking is finally selectable everywhere.
• Bluesky MCP tools (15) — Feeds, search, profiles, threads, notifications, DMs, posting, images, engagement, and moderation through the logged-in bsky.app session.
• MoreLogin browser support — Anti-detect profiles as a first-class browser backend, with profile management in Settings and an MCP action tool.
• Reference-based browser snapshots — AI browser sessions work from compact element references instead of re-consuming full page snapshots. Fewer tokens, same determinism.
• Project storage cleanup — A Projects area in Settings measures and clears build, test, cache, and dependency directories across macOS, Windows, and Linux. Git-tracked files, nested repos, and SynaBun's own runtime all fail closed.
• Stronger scheduling controls — Queue visibility, cross-group mutual exclusion, group-level launch overrides, per-launch OpenAI accounts, and shared runtime options across Automation Studio and Schedules Studio.
• Codex workflow upgrades — Project-aware @ file mentions, multi-account switching and resume, inline plan refinement, persistent MCP approvals, interactive choices, live model metadata, and dynamic reasoning controls.

🔧 Fixed

• Updating took several minutes on a large data home — The pre-update snapshot archived everything, so a multi-GB data home spent minutes compressing during npm install; one report was 9,470 files and 3,832 MB. Upgrade snapshots now skip generated media and fall back to irreplaceable state only when what remains is still over ~1 GB. Scheduled and manual backups are unchanged and still capture everything.
• First launch after an update looked frozen — The snapshot ran silently and an interrupted run left a partial archive nothing reclaimed. It now reports every phase with file counts and sizes, stores already-compressed payloads, and cleans up after itself. A 1.8 GB data home went from 17.8s / 543 MB to 9.7s / 172 MB.
• Codex could not be found on Windows — Even with the global CLI installed. Discovery no longer depends on PATH, both vendor layouts and all three package locations are checked, and the sidepanel prefers a real .cmd launcher over npm's unspawnable shell shim. A missing runtime now says which problem it is.
• Sidepanel launched Opus 4.8 when Opus 5 was picked — The picker and the sidepanel resolved the same alias against different model tables. Both sides now resolve identically, and version skew is reported instead of passing silently.
• Claude model pricing — Corrected against published list prices. Opus 5 was missing entirely and fell through to a Sonnet fallback; Opus and Fable rows were inflated roughly 3x.
• Cross-session isolation — Codex and OpenCode events, transcripts, child agents, approvals, tabs, projects, and accounts no longer leak into unrelated sidepanels or resumed sessions.
• Concurrent browser automation — Server-authoritative tab ownership keeps loops, schedules, agents, and interactive sessions on dedicated tabs; recovery repairs wedged pages without stealing another automation's work.
• Schedule reliability — Run Now no longer queues silently, missed jobs recover after clamshell sleep, automatic runs stay in the background, and startup failures are persisted instead of disappearing.
• Agent interaction deadlocks — Permission stalls, premature prompt rejection, broken plan approvals, missing tool results, and loop hangs after transient API or socket errors, across all three runtimes.
• Crash and corruption paths — Playwright lifecycle crashes, graph-link heap exhaustion, onnxruntime-node shutdown failures, frozen supervised logs, and backup replacement errors in macOS-protected folders.

⚙️ Changed & Improved

• The SynaBun browser is the default public-web path — Public-web browsing, search, and page retrieval go through the configured SynaBun browser; other web tools require an explicit request, and agent-facing Playwright and Chrome DevTools default to localhost testing. All five provider rulesets move 1.0.0 → 1.1.0, so existing users are prompted to refresh their defaults.
• Safer application data — Mutable state lives outside the Git checkout by default, with verified migration, conflict detection, synabun doctor, rotating checksum-verified backups, recovery tooling, and automatic MCP client path repair.
• Neural Interface performance — Memory Explorer virtualization, faster file-tree scanning, idle render-loop pausing, cheaper graph interactions, and lower-cost terminal rendering.
• Browser lifecycle diagnostics — MoreLogin/CDP teardown, pinned-tab recovery, co-ownership, and route validation now fail closed and expose clearer recovery state.
• Accessible UI polish — Global reduced-motion support, refined navigation styling, responsive permissions layouts, and smoother dragging, resizing, tooltips, and detail cards.

Update:

npm i -g synabun@latest

Full notes: CHANGELOG.md