jomcgi.dev / ember / agents

One microVM per agent session.

Killed on idle, rebuilt from disk or S3 on resume.

2.5 ms VM resume·20 s idle before the VM is destroyed·0 real credentials inside
scroll ▼
agent sessionvm off
did last night's chart bump deploy?
vm awake · 2.5 ms
clone jomcgi/homelab · full history
Checking ArgoCD and the chart versions.
creds attached outside the vm
Yes. The chart moved and the rollout is healthy.
idle 20 s · vm destroyed · disk kept
+2 days · workspace in s3
add a regression test for that fix
restored on new node · --resume
Picking up where we left off.
control planeelixir/otpbrick-2 · firecracker nodenodedgo daemonsession vmoffno network card · one channel to the hostnode scratch · nvmebase memfile · sharedworkspace.img · yoursegress sidecarholds the real secretsBearer <placeholder>Bearer ●●●●●●●● · realapi.anthropic.comtls ends at sidecargithub.comclone + pushobject storebase/ snapshotssession-workspace/<lineage> · deleted after 7 daysnew nodefresh vm--resume · intactgRPCload · 2.5 mspatchvsockswap in the real headerclone · token attachedretire → exportrestore
lifecycle data in flight credentialed egress durable, to and from s3

One microVM per agent session.

Killed on idle, rebuilt from disk or S3 on resume. Credentials stay outside the VM.

  1. 01 · wake: vm awake · 2.5 ms, one shared base snapshot, volume patched while paused
  2. 02 · hydrate: clone jomcgi/homelab through the egress sidecar
  3. 03 · creds: real credentials stay outside the vm
  4. 04 · park: idle 20 s, vm destroyed, disk kept
  5. 05 · resume: workspace in s3, restored on new node

Where a session lives

guest ram
disposable · rebuilt in 2.5 ms · never snapshotted
node scratch
shared base memfiles + workspace.img · what --resume reads
durable storage
retired workspaces · survives the machine · deleted after 7 days

Keep going