v0.5.0

Highlights

• The engine records every paid data call and the values it returned, so a table cell can be traced back to the call that supplied it.

Fixes

• upsert_skill refuses ., .. and any path outside the skill before writing anything; a reference path can no longer overwrite SKILL.md.
• update_agent lists name and handle in updated after a rename.
• get_agent still answers when part of a coworker cannot be read, and names that part in unavailable instead of returning an empty list.

Upgrade

• Database: nothing to do.
• Engine: adds new tables to its system database on first start (additive). Back up the data directory first; there is no downgrade.

v0.4.1

Fixes

• Fixed a memory leak in the hub: every server-side Supabase client started a token refresh timer that never stopped and kept the whole request in memory. Long-running hubs grew by hundreds of MB per hour until they ran out of memory. Upgrade recommended.
• Chat: no extra margin above a heading at the top of a message bubble.

Upgrade

• Nothing to do: pull the new images.

v0.4.0

Highlights

• Subscription CLIs follow the release: Claude Code runs on the binary shipped with the Agent SDK and Codex is pinned, reinstalled only when its version drifts.
• The models each CLI says it serves show up in the UI, and the model picker locks the ones your Codex account cannot use.
• Notifications get an entry in the workspace menu.

Fixes

• A Codex run that fails on a model refused by the account ends with Codex's message instead of spinning forever.
• A failed run keeps the provider's error sentence instead of [object Object].
• Connecting Codex reads the account's models before adopting the default one.
• Reopening an invitation link already accepted takes the member back to their workspace.
• The workspace assistant shows a single shortcuts card per message.
• The chat loader and the step group have the same size.
• Facebook Pages: tools that need a permission Meta no longer grants are removed.

Security

• Next.js 16.4.4 (remote code execution fixes) and a sweep of vulnerable dependencies (hono, zod, Tiptap, next-mdx-remote 6, ws, node-forge and more). Upgrade recommended.

Upgrade

• Nothing to do: pull the new images.
• Self-hosting on supabase.com now requires a custom SMTP server: the default mailer sends the sign-in email without its code. The check command now reports a missing schema or a wrong secret key, and sign-in RPC errors are written to the logs.

v0.3.0

Highlights

• The engine can now install a prebuilt release: rerun update --artifact <url> --sha256 <hex> --commit <sha> downloads it, checks it, migrates the data directory with the new build, switches current to it and restarts, keeping the previous release beside it. rerun rollback swaps back in a second, and the systemd unit rolls back once on its own if the new build fails to start.
• The engine knows how it is installed (release, git monorepo, or Docker image) and /health reports it, along with the status of the last update.
• Sign-in page: a "Last used" badge marks the method you signed in with last time.

Fixes

• An update that failed (checksum, disk, migration) no longer leaves the engine answering "already updating" until its next restart.
• The browser installer no longer needs pnpm in a release or an image.

Upgrade

• Nothing to do: pull the new images. rerun update inside the image now says so instead of failing.

v0.2.0

Highlights

• Updated model catalog: Claude Sonnet 5.5 and Haiku 5.5, GPT-6.1 Sol and Terra, Gemini 4 Argon and 3.6 Flash, refreshed OpenRouter versions.
• Codex CLI bumped to 0.159.1 on engine install and update.
• New README with illustrated templates and feature walkthroughs.

Upgrade

• Nothing to do: pull the new images.

v0.1.1

Fixes

• The engine image is now published: ghcr.io/rerun-build/rerun-engine:0.1.1 and latest. The v0.1.0 image build ran out of disk space.

Upgrade

• Nothing to do: pull the new images.

v0.1.0

Highlights

• Initial public release of Rerun: AI coworkers on an isometric board, each with its own skills, memory, schedules and connected apps.
• Self-host with Docker Compose on your own Supabase project, cloud or open source.
• Pair your own servers from Settings › Servers with a one-time docker run command.

Upgrade

• Nothing to do: this is the first release. Follow INSTALL.md or the self-host guide to install.