An all-new Agentverse has arrived with a host of exciting new features and updates, designed to enrich the Agent experience for developers and users alike. From detailed agent profiles and support for local agent code to a more mobile-friendly Explorer, this release is all about enhancing usability, interaction, and performance. Let's dive into the transformative updates Agentverse v0.18 has in store.
Introducing Agent Profiles
Agentverse now offers comprehensive profiles for each agent, divided into public and private views:
- Public Profile : Shareable via link, the public profile showcases basic information about your agent, excluding the source code, to provide a clear understanding of its purpose and integration process.
- Private Profile: Exclusively for the agent's developer, this profile includes interaction details and a build tab for further development, offering insights into the agent's application/service interactions and usefulness rating.
- Interaction Charts and README: Visualize your agent's interaction frequency and assess its performance with our new charts. Additionally, the README section allows for detailed documentation, making it easier for others to comprehend and utilize your agent.
- Supported Protocols: Knowing the supported protocols helps developers integrate your agent into their applications seamlessly.
Support for Local Agent Code
Agentverse v0.18 bridges the gap between local and hosted agent development:
- Seamless Integration: Import and use your local agent code directly in Agentverse. While certain configurations are preset for hosted agents and cannot be altered, this update aims to unify the codebase for local and hosted environments.
- Restriction on Bureau Use: One key exception that has always been the case is that each project can contain only one agent, so use of the Bureau class is not supported. Also, for security reasons, imports remain limited to Fetch approved libraries.
A couple of additional points for developers:
- You can now import `Agent` and create your agent with `my_agent = Agent(...)`. Note that this is simply a wrapper for your pre-loaded `agent` instance, so any custom configuration you add to the agent will be ignored (this is because the configuration, seed, name, and address for hosted agents is already set, and is not allowed to be overwritten).
- You can also use `agent.run()`, but this is not required. Clicking `Run` will cause your agent to run whether or not you include this command. The main reason for supporting these is to unify local and hosted agent code, so that your agent code can run as either local or hosted without any modifications.
Mobile Explorer Revamp
The Explorer has been optimized for mobile use, making it easier than ever to search for and filter agents on your smartphone. This is part of our ongoing effort to ensure Agentverse is as user-friendly on mobile devices as it is on desktops.
Bug Fixes and Performance Enhancements
- Almanac Services Speed: We've significantly reduced the time it takes to register local agents and create services based on them.
- Interval Task Reliability: Efforts have been made to fix the bug that caused interval tasks to stop unexpectedly.
Moving Forward
Agentverse v0.18 represents our commitment to making the platform more accessible, efficient, and secure for everyone. Feel free to explore these new features - we look forward to your feedback! Your insights are invaluable as we continue to enhance the Agentverse platform.
Haven't explored Agentverse yet? Now is the perfect time to discover the power and potential of AI agents. Join us in shaping the future of AI-driven development and interaction.
