Skip to content

OpenSuperBot v0.6.0: desktop app, first-run wizard, and file attachments

Latest

Choose a tag to compare

@github-actions github-actions released this 13 Nov 12:07
· 3 commits to main since this release

A desktop app for macOS and Linux (.dmg, .deb, .AppImage), a first-run setup wizard, a settings page and a refined workbench UI — so trying OpenSuperBot needs neither Node, pnpm, Docker nor a terminal — plus @ mentions in group threads, file and PDF attachments, a startup release check (with no auto-updater while builds are unsigned), and a tool-scoping fix so only turns you start can change rules or routines.

First-open notes for desktop installers (walkthrough and SHA-256 verification in docs/desktop.md):

  • macOS (mac-arm64.dmg / mac-x64.dmg): ad-hoc signed, not notarized with an Apple Developer ID yet. Drag OpenSuperBot into Applications, open it once, click Done (not Move to Trash), then click Open Anyway in System Settings → Privacy & Security.
  • Ubuntu 24.04+ (linux-amd64.deb / linux-arm64.deb): prefer the .deb over the .AppImage so bubblewrap and the AppArmor userns profiles are installed automatically.

Security

  • Only turns you start can change a teammate's standing setup. Saving or forgetting a rule and creating or stopping a routine used to work in any turn, so text in a webhook payload, a page a routine read, or a teammate's handoff could have left a new routine or removed one of your rules behind. These four tools are now offered only in a turn you started, refused if the model names them anyway in any other turn, and the attempt is logged. Handing work to a teammate still works from any turn.

Added

  • A first-run wizard. A fresh install opens on a few short steps instead of an empty workspace: pick the language, pick an AI service from cards (each with a link to where its key is made), paste the key and test it, then pick a model from the ones the service offers. A failed test says what went wrong and what to try next. It then shows what your teammates' computer has to work with (the browser it found, or a download with its size, progress and a mirror in China; Docker; the sandbox for commands) and ends in Chief's thread with three example tasks to try. Every step before the computer check can switch to demo mode instead. Installs set up with environment variables never see it.
  • A settings page, behind the gear in the sidebar: the default model with a way into the AI models dialog (or, in demo mode, a button to connect a real model), the language, which computer teammates get (with why automatic picked the one in use, and a note when a change needs a restart), the browser and where it downloads from, and an About section with the version, the data folder, where the logs go and what it runs on. Settings pinned by environment variables are shown read-only with the variable to change. The setup can be run again from here, keeping the saved key when you pick the same service, and closed half way.
  • Demo mode says so where you work. A thread whose teammate runs the scripted demo model shows a banner under its header (in a group, naming who) with a button to connect a real model, and the model chip reads "Demo mode" instead of the service and stub.
  • Links to a thread. #thread=<id> at the end of the UI's address opens that conversation; a link to one that is gone opens the first. GET /api/summary gives how many teammates are working, how much waits on you and how many routines are on.
  • Ask one teammate in a group. Type @ in a group thread to pick who should answer; only they run a turn, and the chief closes with a dispatch table only when it is named too (named alone, it just answers). For other clients, POST /api/threads/group:…/messages takes an optional mentions list of teammate ids, and an @id written in the text counts the same; display names in the text are not matched. A named id that is not in the group is refused with 400, and so is a non-empty mentions in a direct thread. With no one named, the round is the same as before. Requested in #12.
  • Send a teammate a file (API). A client can upload an image, a text file or a Markdown file (POST /api/uploads, JSON with base64, 8 MB each) and attach up to 8 to a message with attachments. The file is copied into the uploads/ folder of the teammate's workspace, where read_file can open it. A teammate on a model that sees images gets the picture in front of the model on the first turn it meets it, and it stays in view for that turn even when the teammate takes screenshots; later turns carry only its name. Each teammate keeps its own record, so one you ask later in a group still gets the file and the picture. Uploads are served from GET /api/uploads/:id, removed with DELETE, and capped in total by OPENSUPERBOT_UPLOADS_MAX_MB (2048). See docs/attachments.md. Requested in #12.
  • Send files from the app. A paperclip next to the message box, pasting an image, or dragging files onto the conversation attaches them; they upload at once and send with your message, with or without words. In the thread an image is a thumbnail and any other file a strip to download, and a sent file can be removed. The app turns away a file that is too large or of the wrong kind before uploading it, says why an upload failed and lets you try again, and warns when the teammate's model cannot see images. A message that could not be sent goes back into the message box with the reason, where a failed send used to vanish.
  • Send a teammate a PDF. The gateway extracts the text when a PDF is uploaded and puts it beside the document on the teammate's computer (report.pdf and report.pdf.txt, one heading per page), because read_file cannot read a PDF itself. A scan, which has no text, and a document that cannot be parsed are accepted and reported as such, to you in the upload's reply (text: ok, truncated, none or failed) and to the teammate in the conversation. Extraction runs in a separate thread with limits on memory, time (20 seconds), pages (200) and size. CJK radical look-alikes and Latin ligatures in the extracted text are replaced by the real characters, so the text can be searched. This adds one dependency, unpdf, which has no native code.
  • The desktop app (desktop/, Electron 44.9.3). The gateway can run inside the app: it tells the app when it is ready and on which port, shuts down in order when the app asks (routines stop, computers and their Chrome close), downloads the browser with the app's own runtime, and gives commands in the sandbox a node that is the app's runtime. Run from source, nothing changes. The shell starts the gateway, signs its window in without a sign-in link, restarts a crashed gateway, and shows an error page with redacted diagnostics and the log tail when it cannot start. Its window shows only the gateway's UI: other sites open in your browser, the gateway's own pages open in an app window, signed in, other kinds of links are blocked, attachments download to your Downloads folder without overwriting, and pages may only show notifications and write to the clipboard. If port 4747 is taken (a gateway run from source, say) it takes the next free one and keeps it, so webhook addresses stay put; Settings → About shows the port. Closing the window keeps it running, with a menu bar icon (tray on Linux) and a Dock badge for what waits on you; approvals, questions and sign-in requests notify while the window is away; quitting from the app asks first while work or routines are running. It can open when you log in, off unless you tick it on the wizard's last step or in Settings: on macOS as a login item, falling back to a LaunchAgent when the system will not take an unnotarized app (and saying so when you have turned it off in System Settings), on Linux as an autostart entry. When update checks are enabled in Settings (the default), startup makes one GET to GitHub's releases/latest and shows a download link in the menu bar / tray and in Settings → Desktop app when a newer stable version is out; turning it off makes zero requests, and the app never downloads or installs updates automatically. Pages get no Node; the gateway's own page gets the app version, release notice and start-at-login, checked by the app on every call. See docs/desktop.md and desktop/README.md.
  • Mac and Linux installers, release workflow and packaged smoke test. pnpm desktop:package and .github/workflows/release.yml build two macOS .dmgs (Apple silicon and Intel, ad-hoc signed, not notarized) and Linux .deb and .AppImage installers for x64 and arm64, verify packaged builds end to end with scripts/smoke-desktop.ts (pnpm run smoke:desktop: Playwright _electron with chromiumSandbox: true, stepping through demo mode, driving a real browser screenshot and checking that quitting leaves no Chrome or gateway process behind), and publish a GitHub Release with SHA256SUMS.txt. The app carries the gateway with only its production dependencies, outside the asar, and a single SQLite binary for its platform; a dmg is about 135 MB. The AppImage uses the static AppImage runtime, so it opens without FUSE 2 (not installed by default since Ubuntu 22.04), and the gateway strips the AppImage's library, schema and data paths before launching a browser or sandboxed commands. On Ubuntu 24.04+, where AppArmor blocks unprivileged user namespaces by default, the .deb pulls bubblewrap in and installs AppArmor userns profiles for the app, its downloaded browser and bubblewrap; under an AppImage on those systems, the commands switch probes bubblewrap and stays locked with a clear explanation instead of running without a sandbox.

