Canyonos v0.1.736

Release notes for v0.1.736

CLI

New

• Added a canyonos upgrade command. If CanyonOS is managed by uv tool, it upgrades using uv tool upgrade canyonos, preserving any existing version constraint and explaining how to override it with uv tool install canyonos@latest. If not managed by uv, it prints the correct reinstall instruction instead.
• The CLI now warns when your installed version is outdated: a short warning if a newer version is available, a stronger warning if your version is no longer supported. These checks use a locally cached, periodically refreshed policy and never block a command, including on network or cache errors. Warnings go to stderr and don't affect structured output like canyonos test --json.

Improved

• CanyonOS-managed Docker containers (Global Controller, Redis, metrics collector, workflows, and agent replicas) are now grouped under a stable, named Docker project/group, distinct from the dashboard stack, so local containers from different projects no longer collide. stop, quit, clean, test and redeploy continue to affect only their own containers.

Fixed

• canyonos test no longer starts the dashboard stack, removing unnecessary image pulls, a long wait for the stack to come up, and a rewrite of your project's .env file.
• Fixed agent manifest validation to require and check the functions declaration for each agent, with clearer error messages for missing or invalid function definitions, duplicate or reserved function names, and names that would shadow built-in types.

Core

New

• Docker containers launched by CanyonOS are now grouped under a stable, named project (matching the current directory), so local runtime containers (Global Controller, Redis, metrics collector, workflow, and agent replicas) are clearly distinguished from the dashboard stack and from containers belonging to other local projects.
• Agent function signatures (names, arguments, and return types) are now declared directly in the main global controller configuration, replacing the separate per-agent .yaml files.

Improved

• stop, quit, clean, redeploy, and failure cleanup now reliably affect only the containers they own, preventing collisions between multiple local projects.
• Build and validation now use the consolidated agent configuration to generate stubs and check agent methods.
• Validation now reports clearer errors when function declarations are missing or when agent methods don't match the configuration.

Fixed

• Projects using the old per-agent .yaml file layout now fail deployment/validation with a clear configuration error instead of being silently accepted or producing confusing errors.

API

No user-facing changes.

Web

No user-facing changes.