Repository navigation
Release v0.3.0
Wysebee Desktop 0.3.0
Install
- macOS: download
Wysebee-0.3.0.dmg, open it, and drag Wysebee into Applications. - Windows: download
Wysebee-0.3.0-setup.exeand run it. It installs for your user only, with no admin prompt.
Upgrading keeps your agents, tasks, tools, skills and settings. Before changing anything, the app saves a copy of your database next to the original (wysebee.db.v5.bak).
The browser extension hasn't changed in this release, so there's nothing to update in Chrome, Edge or Brave.
What's new
Docker tools that run in your own containers
Two new tool types run commands in a Docker container you already have, such as a database or a dev environment:
- Docker Shell: the agent writes its own commands and reads and writes files in the container.
- Docker Command: you write the command, and
{placeholders}are filled in from the agent's values.
You pick the container from a list when you create the tool. You can also browse the container to choose the working directory, or to insert a file path into a command. Wysebee never creates, starts or stops your containers. If a container is stopped, the tool says so.
Browser access for every agent
- Every agent now has browser access by default.
- When you create an agent, you choose which browser it uses (Chrome, Edge or Brave), or skip and choose later.
- Change it or turn it off on the agent's General tab, under Browser access. Tasks have the same setting.
- If no browser is chosen yet, an agent asked to browse tells you how to set one up.
Try out a tool from its editor
Every tool editor has Try out. It runs the tool as the form currently holds it, including unsaved changes, and saves nothing.
Other changes
- An agent's chat now takes the whole window.
- The General tool group offers HTTP Request and Notification. JSON Response and MCP Server are no longer offered for new tools. Existing tools of those types keep working.
Breaking changes
- Workspaces are gone. Wysebee no longer builds or runs its own containers. On upgrade:
- Each Workspace Shell tool becomes a Docker Shell tool, and each Bash Command tool becomes a Docker Command tool.
- Both point at the container the workspace already ran in (
wysebee_workspace_<name>), starting in/workspace. - An agent connected to a workspace gets a Docker Shell tool for it.
- The containers keep running under Docker's restart policy. Workspace folders and data volumes are left on disk, untouched.
- A tool whose workspace was remote or had been deleted has no container. It isn't offered to agents until you choose one.
- The MCP Server tab is removed. Agents can no longer be reached from claude.ai, ChatGPT, Cursor or other apps, either directly or through an ngrok tunnel. Saved connections and their pairing keys are deleted. Use an agent from its Chat tab instead. (Tools that let an agent call out to an MCP server still work.)
- Remote shells are removed. Probes paired from another computer with a
wbpair1.…string are unpaired, and their keys are deleted. Browser connections are kept.
What leaves your machine
- Less than before. With the MCP Server tab gone, the app no longer listens on any network port, and it never starts ngrok.
- Usage analytics are unchanged, and can still be turned off under Settings → System.