devctl is now zeus: installable, colorful, organized, self-explanatory, and blessed with completions that do not summon Python every time you press TAB.
Zsh, Bash, and Fish get compiled completion scripts. Pressing TAB is now a useful action instead of a tiny act of faith.
The command tree is baked into the shell script, while environment names come from a local cache refreshed by normal fleet reads. No Python startup. No network round trip. No awkward pause where everyone wonders if the laptop has died.
$ zeus env st⇥ status
The old fleet table had all the visual urgency of a tax form. Zeus makes state, failures, and next actions scannable.
$ devctl env ls ENV STATE DEPLOYMENT STALE NOTE inq-547 running ready 0 inq-548 error ready 1 inq-549 sleeping ready 0 Everything looks equally important. Good luck, brave reader.
$ zeus env ls ENV STATE DEPLOYMENT NOTE inq-547 ● running ready healthy inq-548 ● error stale app build failed → zeus env logs inq-548 app inq-549 ◌ sleeping ready wakes on access 2 ready 1 needs you
Color is not decoration here. It is hierarchy. Red rows explain themselves; amber points to drift; cyan keeps the calm things calm. NO_COLOR and --color remain available for scripts and people who fear joy.
Operations now follow themselves to completion, streaming useful progress as it happens. Below: an actual 10m44s environment creation, condensed so nobody has to watch paint compile.
Every operation-starting command follows by default. Use --no-wait when a script should fire and return. Pressing Ctrl-C only detaches—the work keeps going—and zeus env watch <env> drops you right back into the action.
INQ-532 taught the thunder department that an error should name what failed, whose problem it is, and what to do next. A scavenger hunt is not observability.
lambda slice failed (build dev-platform-deploy-lambda: f5d5dd7f-064d-49b2-be95-afa6ff8f0392); see CloudWatch A UUID, a vague destination, and approximately 10,000 lines of emotional support.
sapiens-lambda — build failed (your code) fix your branch, or point the environment at another one next: zeus env status inq-532 diagnosis: CustomMakeBuilder path resolution failed stored: constituent / lambda-build shown: your code / build
When a console session changes an environment but Git does not know yet, Zeus says exactly what is stranded—and keeps saying it before a reset can turn “I definitely made that migration” into an oral tradition.
inq-366: this session APPLIED 1 migration(s) migrations/sapiens/1726661234567_add_widget uncommitted in …/sapiens-hasura: ?? migrations/sapiens/1726661234567_add_widget/ The SQL is already in the environment; the files are only here. Until they are pushed, a fork reset can delete the database half. $ git add migrations metadata && git commit && git push ⚠ FleetView now flags inq-366 until the next deploy includes it.
Lightning is fast. Zeus is faster baby!
Measured replay: parser time fell from 3.5s to 0.2s. The end-to-end target is about half a second. We don't want to keep you waiting
Measured replay · thunder approved
A fresh environment used to be a coffee break. Now it is barely enough time to explain why the meeting could have been a Slack message.
Environment creation dropped from about 12 minutes to 6.5 minutes. Zeus is not running away from responsibility. He is running directly at your ready environment.
5½ minutes returned to the mortal realm
Run each tool with no arguments. One hands you a list of mysterious filing cabinets. The other explains the building.
usage: devctl [-h] [--api-url API_URL]
[--region REGION] [--json]
{env,platform,preview,dev-db,
users,doctor} ...
positional arguments:
env environments: create/ls/status/
source/reconcile/wake/sleep/
reset-fork/replay-clone/preview/
hasura-console/history/destroy
platform fleet-wide operations: capacity,
replay, backfills
preview deprecated: use devctl env preview
dev-db
users
doctor pre-release check
optional arguments:
-h, --help
--api-url API_URL
--region REGION
--json
zeus · operate the dev platform SHELL SETUP completion Print the compiled completion script NOUNS env Create environments, follow them, point them at sources, open them. db The dev-db box every fork is cloned from. user Accounts in the platform's Cognito pool. platform Fleet capacity and control-plane deploys. doctor Can this account run an environment now? Global options include --json, --quiet, --verbose, --color, --no-wait, --timeout, --yes, and --version.
Four nouns—env, db, user, platform—plus doctor. Duplicate aliases disappeared. Environment database actions became env fork …. reconcile --force became sync --rebuild. Now you can understand what we're on about!
zeus operates the platform. make builds the working tree.No more remembering which AWS operation is secretly a Make target. Zeus runs the prerequisite builds it needs, shows the diff, applies the safety rails, and then operates the platform. Make can return to its natural habitat: checks, tests, and builds.
No more “which repo am I in?” archaeology before checking an environment.
make install links bin/zeus into ~/.local/bin.zeus --version tells you the checkout, branch, and commit actually running.~/code/sapiens-app $ zeus env status inq-547 ● running · ready 4/4 slices deployed database fork ready ~/Desktop $ zeus doctor ✓ credentials ✓ control API ✓ fleet capacity ready to create an environment Somewhere deeply suspicious $ zeus --version dev-platform @ main (b93bcb0)
Zeus does not merely rename devctl. It makes the platform readable, discoverable, scriptable, safer to operate—and, against all odds, delightful to type.