AgentLog – a lightweight event bus for AI agents using JSONL logs

A local control plane for AI coding agents

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…

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!

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.

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…

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.