Changelog #0005 · June 11, 2026

Trusted devices, developer tooling, and reliability upgrades

securitytoolingreliabilityperformance

This release focuses on three things: keeping your account secure without getting in your way, getting developers set up faster, and making the platform steadier and easier to navigate.

Trusted device authentication

Signing in to Salus is now both more secure and more convenient. You can mark a device as trusted during two-factor authentication, so Salus remembers it and stops prompting you for a second factor every time. You keep strong account security, with far less friction on the devices you use every day.

Salus CLI and MCP downloads

Developers can now grab the Salus CLI and MCP tools from a dedicated downloads page. Everything you need to get up and running lives in one place, so setting up your local environment and onboarding new teammates is significantly faster.

Working with your AI of choice just got a lot easier. No longer do you need to leave your Claude Code session to deploy; simply use our CLI/MCP to integrate Claude directly into Salus.

The command menu is more helpful when you’re not sure exactly what you’re looking for. When no matching results are found, it now launches the Conversation Agent automatically, so instead of hitting a dead end you get pointed straight towards an answer. We’ve also smoothed out several navigation flows across the platform, including login handling and homepage redirects.

Better platform performance monitoring

Application performance metrics have been significantly improved, giving your team more accurate insight into the health and reliability of your applications. Better signal means you can trust what you’re seeing and act on it with confidence.

Security enhancements

A number of security improvements landed this month:

Trusted device authentication — remember trusted devices during two-factor authentication, as described above.
Expanded non-root workload support — broader support for running workloads as a non-root user, which is a safer default.
Dependency vulnerability remediation — known vulnerabilities in third-party dependencies patched.
Infrastructure hardening and security updates — ongoing hardening across the underlying platform.

Reliability improvements

We also delivered a range of reliability fixes that make day-to-day work smoother:

Improved login handling — a more dependable sign-in experience.
Better deployment pipeline diagnostics — clearer signal when something in a pipeline needs your attention.
Enhanced database naming consistency — more predictable, consistent naming for your databases.
Improved environment variable onboarding — a smoother path for setting up environment variables.

As always, these changes are live now and require no action on your part. We’d love to hear what you think. Your feedback shapes what we build next.