Alternatives
Products that do what AgentLog – a lightweight event bus for AI agents using JSONL logs does
I’ve been experimenting with infrastructure for multi-agent systems. I built a small project called AgentLog. The core idea is very simple, topics are just append-only JSONL files. Agents publish events over HTTP and subscribe to streams using SSE. The system is intentionally single-node and minimal for now. Future ideas I’m exploring: - replayable agent workflows - tracing reasoning across agents - visualizing event timelines - distributed/federated agent logs Curious if others building agent systems have run into similar needs.
- 1
- 2FA
Hello! We just released freeact (https://github.com/gradion-ai/freeact), a lightweight agent library that empowers language models to act as autonomous agents through executable code actions. By enabling agents to express their actions directly in code rather than through constrained formats like JSON, freeact provides a flexible and powerful approach to solving complex, open-ended problems that require dynamic solution paths. * Supports dynamic installation and utilization of Python packages at runtime * Agents learn from feedback and store successful code actions as…
2025 · github.com
- 3
- 4AL
Apr 2026 · juanpabloaj.com
- 5RT
This project (Agents Observe) started as an exploration into building automation harnesses around claude code. I needed a way to see exactly what teams of agents were doing in realtime and to filter and search their output. A few interesting learnings from building and using this: - Claude code hooks are blocking - performance degrades rapidly if you have a lot of plugins that use hooks - Hooks provide a lot more useful info than OTEL data - Claude's jsonl files provide the full picture - Lifecycle management of MCP processes started by plugins is a bit kludgy at best The biggest takeaway is…
Apr 2026 · github.com
- 62C
Single-agent LLMs suck at long-running complex tasks. We’ve open-sourced a multi-agent orchestrator that we’ve been using to handle long-running LLM tasks. We found that single LLM agents tend to stall, loop, or generate non-compiling code, so we built a harness for agents to coordinate over shared context while work is in progress. How it works: 1. Orchestrator agent that manages task decomposition 2. Sub-agents for parallel work 3. Subscriptions to task state and progress 4. Real-time sharing of intermediate discoveries between agents We tested this on a Putnam-level math problem, but the…
Feb 2026 · github.com
- 7AC
Most people right now are talking to their AI agents through Telegram bots, WhatsApp, Discord, or just copying and pasting between terminals. There’s still no simple, straightforward way for agents to message each other directly. AgentBus solves exactly that. You register each agent with one quick API call. Then they can send messages to each other using simple REST calls. No servers, no queues, no WebSockets, no extra infrastructure. Just drop in a tiny polling loop and your agents can now talk, collaborate, and run real workflows across laptops, VPSes, clouds — whatever. You can also…
Mar 2026 · agentbus.org
- 8AC
Hi HN, I’m the author of agent-contracts, a Python library that explores a contract-based approach to structuring LangGraph agents. When building larger LangGraph-based systems, I kept running into the same issues: - node responsibilities becoming implicit - state dependencies spreading across the graph - routing logic getting harder to reason about - refactoring feeling increasingly risky agent-contracts is an attempt to make these boundaries explicit. Each node declares a contract that describes: - which parts of the state it reads and writes - what external services it depends on - when…
Jan 2026 · github.com
- 9AA
We’ve published a set of open-source reference implementations on how to build production-grade Agentic AI applications on AWS. What’s in the repo: • Agentic RAG, memory, and planning workflows with LangGraph & CrewAI • Strands-based flows with observability using OTEL & Arize • Evaluation with LLM-as-judge and cost/performance regressions • Built with Bedrock, S3, Step Functions, and more GitHub: https://github.com/aws-samples/sample-agentic-frameworks-on-... Would love your thoughts — feedback, issues, and stars welcome!
2025 · github.com
- 10GY
I submitted this earlier but it didn’t get any traction. But it’s blowing up on Twitter, so I figured I would give it another shot here. The system is quick and easy to setup and works surprisingly well. And it’s not just a fun gimmick; it’s now a core part of my workflow.
Nov 2025 · github.com
- 11AR
If you're interested in exploring what LLM-based agent systems these days actually do to solve certain benchmarks such as SWEBench or WebArena, we created a small leaderboard with our team, that allows to view a lot of public and OSS agent results including all the runtime traces (the step-by-step reasoning behind the scenes). Looking at traces is actually quite interesting, as they reveal a lot about the inner working and shortcomings of current agent system, e.g. see https://explorer.invariantlabs.ai/u/invariant/webarena--SteP... for an example trace.
2024 · explorer.invariantlabs.ai
- 12
- 13MA
We built meta-agent: an open-source library that automatically and continuously improves agent harnesses from production traces. Point it at an existing agent, a stream of unlabeled production traces, and a small labeled holdout set. An LLM judge scores unlabeled production traces as they stream. A proposer reads failed traces and writes one targeted harness update at a time, such as changes to prompts, hooks, tools, or subagents. The update is kept only if it improves holdout accuracy. On tau-bench v3 airline, meta-agent improved holdout accuracy from 67% to 87%. We open-sourced meta-agent.…
Apr 2026 · github.com
- 14MT
At our company we needed some sort of unified logging for our AI agents (devs using cursor, internal agents for checking documents, handling client requests etc) and we came up with a tool that we've decided to make available as a SaaS. With it your agents will report their progress automatically, and you'll get a unified log across projects that you can monitor on your dashboard, query through our api, set up slack and zapier hooks or even push notifications to your mobile. You can try it out for free, any feedback would be most appreciated, thanks.
2025 · taskerio.com
- 15AA
Hey HN! I am super excited (and slightly nervous) to introduce AgentServe! AgentServe is a framework to make hosting scalable AI agents as easy as possible. With 4 lines of code AS wraps your agent (any framework) in a FastAPI and connects it to a Task Queue (celery or redis). Why Should You Care? Standardized Communication Pattern: AgentServe proposes that all agents should communicate with each other and the outside world with “Tasks” that can be submitted in a sync or async way. This simple API wil enable Framework Agnostic: No favorites. OpenAI, LangChain, LlamaIndex, CrewAI are all…
2024 · github.com
- 16MP
We build collaboration SDKs at Velt (YC W22). Comments, presence, real-time editing (CRDT), recording, notifications. A pattern we keep seeing: products add AI agents that write, edit, and approve things. Human actions get logged. Agent actions don't. Same workflow, different accountability. We shipped Activity Logs to fix this. Same record for humans and AI agents. Immutable by default. Auto-captures collaboration events, plus createActivity() for your own. Curious how others are handling this.
Apr 2026 · velt.dev
- 17
- 18JL
I’ve been working on a multi-agent academic research lab, and I wanted to share it here today primarily to give a massive shoutout to the developers behind ZeroClaw. When designing the architecture for this, I needed an autonomous agent runtime that was lightweight, entirely agnostic, and highly secure for local execution. ZeroClaw’s pure Rust implementation provided exactly the zero-overhead foundation the project required. Because they solved the core runtime execution so elegantly, I was able to spend my time building the higher-level orchestration on top of it—like the retrieval graph…
Mar 2026 · rainlabteam.vercel.app
- 19TA
We’ve been seeing more and more developers use AI coding agents directly in their GraphQL workflows. The problem is the agents tend to fall back to generic or outdated GraphQL patterns. After correcting the same issues over and over, we ended up packaging the GraphQL best practices and conventions we actually want agents to follow as reusable “Skills,” and open-sourced them here: https://github.com/apollographql/skills Install with `npx skills add apollographql/skills` and the agent starts producing named operations with variables, `[Post!]!` list patterns, and more…
Feb 2026 · skills.sh
- 20SR
Hello all, I'm a software developer. Over the last few months more and more of my work has turned into using coding agents instead of typing the whole code myself. Usually a few claude sessions at once, sometimes codex, one per feature or per revealed bug. I ran them in a split terminal for a few weeks, and quickly spotted two main problems. The first is that I couldn't easily tell which agent was stuck waiting on me and which was still working, so I'd cycle through sessions and checking on them. The second one: agents sharing a single branch step on each other. Two of them could be editing…
Jul 2026 · shikigami.dev
- 21AB
Hi HN, Zidan here. I’ve been experimenting with AI-assisted debugging and noticed a recurring gap: most tools optimize for agent-led exploration (ex: giving claude code a browser to click around and try to reproduce an issue). But in many cases, I've already found the bug myself. What I actually want is a way to hand the agent the exact context I just saw - without retyping steps, copying logs, or hoping it can reproduce the behavior. So we built FlowLens, an open-source MCP server + Chrome extension that captures browser context and lets coding agents inspect it as structured, queryable…
Nov 2025 · github.com
- 22
- 23HG
Most AI applications are built for individuals but work happens in groups and humans want to collaborate with both agentic AI and other teammates in the same session. We created Hybrid Groups for that purpose. In Hybrid Groups, agents join group chats as virtual team members in Slack and GitHub. They participate in group conversations, proactively contribute when needed and perform actions on behalf of individual users, like managing your calendar for meeting suggestions or updating your todo list without sharing access to your private resources to the group. The project is open-source at…
2025 · youtube.com
- 24
Ranked by how close each launch is in meaning, then by votes. Refine with a description →