Skip to content

v1.1.4

Latest
Latest

Choose a tag to compare

View all tags
@Haohao-end Haohao-end released this 15 Jun 08:54
v1.1.4
b318db3
OpenAgent Logo

OpenAgent v1.1.4

README improvements, sponsor display enhancements, UI/functional fixes, contributor acknowledgments, and better deployment & developer experience.

Sponsored by Atlas Cloud and Bloome

Visit Website · API Docs · 中文文档 · Ask DeepWiki

--- ## Overview OpenAgent `v1.1.4` is a focused documentation, experience, and stability patch release following `v1.1.3`.

This release primarily polishes the README and project presentation, including sponsor display updates (now featuring both Atlas Cloud and Bloome), acknowledgment for Ryan B.'s security contribution, multiple UI fixes, and improvements to the development workflow. It also fixes several issues related to the Sidebar, Store, Agent binding, and dynamic loading to further enhance workspace consistency and reliability.

It is recommended for all users running the v1.1.3 stack in local development, Docker Compose, or self-hosted environments.

Highlights

README & Project Presentation Improvements

  • Updated sponsor section to prominently feature Atlas Cloud and Bloome.
  • Refactored provider ecosystem titles and improved sponsor block structure.
  • Added acknowledgment to Ryan B. for SSRF vulnerability reporting.
  • Optimized ER diagram layout for the upload_file and process_rule tables.
  • Added *.Zone.Identifier to .gitignore (better Windows user experience).

UI & Functional Fixes

  • Fixed duplicate entries in Sidebar Store and improved icon differentiation for MCP/Workflow/Skills.
  • Optimized Agent binding logic to runtime tools and restored proper App layout behavior.
  • Added support for dynamic loading of Recent Conversations.
  • Removed duplicate MCP entries and hardened release tags.
  • Added error handling for the A2A conversation messages endpoint.
  • Force-tracked safe_http_client.py and cleaned up related ignores.
  • Removed outdated Atlas Cloud gpt-5.2 entry while maintaining compatibility.

Deployment & Developer Experience

  • Improved Skills catalog and Store UI synchronization.
  • Enhanced overall code and documentation consistency.

Developer notes

  • When modifying the README, keep sponsor information synchronized between English and Chinese versions.
  • New UI strings should continue to be managed through i18n keys (following v1.1.3 conventions).
  • Before publishing or deploying, run the frontend validation flow: 
    cd ui
npm run type-check
npm run lint
npm run build
Assets 2
Loading