How to deploy bundles and environments
Date-versioned tool bundles and declared execution environments — what they are and how changes roll out.
Bundles are immutable
A bundle is an immutable, date-versioned grouping of tools — for example neoxam.core_20260501, the core bundle with file, search, and web tools. Agents declare the bundle version they use, so their tool surface never changes silently.
Rolling out a correction
- Publish a new dated bundle — existing bundles are never edited in place.
- Update each agent's descriptor to reference the new bundle, via a reviewed Catalog pull request.
- Let evals re-run: bundle changes re-trigger the eval gate on every declaring agent.
- Merge when scores hold; the new version serves within minutes.
Environments
An environment is a declared container template: a network egress policy (unrestricted, limited to a host allowlist, or offline) plus pre-installed packages. The agent's descriptor references its environment, and the whole definition is auditable in the Catalog.
Note
The environment registry is live today as governance metadata; declarative egress enforcement arrives with the V1 Beta, and bundle workflows mature toward GA.
Still stuck?
Tell us what you were trying to do and where it failed — screenshots and run IDs help. A human follows up.