Reference
VM Versioning
How agent VM image versions and protocol numbers work, and how to upgrade.
VM Versioning
Every agent runs a specific version of the CrabGlamp container image. Two numbers matter.
Version vs. protocol
Version (semver, e.g., 0.7.0) — the image build. Tracks every change: tools, fixes, configs.
Protocol (integer, e.g., 3) — the API contract between the web app and the container. Only bumps when the communication layer changes.
cat /opt/crabglamp/version.jsonAgents are frozen
When you create or clone an agent, it gets the current image. That image never changes. Your agent runs the same version for its entire life.
- New features may need a newer image.
- Your agent won’t break when we ship updates.
- Clone to get the latest.
Protocol history
| Protocol | What changed |
|---|---|
| 1 | Original paths: /terminal/, /editor/, /revoke |
| 2 | /_cg/ namespace, two-nginx architecture, customer web hosting |
| 3 | GlampHub support |
Upgrading
No in-place upgrades. Clone your agent → verify → destroy the original.
Files, packages, and configs carry over. The image version, protocol, and agent-specific env vars change.
Feature requirements
| Feature | Needs |
|---|---|
| GlampHub | Protocol 3+ |
| Web hosting | Protocol 2+ |
/_cg/ paths | Protocol 2+ |
Dashboard tells you if a feature needs a newer image.