Add howl-anderson/agentsilex#64
Open
shreyas-lyzr wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds AgentSilex by @howl-anderson to the registry.
Repo: https://github.com/howl-anderson/agentsilex
Category: developer-tools
Tags: agent-framework, litellm, multi-agent, tool-calling, mcp, streaming, opentelemetry, python, hackable, minimal
AgentSilex is a transparent, minimal, and hackable Python agent framework (~300 lines of core code) built on LiteLLM for universal LLM support. It supports tool calling, multi-agent handoffs, MCP client, streaming, OpenTelemetry observability, and a built-in evaluation framework — with no magic and no hidden complexity.
Note on CI: A companion PR adding
agent.yaml+SOUL.mdto the upstream repo has been opened at howl-anderson/agentsilex#1. The registry CI check for those files will pass once that PR is merged. Both PRs are open simultaneously per the standard GAP submission flow.