v1.1.3
OpenAgent v1.1.3
Internationalization foundation, bilingual workspace experience improvements, localized UI copy, language runtime support, and release stability polish.
Sponsored by Atlas Cloud
Overview
OpenAgent v1.1.3 is a focused patch release after v1.1.2.
This release introduces the first structured internationalization (i18n) layer for the OpenAgent frontend. It prepares the product workspace for a better English and Chinese experience, centralizes user-facing copy into locale resources, reduces hard-coded UI text, and improves consistency across common product flows.
It also includes release-cycle stability work around frontend build readiness, Skills catalog packaging, API startup catalog synchronization, and Alembic migration handling for deployment environments.
It is recommended for users running the v1.1.2 stack in local development, Docker Compose, or self-hosted environments.
Highlights
Internationalization foundation
- Added frontend i18n support for the OpenAgent Vue workspace.
- Introduced locale resource organization for user-facing product copy.
- Added bilingual localization groundwork for English and Chinese UI experiences.
- Centralized common labels, actions, placeholders, navigation text, messages, and page copy.
- Prepared frontend pages and components to resolve display text through i18n keys instead of hard-coded strings.
- Added safer fallback behavior so untranslated or missing keys can degrade more gracefully.
Bilingual workspace experience
-
Improved localized copy coverage across core product areas:
- Home assistant
- App workspace
- Workflow builder
- Dataset and document management
- Public apps, tools, and workflow browsing
- Authentication, settings, dialogs, and common UI states
-
Reduced mixed-language UI text in the frontend workspace.
-
Improved consistency for page titles, menu items, buttons, empty states, validation messages, and toast notifications.
-
Prepared the UI for future language expansion beyond the initial English and Chinese coverage.
Language runtime behavior
- Added runtime language resolution support for the frontend application.
- Prepared the app bootstrap flow so localized pages can render through the i18n layer.
- Added support for preserving or reusing the active language during the frontend session.
- Kept the default English experience available while enabling Chinese UI usage.
Release and deployment polish
- Ensured localization resources are included in the frontend build path.
- Kept Vite and Docker build behavior compatible with the new i18n structure.
- Continued release stability cleanup around built-in Skills catalog packaging.
- Improved API startup behavior by syncing the Skills catalog during service initialization.
- Fixed catalog markdown tracking so packaged Skills documentation is included reliably.
- Resolved Alembic migration head split issues that could affect deployment upgrades.
Developer notes
-
New user-facing frontend strings should be added through locale keys instead of being hard-coded in Vue components.
-
When adding or changing UI copy, update both English and Chinese locale resources in the same change whenever possible.
-
Keep fallback copy concise and predictable so partially translated pages remain usable.
-
Before publishing or deploying, run the frontend validation flow:
cd ui npm run type-check npm run lint npm run build -
For Docker-based deployments, rebuild the stack so the updated frontend assets and locale resources are bundled correctly.
Upgrade notes
-
No breaking backend API changes are expected for existing
v1.1.2deployments. -
Self-hosted users should pull the latest code and rebuild frontend assets or Docker images.
-
Deployments using Docker Compose should run the normal rebuild/start flow after updating:
cd docker docker compose up -d --build -
If you maintain custom frontend copy or downstream UI modifications, migrate those strings into the locale resource structure to stay compatible with the new i18n workflow.
Recent commit summary
- Added the first structured frontend internationalization layer.
- Localized and centralized key UI text for English and Chinese experiences.
- Improved workspace copy consistency across common pages and flows.
- Synced the built-in Skills catalog during API startup.
- Ensured Skills catalog markdown files are tracked and packaged correctly.
- Resolved Alembic migration head split issues for deployment stability.