What changed
Coolify released stable v4.6.0 on November 2, 2026 (UTC). It adds resource-scoped permissions for team members and API tokens, with read, read sensitive, deploy, write, delete and root levels. Grants can be restricted to selected projects, environments or individual resources; token permissions cannot exceed the owner's. Breaking change: delete operations through REST API and MCP now require the new delete ability or root, not write alone. The release also adds MCP/API management of Cloudflare DNS records, integration tokens and secret managers, changes instance update channels and hardens GitHub Actions, secret responses and Reverb routing.
Why it matters
Coolify is a privileged control plane for servers and deployed workloads. Previously, broad write access exposed a large destructive surface to CI jobs and AI agents. Scoped grants can reduce the blast radius of a leaked or misused token, while the new delete requirement may intentionally break existing automations. Operators must audit tokens and workflows rather than assuming that a successful upgrade preserves every API permission.
Access can now follow the resource rather than the whole team
Administrators can grant viewer, developer, operator or full presets, or configure granular access to projects, environments and resources. Limited users and tokens should see only their permitted inventories, deployments and search results. Revoking a user's access also invalidates dependent tokens. The hierarchy adds explicit delete and root privileges beyond read, read sensitive, deploy and write.
Existing deletion workflows need a permission audit
A write-only token can no longer delete resources, environment variables, storage, backups, scheduled tasks or tags through the API or MCP. Operators should identify integrations that intentionally delete and grant delete only where necessary. Do not solve the upgrade by distributing root tokens indiscriminately. Documentation pages may lag the release: several current API references still describe write-based deletion, so use the tagged v4.6.0 release notes as the version-specific authority.
AI agents get more infrastructure actions, with higher stakes
New MCP tools can manage DNS, integration tokens, Cloudflare tunnels and secret-manager associations. Secret-manager APIs list key names but do not return secret values, according to the release notes. These capabilities make agent workflows more useful but expand the set of actions that warrant explicit approvals, scoped tokens and audit review.
Release and supply-chain operations change
Stable, preview and nightly channels are selectable. CI workflows pin actions to full commit SHAs and a lockfile including repository identity; release credentials are separated by environment. The build process now uses zstd-compressed image layers and requires a compatible Docker Engine. The release removes Windows Docker Desktop support and some moving image tags, so operators relying on old deployment assumptions should review the full changelog.