OAuth authorization can now limit an access token to a selected team. Integrations can use this team context instead of treating every token as access to all of the user's teams.

Deployments can now run on servers without PHP installed when the application does not need it. PHP-specific preparation and Composer installation steps are skipped when the corresponding tools are unavailable, so deployment scripts can support other application stacks.

Add an integration for your self-hosted GitLab instance and connect its repositories to Deploy Chief. Configure the GitLab application for your instance and provide its HTTPS URL when setting up the connection.

You can now connect more than one application to the same repository, allowing separate deployment configurations for the same codebase. When connecting GitHub, choose which available installation to link to the team.

You can now roll back to an earlier deployment by activating its existing release on your servers. The target release must still be present on the servers; a rollback reuses that release rather than building it again.

You can now start a fresh deployment using the same commit and environment as an earlier deployment. Use Redeploy when you need to run the deployment again without selecting the commit manually.

You can now select YAML syntax highlighting in the Paste tool. Shared YAML configuration is easier to read with highlighting suited to the format.

HTTP checks now also run for monitored IP addresses. You can inspect the HTTP response alongside certificate information when monitoring a host directly by its IP address.

You can now remove a connected DigitalOcean account from Bill.DO using Disconnect in the account settings or reconnect screen. You can connect the account again later.

Managed database cost estimates now account for additional configured storage alongside the database size and node count. This gives you a more complete view of the cost of databases with expanded storage.

HTML pastes now include a preview window. You can inspect the rendered output alongside the source when sharing or reviewing an HTML snippet.

New environments now show a setup checklist with links to configure settings, prepare the .env file, set deployment scripts, and run your first deployment.

Two new utilities let you convert text to HTML entities and decode HTML entities back to text. Use them when preparing text for HTML or inspecting encoded content.

You can now register a passkey and use it to sign in to your Chief Tools account. Choose passkey sign-in on the login page and confirm with your device or password manager.

The Redirect resolver follows a URL's redirects and shows the steps along the way. You can inspect the redirect path and final destination when troubleshooting links.

The Paste tool now has an improved syntax selector for choosing how a shared paste is highlighted. Pick the appropriate language when creating a paste so its contents are easier to read.

HTTP checks now show the response status code. You can also choose how responses in the 400–499 range affect monitored health using the HTTP status preferences: HTTP status 4xx as OK or HTTP status 4xx as error.

The Certificate chain resolver lets you paste a PEM certificate and retrieve its intermediate certificates. You can copy the resolved chain or the certificate together with its chain for use in your TLS configuration.

Link statistics now separate crawler visits from regular clicks. You can inspect crawler activity alongside the click history without automated previews inflating the regular click count.

The Favicon resolver retrieves a site's favicon from its domain name. You can also embed a favicon with an image URL in the form https://favicon.chief.tools/resolve/DOMAIN.