Skip to main content
Software Engineering Daily

AURA and Open-Source Agents for Production Operations

53 min episode · 2 min read
·
Andre Elizondo

Episode

53 min

Read time

2 min

Topics

Remote Work, Leadership, Artificial Intelligence

AI-Generated Summary

Key Takeaways

  • Declarative Agent Configuration via TOML: Aura uses a simple TOML file to define agents, orchestrators, and workers without scripting reasoning loops or retry logic. Teams specify system prompts, tool access, and LLM selection per agent. Sane defaults handle orchestration mechanics automatically, reducing time-to-outcome from days of framework assembly to same-day deployment.
  • Mixed-Model Orchestration for Token Economics: Assign a large model like Claude Opus to the top-level orchestrator for planning and reasoning, then configure smaller models like Haiku to individual worker agents for delegated tasks. This tiered approach is declared directly in the TOML config and can meaningfully reduce token costs at production scale without sacrificing output quality.
  • Scratchpad Pattern for Context Window Management: SRE workflows generate data volumes that immediately overflow context windows when fed raw into models. Aura's native Scratchpad feature intercepts tool outputs, writes them to disk, and lets the model interact with file contents selectively. Enabling it requires a single config line, preventing context bloat from tools like Prometheus MCP servers.
  • Graduated Autonomy via Three Control Layers: Teams configure human-in-the-loop across three distinct levels: restricting write-access tools entirely, capping how far an agent progresses before requesting approval, or enabling full autonomous remediation. Mesmo's MCP server exposes a single help-request tool that handles on-call lookup and Slack notification automatically, removing the need for agents to resolve those dependencies themselves.
  • Runbook Feedback Loop via Agent-Opened PRs: Rather than treating runbooks as read-only grounding documents, Mesmo configures Aura to open GitHub pull requests updating runbooks when an investigation reveals procedural drift. This closes the institutional knowledge loop, converting one-directional consumption into a continuously maintained, agent-verified source of truth without requiring manual SRE maintenance overhead.

What It Covers

Andre Elizondo, head of product at Mesmo, explains how their open-source agent framework Aura applies Kubernetes-style declarative configuration to SRE and platform engineering workflows, addressing why production operations agents require fundamentally different architecture than coding agents across context engineering, multi-agent orchestration, memory, and governed autonomy.

Key Questions Answered

  • Declarative Agent Configuration via TOML: Aura uses a simple TOML file to define agents, orchestrators, and workers without scripting reasoning loops or retry logic. Teams specify system prompts, tool access, and LLM selection per agent. Sane defaults handle orchestration mechanics automatically, reducing time-to-outcome from days of framework assembly to same-day deployment.
  • Mixed-Model Orchestration for Token Economics: Assign a large model like Claude Opus to the top-level orchestrator for planning and reasoning, then configure smaller models like Haiku to individual worker agents for delegated tasks. This tiered approach is declared directly in the TOML config and can meaningfully reduce token costs at production scale without sacrificing output quality.
  • Scratchpad Pattern for Context Window Management: SRE workflows generate data volumes that immediately overflow context windows when fed raw into models. Aura's native Scratchpad feature intercepts tool outputs, writes them to disk, and lets the model interact with file contents selectively. Enabling it requires a single config line, preventing context bloat from tools like Prometheus MCP servers.
  • Graduated Autonomy via Three Control Layers: Teams configure human-in-the-loop across three distinct levels: restricting write-access tools entirely, capping how far an agent progresses before requesting approval, or enabling full autonomous remediation. Mesmo's MCP server exposes a single help-request tool that handles on-call lookup and Slack notification automatically, removing the need for agents to resolve those dependencies themselves.
  • Runbook Feedback Loop via Agent-Opened PRs: Rather than treating runbooks as read-only grounding documents, Mesmo configures Aura to open GitHub pull requests updating runbooks when an investigation reveals procedural drift. This closes the institutional knowledge loop, converting one-directional consumption into a continuously maintained, agent-verified source of truth without requiring manual SRE maintenance overhead.

