What changed

• Your agents keep their own MCP servers. Integrations are the servers you want everywhere; everything an agent loads by itself now loads beside them in a Storm session:
  • Claude Code: the servers you add with claude mcp add, its plugins’, and a project’s .mcp.json (after Claude Code asks you).
  • Codex: your servers, plugins and ChatGPT apps. Storm no longer rewrites them away, and Codex asks its own question before trusting a workspace’s .codex/ settings, instead of opening on Folder access every time. Storm’s own hook is recorded as trusted, so Codex reviews every other hook itself.
  • OpenCode: your global config and its servers. A repository’s own OpenCode config stays off: it could turn off the question OpenCode asks before each Storm tool.
  • If one of your servers has the same name as an integration, Storm’s copy is renamed storm_<name> so both load.
  • A host that runs code you don’t trust can give its sessions Storm’s servers alone: agent_mcp = "storm-only" in its runtime.toml.
• Notes always open. A note the app hadn’t cached could say That note no longer exists when a relay request merely dropped; now only the server saying so shows that, and anything else offers Retry. Opening a second note while the first loads no longer shows the first.
• Typing in Codex is clean. A Mac host sent keystrokes one byte at a time, so an arrow key could arrive as Esc and then text, and reopening a session answered the terminal’s old questions again into the agent. Both are fixed.
• Integrations and Claude login in Settings are marked Beta.

Upgrade storm-server, storm-runtime on every host, and the apps.

• Codex runs on your Runtime Hosts, with your notes, your integrations and Resume, like Claude Code. Log it in once on each host (see Runtime Hosts): Storm keeps Codex’s login and conversations in its own Codex home, so each session gets only the servers Storm gives it. Each launch opens on Codex’s Folder access screen; choose Open restricted. Codex runs without its own sandbox, which needs something the host’s service forbids, and asks before every Storm tool.
• Cursor and Command Code can be started from the app as terminals. They get no notes or integrations yet: Storm hasn’t been able to check them with a signed-in account.
• Your agents’ plugins work in Storm sessions. A plugin’s local MCP server runs in the session as it would outside Storm, in Claude Code and Codex. A plugin’s remote server (Slack’s, for example) reaches a session only as an integration, so it is never signed in on a host. Storm now lists those under Settings › Integrations › From your plugins. Whatever a session leaves out is named when it starts and in the session’s Details. A host can turn plugin servers off with plugin_mcp = "off" in runtime.toml. See Plugins.
• A Codex plugin that has hooks is turned off in Storm sessions, and so are ChatGPT apps.
• Sign in to a service with your own app. For a service that won’t let Storm register itself, such as Slack, choose ⋯ › Use your own app on the integration (or Storm asks for one): paste the app’s client ID and secret. The secret is stored encrypted on your server. Storm also registers with services that only accept apps holding a secret, and asks for the scopes a service publishes for MCP when you leave them empty.

Upgrade storm-server, storm-runtime on every host, and the apps.

• The Storm app on Windows and Linux. On Windows, install.ps1 installs it with a Start-menu entry (-App), or unzip storm-app-windows-x86_64.zip and run storm.exe. On Linux, install.sh --app installs the storm-app package on Debian and Ubuntu (also sudo apt install storm-app from the Storm repository) and the tarball into your home directory anywhere else. One copy runs at a time, it finds servers on your network, and an image on the clipboard pastes into a session.
• One Claude login for every host. Paste a claude setup-token once in Settings › Claude login, tick the hosts that may use it, and Claude Code sessions there sign in with it. Needs this release’s storm-server and storm-runtime on each host; an older host keeps its own login.
• The installer no longer asks for agent logins. Claude Code signs in from the app, OpenCode from a shell session on the host. The installer’s MCP only option (--mcp) is now offered.
• An MCP server on your own network can be plain http:// when its address is a local IP or localhost. The app warns that its token is sent unencrypted; sign-in with OAuth still needs https://.
• Your edits are safer:
  • text typed while a save is in flight is never dropped;
  • an offline edit to a note deleted elsewhere comes back as a new note instead of disappearing;
  • a note keeps its identity when it is renamed or copied outside Storm;
  • a byte-order mark at the top of a note no longer hides its frontmatter.
• The server is stricter at its edges: an error says only what happened (a 404 means not found), every relay connection caps a message at 16 MiB, attachments are served sandboxed, and a rename that only changes case works.
• Backups link unchanged files to the previous backup instead of copying them, and refuse to run when the vault root looks empty.
• OpenCode sessions keep the workspace’s own instructions file while still ignoring its project configuration.

Upgrade storm-server, storm-runtime on every host, storm-relay if you run one, and the apps.

• The rail’s agent mark animates while an agent is working, instead of showing a count.
• The Agents overview keeps each row’s trailing labels flush right.

• Integrations can be limited to chosen Runtime Hosts — a work integration on the work machine only. A narrowed scope cuts off sessions already running on other hosts.
• Links in a session’s terminal open in your browser. A tap shows the real target first; Cmd/Ctrl-click opens at once.
• New pixel-drawn Notes and Agents icons on the rail.
• storm-runtime mcp-connect ships in the binaries: AI apps connect through it with the configuration the key dialog shows. The installer’s MCP-only option is not offered yet.

v0.9.0 was tagged but never published; this release carries it.

• Relays, finished. The apps reach the server through a relay when its own address does not answer, sign in and stay connected over mobile data, and use agents, integrations, attachments and Add a device away from home. Pairing works through a relay too. A relay can now also run on Cloudflare Workers. Large uploads and downloads cross a relay intact.
• Pairing on your network: the apps list the Storms they find under On this network; pick yours and enter the password. Refused on networks the computer treats as public.
• Firewalls: the installers ask before allowing Storm’s port from your local network, and only from it; storm-server status reports the firewall.
• storm-runtime mcp-connect: one configuration for AI apps that works at home and away, and checks the server’s identity before sending the key.
• Disconnecting a device in the app now signs it out on the server.

• Windows: the server runs as you at logon and the Runtime Host as a Windows Service, both installed by install.ps1.
• Resume reopens an ended Claude Code or OpenCode session’s own conversation on the same host and workspace.
• Sign-in no longer hangs in Firefox-based browsers.
• The phone’s session header is compact, giving the terminal the screen.

• The installer offers a first workspace for a new Runtime Host.
• An empty host shows its workspace folder, with Check again.
• Pasting an image to a host too old to accept it fails at once.

• Sessions take their name from the agent’s own terminal title, with the agent’s logo and a working / idle badge.
• Paste or drop images into a session on desktop, the web and Android — including Gboard’s image keyboard.
• Settings › Terminal: text size, line spacing and padding.
• Android 16’s back gesture goes to the parent page.

v0.6.0 was tagged but never published; this release carries it.

• The interactive installer sets up the server and app, a Runtime Host, or everything, on Linux or macOS, pairs your phone and enrolls the host. Re-run it to upgrade, check status or uninstall.
• The server runs on macOS, as you, with your notes in ~/Storm.

• The Runtime Host runs on a Mac as a LaunchDaemon under its own hidden account, installed from the release or with Homebrew.

• Storm v2: an activity rail for Notes and Agents, one global Settings, and launch straight back to where you were.
• One account. Storm is single-user; older servers keep their oldest owner when they upgrade.
• The loop: start a session from a note, give it one vault it may write to, and see what it wrote — each note it touched links back to the session.
• Integrations: connect MCP servers such as Notion or Linear once; agents use them without ever receiving the credential.