Changed

  • Refined workbench UI and macOS window chrome. The client uses a deeper obsidian zinc surface with hairline borders, consistent inline SVG icons in place of character glyphs, and an inset title bar on macOS so the sidebar, thread header and computer panel meet the window edge. The sidebar groups direct threads and rooms with message timestamps, pins AI models and Settings to a footer bar, and folds into a drawer on narrow windows. Conversations open on a welcome card with starter prompts when empty, show a pill to jump back to the latest message when scrolled up, open screenshots and image attachments in a lightbox, and group composer attachments, @ mentions and send/stop controls into one input card. Dialogs close on Esc from the topmost layer first, and destructive actions ask in an in-app confirmation dialog instead of window.confirm.
  • Teammates have faces instead of emoji. Each avatar is a small coloured shape with a pair of eyes, picked from the teammate's id so it is the same everywhere. It acts out the teammate's state — bobbing while working, hopping when it waits on you, shaking its head when stuck, smiling when done — and holds still when your system asks for reduced motion. The README screenshots are retaken with them.
  • Screenshots are served with X-Content-Type-Options: nosniff, like uploaded files.
  • The README screenshots are retaken on 0.5.0. They show the new name, each teammate's model chip, and a local computer's live screen in the panel. The conversation is the built-in scripted demo.

Fixed

  • Stop works while a teammate is waiting to retry. When a provider answered 429 or 503 and the gateway was waiting before the next try (up to 30 seconds if the provider sent Retry-After), pressing stop did nothing until that wait was over. The wait now ends the moment you stop the turn, and no further request is made. This applies to OpenAI-compatible and Responses connections; Claude connections already behaved this way. Reported in #22.
  • In demo mode, a link followed by Chinese punctuation is opened without the punctuation, and Chinese requests to send, email or reply are held for approval like English ones.
  • Linux ARM64 machines without a preinstalled browser can now find the Chrome for Testing binary (chrome-linux-arm64/chrome) downloaded by playwright-core.

Full changelog: v0.5.0...v0.6.0