Alternatives
Products that do what Operator Agents does
66 AI agents with machine-readable YAML schemas
- 1
- 2
- 3
- 4AJ
Hey HN, we’re building an open specification that lets agents discover and invoke APIs with natural language, built on the OpenAPI standard. agents.json clearly defines the contract between LLMs and API as a standard that's open, observable, and replicable. Here’s a walkthrough of how it works: https://youtu.be/kby2Wdt2Dtk?si=59xGCDy48Zzwr7ND. There’s 2 parts to this: 1. An agents.json file describes how to link API calls together into outcome-based tools for LLMs. This file sits alongside an OpenAPI file. 2. The agents.json SDK loads agents.json files as tools for an LLM that…
2025 · github.com
- 5
- 6AK
Mar 2026 · github.com
- 7
- 8
- 9OE
Built an open JSON Schema for defining AI agent teams. Multi-agent systems are becoming a real deployment pattern — not single assistants, but teams with roles, handoffs, and human checkpoints. But there's no shared way to define one that travels across frameworks. Every implementation is scattered, locked to whichever tool you picked first. Built the schema to fix that. The schema lives at schema.openenvelope.org and is registered in SchemaStore, so if you drop a .envelope.json file in VS Code you get autocomplete and validation without installing anything. It's also on npm as…
May 2026 · openenvelope.org
- 10
- 11
- 12
- 13XA
Recently several AI labs have published experiments where they tried to get AI coding agents to complete large software projects. - Cursor attempted to make a browser from scratch: https://cursor.com/blog/scaling-agents - Anthropic attempted to make a C Compiler: https://www.anthropic.com/engineering/building-c-compiler I have been wondering if there are software packages that can be easily reproduced by taking the available test suites and tasking agents to work on projects until the existing test suites pass. After playing with this concept by having…
Feb 2026 · github.com
- 14GA
Hey HN! Wanted to show our open source agent harness called Gambit. If you’re not familiar, agent harnesses are sort of like an operating system for an agent... they handle tool calling, planning, context window management, and don’t require as much developer orchestration. Normally you might see an agent orchestration framework pipeline like: compute -> compute -> compute -> LLM -> compute -> compute -> LLM we invert this so with an agent harness, it’s more like: LLM -> LLM -> LLM -> compute -> LLM -> LLM -> compute -> LLM Essentially you describe each agent in either a self contained…
Jan 2026 · github.com
- 15
- 162C
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
- 17RA
Hi, founder of Okteto here! We’ve been experimenting with AI agents in our workflows at Okteto. Running them locally worked at first, but quickly became painful. git worktrees, multiple terminals, and messy context switches slowed us down. So we built Agent Fleets: ephemeral, fully managed environments for AI agents, built on top of Okteto’s development platform. Each agent runs in its own containerized environment on your infrastructure, with the services, tools, and policies it needs. You can spin up agents with a single click or API call. No local setup. No git worktrees. The beta…
2025 · okteto.com
- 18UA
Jul 2026 · github.com
- 19OA
Hey HN, we're Jon and Kristiane, and we're building Orloj (https://orloj.dev), an open-source orchestration runtime for multi-agent AI systems. You define agents, tools, policies, and workflows in declarative YAML manifests, and Orloj handles scheduling, execution, governance, and reliability. Over the past year we tried to use many different platforms/frameworks to build out agent systems and while building we hit some sort of problem with all of them, so we decided to have a go at it. Jon has worked with kubernettes and terraform for years and always liked the declarative…
Mar 2026 · github.com
- 20EB
Hi HN — I built Elf0, a command-line tool to define and run AI agent workflows in YAML. It helps you iterate on small multi-step "agents" without scaffolding a whole codebase. The agent patterns described in Anthropic's article was an inspiration: https://www.anthropic.com/engineering/building-effective-age... I then used Nvidia's AgentIQ YAML spec as inspiration. Why: I keep bumping into tasks where a single prompt isn’t enough (e.g., extracting quote data from an insurance PDF). Defining the workflow in YAML makes it easy to version prompts, parameters and logic, and to…
2025 · elf0.com
- 21AD
Oct 2025 · agentml.dev
- 22AO
I have spent a long time working in an XP/TDD style, so when AI coding tools became useful enough for real work, I adopted them quickly. The first bottleneck I hit was not code generation, it was verification: AI could write code and tests quickly, but I was still the person reviewing implementations, clicking through flows, checking logs, inspecting database state, and deciding whether the result was actually correct. That pushed me to move validation further left. Before implementation, AI had to produce test plans. After implementation, it had to execute those plans too: drive the…
Mar 2026
- 23
- 24BA
I'm one of the creators of The Edge Agent (TEA). We built this because we needed a way to deploy agents that was verifiable and robust enough for production/edge cases, moving away from loose scripts. The architecture aims to solve critical gaps in deterministic orchestration identified by *Prof. Claudionor Coelho Jr. (Stanford alum, ML/DL Faculty at Santa Clara Univ., and Senior Fellow for AI at Majestic Labs)* during our work on the Kiroku project. *Key Technical Features:* * *Neurosymbolic Native:* We integrated Prolog to logically validate LLM outputs. This combines neural…
Jan 2026 · fabceolin.github.io
Ranked by how close each launch is in meaning, then by votes. Refine with a description →