v1.0.1
Agent Manager v1.0.1 upgrades the platform from OpenClaw Manager to a general-purpose Agent management platform. This release adds LiteLLM gateway support and email authentication, and introduces automatic database migration triggered by ROS upgrades. Because this version evolves the database schema, review the upgrade steps before you upgrade an existing service instance.
Release date: 2025-04-27
New features
Platform architecture upgrade: from OpenClaw Manager to a general-purpose Agent management platform
Upgrades the platform from an OpenClaw-only management tool to a general-purpose Agent management platform. Adds a configuration system that associates Agent types (
agent_types) with channel templates by type, which lays the foundation for integrating Agents such as QwenPaw.Adds SandboxSet CRD management, which provides a visual interface for creating, editing, and deleting SandboxSets. The built-in SandboxSet is created automatically during administrator initialization.
Brings the Hermes Agent type under platform management, with Docker configuration and service management files.
Multilingual support (i18n)
Supports switching between Chinese and English across the administrator console, the user console, login and registration, model and channel configuration, and the SandboxSet, version panel, and Skills onboarding pages.
LiteLLM gateway support
Adds the LiteLLM gateway type for model channels, which can coexist with existing OpenAI-compatible channels.
Adds Budget configuration: set quota limits per user or per token, and sync user limits to the LiteLLM gateway.
Email authentication and password management
Adds email registration and email login, along with a complete password reset flow.
Administrator capability enhancements
Enables administrators to create instances directly for users. If the user does not exist, the user is created automatically.
Automatic database migration triggered by ROS upgrades
Introduces the DbMigrateJob mechanism: when a service instance is upgraded, ROS automatically runs the incremental migration scripts in
migrations/versions/<semver>/*.sql, with no manual operations required.Provides built-in idempotency checks and SHA256 content verification based on the
schema_migrationstable to prevent inconsistencies caused by tampered scripts.Supports running database initialization scripts repeatedly and reusing them safely in upgrade scenarios.
E2B sandbox integration
Enables dynamic DNS resolution for the E2B domain, which automatically determines whether to use the public or the private network and replaces the previous static
E2B_IPconfiguration.Writes user configuration as the
nodeuser to/home/nodein the sandbox.Adds a fallback mechanism for E2B API host resolution, which improves availability across network environments.
Instance and runtime experience
Shows the real instance ID instead of the sandbox ID in instance lists and details, which makes reconciliation and troubleshooting easier.
Adds the Starting and Stopping statuses and a health check mechanism for instance recovery.
Engineering and documentation
Adds ESLint strict mode, pre-commit checks, and a development guide for new contributors.
Adds a project documentation index page for easier access to platform documentation.
Improvements
Model and gateway configurations are encrypted uniformly, and configuration fields are separated more clearly.
User session handling is optimized to avoid fetching the user profile repeatedly on initial load.
Instance operation auditing and rollback mechanisms are improved.
Supabase access now prefers a private VPC connection, which reduces cross-network latency and security risks.
Upgrade steps
Before you upgrade an Agent Manager service instance to v1.0.1, note the following:
This version performs database schema evolution: OpenClaw tables are migrated to the general-purpose Agent table schema, for example
openclaw_instances → agent_instances. ROS DbMigrateJob completes the upgrade automatically.If you previously customized the LiteLLM or email service variables in
.env, complete them based on the latest.env.example.
Do not interrupt the ROS stack during the upgrade.
In the Compute Nest console, run Upgrade on the service instance. For instructions, see Upgrade a Compute Nest service instance. Database migration completes automatically as part of the upgrade.