Repository navigation
0.1.5 adds vxl mcp, so coding agents can plan and apply deploys with a digest check, and makes self-healing proposals and quarantines survive a daemon restart. From this release Voxeltron is free to use and distributed as signed binaries.
Changed
- Voxeltron is now free to use and distributed as signed binaries. The source is no longer public. 0.1.4 and earlier remain available under Apache-2.0.
- 0.1.4 servers upgrade by rerunning the installer from voxeltron.dev.
Added
vxl mcp, a stdio MCP server so coding agents can operate Voxeltron. It offers read-only tools (status, apps, logs, deployments, audit and more) by default. With--allow-apply, an agent can plan a deploy fromvoxeltron.yamland then apply exactly that plan:planreturns an id and a digest, andapplyrunsvxl up --expect-digest, which refuses if the manifest or sources changed since the plan. Apply also needs the app name as confirmation. Plans expire after 30 minutes.vxl up --expect-digest DIGESTrefuses to deploy unless the computed plan has that digest.- The audit log records the calling client's user agent on admitted changes, so changes made through
vxl mcpshow which agent made them. [ai] web_tools = falseturns off the operations agent'sweb_searchandhttp_clienttools.[self_healing] diagnosis_timeout_secs(default 120, from 30 to 3600): how long the AI diagnosis attached to a proposal may run.
Security
- A caller without permission on a project gets
PERMISSION_DENIEDfromSwitchDeploymentTraffic, whatever it asked for. Before, a gradual switch request was refused as unimplemented before the permission check. vxl mcpchecks that a manifest's build path stays inside the MCP root on the manifest it actually archived, so a manifest rewritten between the check and the plan cannot plan, or apply through a matching digest, a build from outside the root.
Fixed
- Self-healing proposals and quarantines survive a daemon restart. Before, both were kept only in memory: a restart dropped a proposal waiting for an operator, and the quarantined app was started again, by the boot-time restore of stopped apps and by a fresh restart budget, so it crashed and was proposed again. Now
vxl approvals listshows the same proposal after a restart, approving it runs the rollback, records the approver and runs the recovery check, and expiry still counts from the original request. The daemon database gains two tables,runbook_pending_approvalsandlifecycle_quarantined_deployments, created at startup; no action is needed to upgrade. If the daemon stopped after quarantining an app but before saving its proposal, the restarted daemon raisescrash_quarantineagain and proposes a fresh rollback, so no app stays stopped unnoticed; a saved proposal whose runbook step changed is closed as expired and replaced the same way. A decision on a saved proposal is recorded in the same transaction that removes it, so a proposal is never decided or run twice, and the resumed run gets its original parameters. Only proposals the daemon made itself are kept: a runbook an operator started is still dropped by a restart. With self-healing off, the next start releases saved quarantines and closes saved proposals as timed out. A proposal still pending when you upgrade from an earlier release was never saved; its quarantine was not saved either, so that app is handled as before. - Managed databases start on daemon boot before application restoration, with bounded engine readiness checks and alerts on failure. Database list/get report observed container state, and lifecycle supervision restarts stopped databases within the normal restart budget. Reboot battle tests now verify database containers and pre-reboot Postgres/Redis data.
- A rollback no longer restores the same release it is rolling back. Restarts can relaunch a crashing release as a new deployment, and rolling back to that copy changed nothing. When the previous deployment runs the same release (same image and tag, command, arguments, environment, resources, secret files, writable paths, egress and kernel enforcement),
vxl rollbackrefuses with "no different release to roll back to", and self-healing raisesremediation_no_targetinstead of proposing a rollback. A change to configuration alone, such as the memory limit, still rolls back. - A new deployment of a quarantined app, whether a redeploy or a rollback, gets a fresh restart budget and can raise a new proposal. Before, the quarantine stayed with the app name, so a redeploy under the same name was never restarted or escalated again ("Lifecycle remediation requires operator attention").
- The self-healing diagnosis no longer ends with the internal
[goal-verification] satisfied=... gaps=[...]text or starts withFINAL:. - A
query_logsfailure during a diagnosis now logs the reason. vxl statusandvxl status --jsongive the publichttps://URL, or none, as the app'surl. Before, an app with no public domain showed the container's internal address, which resolves only inside the server's Docker network. That address is noworigin_url.- Under
--json, SSH host key prompts and warnings go to stderr, so stdout is always exactly one JSON document. vxl ps --helpandvxl ls --helpno longer advertise an[app]argument the commands reject.- The built-in runbooks run as written.
- A partial
[ai]table loads, with the default agent name and prompt for any keys it leaves out. - The operations agent lists only tools that have a backend to read from.
- The TUI AI panel shows the model the server actually uses, and offers only commands that work.
vxl mcp'saudit_exportreturns the newest events.vxl deploy --strategyandvxl-admin create-deployment --strategyaccept onlyrollingandrecreate. The daemon's CreateDeployment returnsUNIMPLEMENTEDfor canary andINVALID_ARGUMENTfor an unknown strategy value, and SwitchDeploymentTraffic returnsUNIMPLEMENTEDfor gradual switching, instead of silently running the standard deploy path.- Self-healing proposals waiting for an operator, and quarantined apps, survive a daemon restart or upgrade. After a restart,
vxl approvals listshows the same proposal under the same id, and the quarantined app stays stopped. Expiry still counts from the original request.
Upgrade notes
- Upgrade a 0.1.4 server by rerunning the installer from voxeltron.dev. The installer verifies
SHA256SUMS.minisigwith the release key before installing anything. - The daemon database gains two tables,
runbook_pending_approvalsandlifecycle_quarantined_deployments, created at startup. No action is needed. - The guided move of
vxl bootstrapservers from root to thevoxeltronuser, planned for 0.1.5 in the 0.1.4 notes, is not in this release. Those servers keep running the daemon as root after upgrading. - Each archive's
LICENSEis now the Voxeltron free binary licence, andLICENSE.busyboxis new.
Third-party notice. The Linux voxeltrond and vxl-admin include BusyBox, under the GNU General Public License, version 2 only. Its complete source is attached to this release (busybox_1.36.1-6ubuntu3.1.dsc and its files, with BUSYBOX-SOURCE-README.md); the licence and written offer are in NOTICE-busybox.md and in each archive's THIRD-PARTY-NOTICES.md.