Discover and explore top open-source AI tools and projects—updated daily.
easylink-ai-openAgent runtime core for building AI agents
New!
Top 90.2% on SourcePulse
<2-3 sentences summarising what the project addresses and solves, the target audience, and the benefit.>
easylink-ai-open/agent-runtime provides a standalone, provider-neutral core for AI agent development. It decouples the agent loop, LLM interactions, and tool execution from specific product implementations, offering reusable primitives and extensibility for developers building sophisticated agents.
How It Works
<2-4 sentences on core approach / design (key algorithms, models, data flow, or architectural choices) and why this approach is advantageous or novel.> The runtime manages the core agent loop, context estimation, iteration budgets, collaboration modes, and hooks. It uses neutral data types (Message, Part, LLMRequest/Response) for LLM interactions, abstracting provider specifics via built-in wire converters. This design ensures independence from product applications, communicating solely through neutral runtime data types at its boundaries.
Quick Start & Requirements
uv pip install -e . --python .venv/bin/python (within a Python 3.11 virtual environment).uv for installation, pytest for testing.Highlighted Details
ModelClient, ToolDispatcher, SystemPromptProvider, and CacheStrategy.blocked_tools, blocked_effects) without hardcoding policies.AgentHooks provide lifecycle extension points for context compaction, policy enforcement, and auditing.max_context_tokens and pluggable Compactor strategies (like SummarizingCompactor) for context window utilization.Maintenance & Community
The provided README does not contain specific details regarding notable contributors, sponsorships, community channels (e.g., Discord/Slack), or a public roadmap.
Licensing & Compatibility
Licensed under the Apache License, Version 2.0. This license is permissive and generally suitable for commercial use and integration into closed-source applications.
Limitations & Caveats
Core functionalities like memory, sessions, sandboxing, persistence, and brand policy are explicitly externalized, requiring implementation by the consuming product layer. Default configurations for ToolDispatcher and CacheStrategy are no-ops, necessitating explicit setup. The SummarizingCompactor involves hidden model calls, potentially adding latency or cost.
1 week ago
Inactive
letta-ai