Changelog

What changed, and when.

62 releases so far. Each entry is the commits between that tag and the one before it — the same list a maintainer reads, not a summary written afterwards.

0.28.3

8 September 2026 latest

Measure the opsmaxx.dev rebuild step like every other one
Load the vault's status when the unlock dialog opens
Send Server services a connectable target, not the Server itself
Recognise a locked vault in the shape it actually arrives in, and reach the writes
Offer the unlock where an on-demand read hits the locked vault
Say what stopped the sweep, wherever the sweep is what is missing
Rebuild opsmaxx.dev when a release is published (#20)
Support accounts that can move files but not run anything
Show interfaces, their addresses and the resolvers
Let the file browser's path be typed
Show per-core CPU, the memory breakdown, and the detected distribution
Show the parent directory as `..` in the file browser
Report the disk figure df reports, and say which filesystem

0.28.2

8 September 2026

Fix three things a person hit while trying to use the app
Send the jump chain with the reads that are asked for, and type it so it cannot
Land the certificate's trust setting, or say exactly how to finish it
Stop an unchanged reconfigure from abandoning the sweep in flight
Make the operation tree actually select an operation

0.28.1

8 September 2026

Fix rename fallout in tests: fixture-tied literals the substitution touched
Revert line endings to LF and restore corrupted sidecar binary
Fix repo links to point at the real OpsMaxx/ShellPilot location
Rebrand ShellPilot to OpsMaxx

0.27.0

8 September 2026

Let the HTTP client add, switch and edit an API from the main pane
Say what is stopping the sweep, and offer the unlock where it is stopping
Resolve credentials and transport for the four on-demand host reads
Bound the CI-contention load so it cannot outlive its script

0.26.0

8 September 2026

Add the fleet-wide drift question

0.25.0

8 September 2026

Add image listing and per-host configuration drift

0.24.0

7 September 2026

Group containers by compose project
Let an agent read alerts that have already fired
Let an agent ask what it is allowed to do
Add container control and backup health
Let an agent read the fleet inventory in one call
Let an agent read a container's logs
Let an agent read containers
Show the operation tree in the HTTP client
Give the HTTP client the layout it was built for
Fix three concrete faults in the HTTP client
Tell the truth about an untrusted certificate

0.23.0

7 September 2026

Close the remaining traffic-inspector gaps
Keep the contexts when the current one cannot be reached
Make an unmeasured disk null rather than 0%
Add this machine to live metrics and the Files view
Stop reporting non-HTTPS tunnels as certificate pinning
Close four edge cases in the traffic inspector
Read posture and drift for this machine, without the sweep
Add an HTTPS traffic inspector
Extend the local target to Kubernetes, compose and cron
Let Docker, Kubernetes, cron and host facts target this machine
Open a scratch request on the path its URL names
Cover the HTTP client's transport
Add the HTTP client view
Send HTTP requests from main, optionally through a server
Wait on the condition, not on a turn count, in the process supervisor tests

0.22.3

7 September 2026

Stop a placeholder impersonating a stored password

0.22.2

7 September 2026

Let Settings, AI & MCP and the command palette scroll

0.22.1

7 September 2026

Fix three things visible in the shipped 0.22.0 build

0.22.0

7 September 2026

Put the data first, and give the app one type scale
One dialog, one empty state, one destructive treatment
Let somebody check a connection before saving it
Stop warning a new user about a backup of nothing
Let somebody compare the tiers, and confirm the emergency stop
Make an audit row able to reconstruct the event
Stop offering an authentication method the build reinterprets
Send the approval modal the four facts it was rendering as absences
Move the three writes off the read surface, and stop amber meaning "second host"
Show that a wide table has more to the right
Say when the fleet is muted
Calibrate friction on blast radius, not on how frightening the verb sounds
Ask a first-run user for one thing, and defer the other six
Stop pointing a new user at a sidebar with nothing in it
Say which failure it was, and stop offering the button that cannot help
Never render two selectable rows with the same label
Stop a type toggle carrying the previous type's port, and name the right database
Merge origin/main into the criticals branch
Tell the operator what an agent is asking for, and that they answered
Split the fleet destination by what a tab does to the server
Do not create an unrecoverable vault behind a dialog that says "unlock"
Hide the bearer token, and stop claiming it was already hidden
Split the accent into a fill and an ink, and lift the ramp to AA
Give the name "Read Only" to a tier that is read only
Stop deriving a hostname from a string that did not parse

0.21.0

6 September 2026

Ask the wave's own hosts whether their nodes came back
Read the dump config's mode with a fallback that actually falls back
Say that a chain is one node, before somebody finds out the hard way
Check the stage gate the approval was given for
Chain a node's maintenance, and stop the gate passing a broken node
Roll a compose service back, using the backup the host already had
Count how much a host is complaining, and never read silence as calm
Say whether the logs are being trimmed, and what the journal's ceiling is
Dump MongoDB, without the password on the command line
Search the journal across hosts, and stop the spelling deciding the answer
Offer the restart where the failure is, and fix a nonce that collided
Stop a test depending on the machine it runs on

0.20.0

6 September 2026

Send the failed-unit jump to the part of the log that explains it
Grow a logical volume, and refuse every way of making one smaller
Refuse podman's compose provider, because it cannot be read safely
Record every installed package, and stop deferring the size question
Read filesystems on the BSDs this build says it supports
Record what the podman and RPM measurements settled
Measure podman and the RPM kernel path, and fix what they found
Check the allocatable read against a cluster it was not written for
Ask whether a timer's job worked, not just when it is due
Read every filesystem, and say how many were not one
Say which kernel is running against which are installed
Say what each node has promised, and check it against the scheduler
Stop the capacity row claiming two more things that shipped
Correct the two capacity rows the last commit said it had corrected
Let the panel pick a vault entry, and give it a vault that has no values
Write one .env variable from the vault, without the value passing a window
Ask the two questions netd cannot, and refuse the third by name
Probe the tunnel from inside it, and show the peers the sum was hiding
Read each peer's own counters, and keep the keys off the agent's side
Wire the .ovpn edit, and correct the caution that stopped it
Sample database size on a cadence, at a price worth paying
Say why the .ovpn edit has no button yet
Put the engine upgrade on screen, and split it where the guard said
Read the growth series back, so the forecaster is reachable
Record the size where the read already happens
Decide which size number may be plotted, and refuse the other one
Forecast bytes with a rule that has a scale, and keep the rate
Edit an .ovpn without ever showing the key
Upgrade the engine, and leave the one check this cannot verify to a person
Wire the operator's drift watch, and re-check it where it is run
Let an operator choose a drift watch, behind four gates
Rank the estate by trouble, and keep the hosts that refused in the list
Ask the bastion graph what a key opens, not just what a reboot breaks
Export the access review, with its gaps in the same file
Record why the kernel row stopped at the measurement
List the packages behind the security count, and the three numbers for it
Read a scanner if the host has one, and never print zero as safe
Grade a build by what a Dockerfile is, and leave pull alone
Print what compose said about the file, not what we said about ourselves
Give the review a button, and print what it could not see
Call the eleven parsers item 39 shipped
Actually put networks in the preview they were built for
Put the health log on screen, redacted where the reader is
Read the health log, and stop the status word from being the whole answer
Restart a service by naming its containers, and say what that will not do
Ask which containers hold a network, not which are running
List what nothing references, and say why that is not a delete list
Point rollout status at where it actually shipped
Ask whether the add-on runs, not whether the rollout finished
Say what deleting a claim would do, since the volume will not
Show the image a revision actually is, not the label it inherited
List what has finished and is still there, dated from what exists
Read what a kubeconfig can actually do, minus what everyone can
Tell a budget guarding nothing from one at its limit
Tell an HPA that cannot measure from one measuring zero
Compare what workloads ask for to what nodes can give, and read the claims
Read node conditions, where False is good three times out of four
Show what sudo grants, keeping "not asked" apart from "could not read"
Gate the sudoers read on the consent, in main
Read sudoers off the host, skipping what sudo itself skips
Put the sudoers read behind its own consent, off by default
Ask MySQL which statements scan, and delete a verdict that already existed
Return the session holding the lock, in the query the app actually runs
Let somebody add the watch the alert depends on
Poll for restarting pods, only where the operator said to look
Wire the per-mount read to the probe, and test the wire
Read every filesystem, not just the one mounted on /
Prove the helm parse against helm
Key a crashloop on the cluster, not on whoever holds the kubeconfig
Learn what a crashlooping pod actually reports, from one that was
Ask three more engines what they are actually doing
Show the session holding the lock, which the old read never returned
Read what sudo actually grants, instead of guessing from a group list
Give database dumps the retention they never had
Push a file where the approval covers the bytes, not a description of them
Read the two things the readiness report needed, and show it
Say whether a cluster upgrade is safe to start, and leave the upgrade alone
Manage an account without ever putting a password in a step
Install exactly this package, and say so per manager
Let an operator go quiet on purpose, without a second way to be silent
Let an operator write the undo down while they still know it
Show what the compose file says, not just what it is running
Pull the one service that changed, not all twelve
Watch the certificates that stop a Kubernetes cluster dead
Separate the accounts that are software from the ones that are people
Find the keys nobody is using, without calling a quiet server stale
Let an agent ask where a server is heading, not just where it is
Store the inode number the probe has been measuring all along
Tell the operator a VPN certificate is expiring, before the connect fails
Carry crl-verify through an import, instead of dropping revocation
Alert when a VPN is down, and separately when it is up and silent
Connect the failed-unit list to the log tail it was written for
Make a service action a typed step, not a line somebody typed
Give the job engine the surface it shipped without
Stop reading "logind would not answer" as "logind said no"
Correct three roadmap lines that outlived what they describe
Give the approval log a word for the write that can lock you out
Let a person answer the compose panel's confirmation, not the panel
Stop grading a statement, or a command, by the word in front of it
Alert when there is no backup, which item 5 finally made possible

0.19.1

5 September 2026

Let the unit editor be used, with the file on screen before it lands

47 earlier releases are on GitHub.

See all 62 releases