agentUniverse
Build domain-aware multi-agent applications with configurable collaboration patterns.
- Source repo
- agentuniverse-ai/agentUniverse
- Stars
- ★ 2.4k
- Last updated
- 12d ago
- License
- Apache-2.0
- Primary language
- Python
- FA score
- 30/100 · Major gaps
At a glance
- How it runs
- Works with
- Universal · cross-platformOpenAI API · Claude API
- Cost
- Free software; you pay for model usage
- Setup effort
- Medium · a few setup steps
- You'll need
- Typical use
- A financial-research team breaking event interpretation or industry analysis into planning, execution, expression, and review can use the PEER pattern.
- Not a fit if
- Users wanting a zero-config out-of-the-box tool; you must write config files and supply model keys
- Teams needing documented production deployment, auth, or pricing; the material does not cover these
- Source review
- 30/100 · Major gaps 8 safety controls not found
What does this agent do, and when should you use it?
agentUniverse is a Python framework for building LLM-powered single-agent and multi-agent applications. Its named collaboration components include PEER—Plan, Execute, Express, Review—and DOE—Data-fining, Opinion-inject, Express; developers can also customize and orchestrate additional patterns. The framework covers domain prompts, knowledge construction and management, tools, knowledge bases, RAG, memory, prompt management, and performance evaluation in the agent-building process. Model integrations are configured for the listed families from providers including Qwen, DeepSeek, OpenAI, Claude, Gemini, and Llama. It also offers a visual agentic-workflow platform built with magent-ui and observability based on OpenTelemetry.
A developer installs the framework with pip install agentUniverse, then selects an LLM in agent configuration. For the documented DeepSeek example, they set DEEPSEEK_API_KEY in custom_key.toml and set llm_model to default_deepseek_llm. An application can assign a complex task across PEER roles—Plan, Execute, Express, and Review—or use the DOE roles—Data-fining, Opinion-inject, and Express—for data-intensive work that incorporates expert opinion. The framework can incorporate tools, knowledge bases, RAG, memory, and domain prompts into an agent flow, and documents using and publishing MCP Servers. For visual workflow authoring, developers install magent-ui ruamel.yaml and run the sample product_application.py.
- A financial-research team breaking event interpretation or industry analysis into planning, execution, expression, and review can use the PEER pattern.
- A team producing financial-report-style output from data while incorporating expert opinion can use the DOE pattern.
- A developer prototyping a legal-advice workflow can use the Legal Advice Agent v2 example.
- A developer building a Python code generation and execution workflow can use the corresponding sample application.
- A team that needs a multi-turn discussion among multiple agents can use the Discussion Group example.
- A developer who prefers canvas-based workflow construction can use the visual platform jointly developed with difizen's magent.
How do you install or deploy this agent?
Python 3.10+ is required. Install the framework with pip install agentUniverse. For the visual workflow platform, additionally run pip install magent-ui ruamel.yaml. For the documented DeepSeek setup, set DEEPSEEK_API_KEY in custom_key.toml.
How do you use this agent?
Start with the documented “Run the first example” tutorial. For a standard application, begin from examples/sample_standard_app and select a model in the agent configuration; the DeepSeek example uses llm_model: default_deepseek_llm. To launch the visual platform sample, run examples/sample_apps/workflow_agent_app/bootstrap/platform/product_application.py.
What are this agent's strengths and limitations?
- Includes two named collaboration patterns: PEER for complex reasoning and analysis, and DOE for data-intensive tasks that incorporate expert opinion.
- Lists configurable integrations across multiple model providers and families, including OpenAI, Claude, DeepSeek, Qwen, and Gemini.
- Supports domain prompts plus knowledge construction and management for bringing domain SOPs and expertise into agent workflows.
- Provides OpenTelemetry-based lifecycle observability for agents, LLMs, and tools.
- Offers both a Python framework path and a magent-ui-integrated visual workflow platform.
- The supplied material does not include the exact command for running the first example; that detail is delegated to a linked tutorial.
- Each model provider requires its own credentials and configuration; only the DeepSeek
DEEPSEEK_API_KEYexample is explicit in the supplied material. - The visual workflow platform adds
magent-uiandruamel.yamlas dependencies. - PEER and DOE are the collaboration patterns explicitly stated as currently available; additional patterns are described only as forthcoming.
- The supplied material does not document a production deployment topology, resource requirements, authentication model, or model-call pricing.
How does this agent compare with similar options?
The supplied material cites PEER research that compares PEER with BabyAGI. It states that PEER had higher average scores across seven evaluation dimensions and reports 83% accuracy with GPT-3.5 Turbo (16k) and 81% with GPT-4. This is research evaluation evidence, not a substitute for testing an intended workload.
Key facts side by side with the most closely related agents.
| Agent | Source review | Form / cost | Stars | Updated | Language | Full support on |
|---|---|---|---|---|---|---|
| agentUniverse This agent | 30 · Major gaps | Library / SDKFree + model costs | ★ 2.4k | 12d ago | Python | OpenAI API · Claude API |
| Inkeep Agents | 45 · Major gaps | Web appFreemium | ★ 1.5k | 1d ago | TypeScript | — |
| Microsoft Agent Framework | 49 · Major gaps | Library / SDKFree + model costs | ★ 15k | today | Python | OpenAI API |
| OpenAI Agents SDK | 64 · Some gaps | Library / SDKFree + model costs | ★ 31k | 1d ago | Python | OpenAI API |
How does FollowAgents rate this agent?
Why each dimension lost points
Evidence shows: The repository provides no documentation on permission model, user confirmation, data flow transparency, sensitive data handling, dependency security audit, external effect control, rollback mechanism, or source attribution. All trust criteria are unsupported, hence score 0.
Evidence shows: README and pyproject.toml are consistent in name, version, and license, so self-consistency scores 2. Dependency availability: pyproject.toml lists many dependencies but no lock file or version range verification, so score 1. Failure messages: No documentation on error handling or failure messages, so score 0.
Evidence shows: README clearly identifies target audience (developers and enterprises) and typical scenarios (finance, legal), so audience and scenarios score 2. Capability boundaries: PEER and DOE patterns are described but no explicit limitations, so score 1. Trigger precision: No trigger mechanism or precise conditions documented, so score 0. Environment fit: Python version and OS requirements provided, but no full deployment guide, so score 1.
Evidence shows: README provides clear table of contents and documentation links, so information architecture scores 2. Install notes: pip install command provided, score 2. Naming stability: Version defined in pyproject.toml but no naming convention doc, score 1. Examples and FAQ: Multiple sample apps provided but no FAQ, score 2. Known limitations: None mentioned, score 0. License: Full Apache-2.0 license text provided, score 3. Versioning and changelog: Version number provided but no changelog, score 1. Maintenance responsibility: Maintainer emails and Discord link provided, score 2.
Evidence shows: Output usability: Example code shows how to get output but no output format documentation, score 1. Marginal value: Framework offers multi-agent collaboration patterns with unique value, score 2. Cost-benefit: No performance or cost analysis, score 1.
Evidence shows: Claim traceability: README cites PEER paper but no sources for other claims, score 1. Cross-source corroboration: Paper link and commercial product link provided but no independent verification, score 1. Fact-inference separation: Documentation mixes facts and inferences without clear distinction, score 1.
- Not found in source: least-privilege scopingGrant only what the task needs: a dedicated account or read-only token, scoped to specific directories and repos.
- Not found in source: confirmation before actingTurn on (or add) a confirmation step before it acts, and try it in a sandbox or test environment before real data.
- Not found in source: data-flow disclosureWatch which external services it contacts (proxy or firewall logs) and keep sensitive data out until you know where it goes.
- Not found in source: sensitive-data handlingUse dedicated, low-privilege, revocable API keys — never production credentials — and keep secrets out of logs.
- Not found in source: dependency securityPin versions and run a dependency audit (npm audit, pip-audit) before installing; prefer running it in a container.
- Not found in source: disclosed external effectsEstablish which external systems it writes to, sends to or changes, and verify with test accounts or repos before production.
- Not found in source: rollback or recovery pathBack up first, or work on a git branch or snapshot, so its changes can be undone.
- Not found in source: verifiable attributionInstall from the official repo or registry and check the publisher and URL to avoid look-alike packages.
- No permission model or user confirmation mechanism provided; assess security risks before deployment.
- Dependencies are not pinned, posing supply chain risks; consider using a lock file.
- No known limitations or troubleshooting guide; use with caution in production.
Recent releases
Latest entries from the project's GitHub Releases. Notes are quoted from upstream as written, not rewritten or tested by FollowAgents.
-
Release notes excerpt
[0.0.19] - 2025-11-17 Added - Added AWS Bedrock model support - Added ollama embedding component support - Added jina rerank component support - Added vector database component support - Faiss vector database support - Qdrant vector database support - Added a batch of new Reader data loading components - Added Notion, GoogleDoc, Confluence cloud document loading components - Added file format support for epub, rar, sevenzip, zip, xlsx - Added text extraction components for images and PDF files based on PaddleOCR …View on GitHub ↗ -
Release notes excerpt
[0.0.18] - 2025-07-10 Added - Added observability capabilities for agent applications based on the OTel protocol Established observation standards for aU agent applications based on OTel (OpenTelemetry) protocol. Comprehensive metrics and traces (including token consumption, latency, success rate, etc.) are collected across key components such as agents, LLMs, and tools. The implementation supports integration with mainstream observability frameworks including SigNoz, Jaeger, and Prometheus, enabling full lifecycle observability for agents. …View on GitHub ↗ -
Release notes excerpt
[0.0.17] - 2025-05-22 Added - MCP Integration & Publishing Capabilities Enables rapid integration with MCPServer for agent, and allows publishing tools/toolkits from aU as MCPServer services - Toolkit Capabilities Supports categorized management of tools and configuration for agent - Knowledge Reader Components - Added Yuque document loading component - Added async_execute method to base tool class, enabling asynchronous tool invocation - Added custom plugin extensions for trace collection processing - Added configurations for the complete Qwen3 series model Changed …View on GitHub ↗
FAQ
Am I locked into one model provider?
What credentials are documented for DeepSeek?
DEEPSEEK_API_KEY in custom_key.toml, then set llm_model to default_deepseek_llm in the agent configuration.