Migrating from OpenEve
What the OpenEve to Assembly Line rename changed, what still works under its old spelling, and what was removed pre-launch.
The product formerly named OpenEve is now Assembly Line. The framework never shipped to external users under the OpenEve name, so the rename was a clean cut, not a compatibility window: every renamed surface below now accepts only its new spelling. There is one permanent exception: the host environment-variable mirror.
If you have an older local checkout or a script written against the OpenEve names, update it to the new spellings; the legacy ones no longer work.
Renamed, no alias
| Surface | Old (no longer works) | New (only) |
|---|---|---|
| Product name | OpenEve | Assembly Line |
| npm scope | @openeve/* | @assemblyline-agents/* |
| Facade package | openeve (unscoped) | @assemblyline-agents/sdk |
| CLI binary | openeve | assembly-line |
| Build artifact dir | .openeve | .assembly-line |
| Hosts inventory | openeve.hosts.json | assembly-line.hosts.json |
| Internal HTTP routes | /openeve/* | /assembly-line/* (legacy paths 404) |
| OAuth callback | /openeve/connections/callback | /assembly-line/connections/callback |
| Scheduler header | x-openeve-scheduler-secret | x-assembly-line-scheduler-secret (legacy header is rejected) |
| Plugin export | openevePlugin | assemblyLinePlugin |
| Provider export | openeveProvider | assemblyLineProvider |
| Telemetry namespace | openeve.* / ai.openeve.* | assembly-line.* / ai.assembly-line.* |
| Docker/VPS labels & names (new resources) | openeve.* / openeve-* | assembly-line.* / assembly-line-* |
A plugin package that still exports only openevePlugin/openeveProvider is
treated as exporting nothing. The CLI and compiler report it as a package
with no contributions. Rename the export to pick it back up.
The one permanent alias: environment variables
Every branded environment variable is still readable under both prefixes, forever:
| New | Legacy | Behavior |
|---|---|---|
ASSEMBLY_LINE_* | OPENEVE_* | Both spellings are mirrored to the same value at env ingestion. The new name wins if both are set; setting both to the same value is fine; setting them to different values fails at startup. |
This is intentional and will not be removed. Existing deployed hosts (for
example a VPS deployment with OPENEVE_ADMIN_TOKEN in its environment) never
need to be touched. Prefer ASSEMBLY_LINE_* in new configuration, but either
spelling works indefinitely.
What never changes
These identifiers were never part of the rename and are permanent:
- Postgres
openeve_*tables and indexes,NNN_openeve_*migration IDs, and theoe_database prefix, the migration ledger is checksum-verified and the physical schema lives on production databases. /var/lib/openeve:/home/openeve, theopeneveOS user, and its sudoers/sshd drop-ins on existing deployed hosts.- Existing container, volume, and network names (
openeve-caddy,openeve-edge,openeve-postgres, per-deploymentopeneve-<slug>*). - The
/workspace/.openevereserved sandbox directory persisted inside deployed sandboxes. - The
openeve-computer-use/v1crypto contexts, renaming them would break all existing device bindings. - The channel event wire value
source: "openeve_state". - Git history, tags, and release notes.
See docs/rename/manifest.md in the repository for the complete, maintained
identifier-by-identifier record (that file lives outside the published docs
site).