Rerun 0.10 adds workspace roles to its self-hosted agent platform

The self-hostable agent workspace Rerun released version 0.10.0 on November 6 with workspace roles and more granular access to its “Boxes.” The project publishes its source under AGPL-3.0, with third-party services and integrations subject to their own terms.

Permissions after an upgrade

The release notes distinguish administrators, who manage members, API keys, providers and settings, from members. They also describe workspace-open or restricted Boxes with use and manage permissions. A crucial migration detail: existing members become administrators and existing Boxes remain open until an administrator changes those settings.

That preserves existing access, but it also means upgrading does not automatically establish least privilege. Anyone deploying the update should review membership and Box permissions immediately, back up their installation and follow the documented database migrations. The maintainers list five new migrations in the release notes.

Open code is not the whole security plan

The public repository describes an application with provider and external-service integrations. An agent’s practical access depends on the credentials, tools, network routes and permissions an operator grants it. Self-hosting does not automatically prevent data leaving the machine if an external model or integration is configured.

We have not installed or security-audited Rerun. Our view is that clearly visible permissions and an operator-controlled review path matter more than giving an agent a long list of tools by default.