{"repo":"alloy-ex/alloy","free":true,"listed":false,"github":"https://github.com/alloy-ex/alloy","clone":"git clone https://github.com/alloy-ex/alloy.git","description":"Model-agnostic agent harness for Elixir","language":"Elixir","stars":81,"topics":["agent-framework","ai","ai-agents","anthropic","elixir","gemini","genserver","llm","openai","otp"],"license":"MIT","category":"ai-agents","readme_excerpt":"Alloy Minimal, OTP-native agent loop for Elixir. Alloy is the completion-tool-call loop and nothing else. Send messages to any LLM, execute tool calls, loop until done. Swap providers with one line. No opinions on sessions, persistence, memory, scheduling, or UI — those belong in your application, where OTP already gives you the runtime. Alloy is a harness, not a framework. Three runtime dependencies, 9,000 lines — small enough to read in an afternoon, and everything beyond the loop is a recipe built on the primitives, not a subsystem. Why Alloy? Most agent frameworks try to be everything — sessions, memory, RAG, multi-agent orchestration, scheduling, UI. Alloy does one thing well: the agent loop. The BEAM makes the rest cheaper than a framework can: sub-agents are supervised function calls (recipe), MCP servers mount as tools (recipe), parallel tool execution is Task.Supervisor , and crash isolation is just processes. Design Boundary Alloy stays minimal by owning protocol and loop concerns, not application workflows. What belongs in Alloy: - Provider wire-format translation - Tool-call / completion loop mechanics - Normalized message blocks - Opaque provider-owned state such as stored response IDs - Provider response metadata such as citations or server-side tool telemetry What does not belong in Alloy: - Sessions and persistence policy - File storage, indexing, or retrieval workflows - UI rendering for citations, search, or artifacts - Scheduling, background job orchestrati","default_branch":null,"files":null,"tree":[],"storefront":"/r/alloy-ex","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/alloy-ex/alloy/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}