Notable Moment

Elizondo reframes the SRE role entirely: rather than agents replacing on-call engineers, the outcome Mesmo observes internally is that SREs shift from reactive firefighting toward designing reliability systems, while agents handle tribal knowledge that previously lived only in individual engineers' heads.

Know someone who'd find this useful?

Episode Transcript

AI agents have transformed how software gets written, but the operational side of running software in production has not yet experienced a similar revolution. The same teams responsible for keeping systems healthy, investigating incidents, and managing reliability are still doing much of that work manually. Mesmo is a production AI company that makes autonomous operations fast, efficient, and safe. Their open source project, Aura, is a declarative agent framework specifically designed for SRE and platform engineering workflows. It takes a Kubernetes inspired approach where teams define what they want agents to do rather than scripting every step of how to do it. Andre Elizondo is the head of product at Mesmo, and he has a background in systems engineering, SRE, and observability. In this episode, Andre joins Kevin Ball to discuss what makes SRE agent workflows fundamentally different from coding agents, how Aura handles context engineering, Aura's declarative configuration model, the spectrum of agent autonomy, and where the role of the SRE is headed as agents take on more of the operational work. Kevin Ball or Kate Ball is the vice president of engineering at Mento and an independent coach for engineers and engineering leaders. He cofounded and served as CTO for two companies, founded the San Diego JavaScript meetup, and organizes the AI in action discussion group through Latent Space. Check out the show notes to follow Keball on Twitter or LinkedIn, or visit his website, keball.llc. Andre, welcome to the show. Thanks for having me. Yeah. I'm excited to dig in. So let's start with you. Can you give us a little bit of your background and how you came to be at Mesmo? Yeah. Absolutely. So my background at my core is, you know, I started my career running systems the And so my my view on the space is primarily from an operator or an SRE. Back in the day, we called them sysadmins. Right? And over the last few years, I've been heavily involved in the AI ecosystem, especially around agents. And so, you know, here at Mesmo, what I'm focused on, I head up our product team and, we're a small but mighty team that's very focused on building, you know, really the, the ecosystem around how we enable SREs, platform engineers, really everybody in in operations to gain the same benefits that we've seen with coding agents over the past few years rather for, how we better use them to, reinvent how we build, maintain, troubleshoot everything around production. Nice. So can you give us actually just that, like, quick high level what is Mesmo? And we're talking a lot about agents, and we'll talk a lot about agents. But, like, Mesmo is a company. What do you do? Yeah. So when you think about what the software factory is that a lot of folks are talking about right now, usually, that's around, hey. How do I use something like a coding agent to build software faster, test it faster, and get it …

Get the full transcript (11,412 words) + summary by email — free

One-time email with the complete transcript and AI summary of this episode. No account needed.

One email, no spam. We’ll also show you what SignalCast does.

Browse all Software Engineering Daily transcripts →

You just read a 3-minute summary of a 50-minute episode.

Get Software Engineering Daily summarized like this every Monday — plus up to 2 more podcasts, free.

Pick Your Podcasts — Free

Keep Reading

Books, tools, and gear mentioned in this episode

SignalCast may earn commission on purchases via these links.

Tools

  • AuraBy guest

    by Mesmo

    Andre Elizondo, head of product at Mesmo, explains how their open-source agent framework Aura applies Kubernetes-style declarative configuration to SRE and platform engineering workflows
  • preventing context bloat from tools like Prometheus MCP servers

More from Software Engineering Daily

We summarize every new episode. Want them in your inbox?

Similar Episodes

Related episodes from other podcasts

Explore Related Topics

This podcast is featured in Best Cybersecurity Podcasts (2026) — ranked and reviewed with AI summaries.

Read this week's AI & Machine Learning Podcast Insights — cross-podcast analysis updated weekly.

You're clearly into Software Engineering Daily.

Every Monday, we deliver AI summaries of the latest episodes from Software Engineering Daily and 192+ other podcasts. Free for one show.

Start My Monday Digest

No credit card · Unsubscribe anytime