# Always-on agents run production without the on-call tax — Justin Smith, Resolve AI

Source: [AI Engineer](https://www.youtube.com/watch?v=vSx5IULvBns)  
Feed7 permalink: https://feed7.dev/p/always-on-agents-run-production-without-the-on-call-tax-justin-smith-res-06ukqzk  
Published: 2026-08-09T14:45:06.000Z  
Trust: Source Linked (source_linked)

## Why Included

Always-on production agents can turn releases and operational events into tailored monitoring tasks. The useful pattern is persistent context plus scoped triggers, checks, and escalation.

## Source Summary

Resolve describes cloud agents that run on schedules, event streams, or direct messages inside a sandbox with shared memory. In the demo, a **GitHub release tag** triggers inspection of the code changes, selection of relevant telemetry, and a release-specific monitoring plan.

## Practical Implication

Start with bounded background work such as weekly handovers, health summaries, release watching, or answering operational questions. Connect existing skills and MCP services, and require human confirmation when the agent lacks enough confidence to respond.

## Agent-Ready Context

Resolve describes cloud agents that run on schedules, event streams, or direct messages inside a sandbox with shared memory. In the demo, a **GitHub release tag** triggers inspection of the code changes, selection of relevant telemetry, and a release-specific monitoring plan.

Start with bounded background work such as weekly handovers, health summaries, release watching, or answering operational questions. Connect existing skills and MCP services, and require human confirmation when the agent lacks enough confidence to respond.

The release example used a **fake environment**, and the talk reports no measured reliability, cost, or incident-reduction results. Persistent access to telemetry, Slack, and production knowledge also makes permission scope, stale memory, and false confidence important unresolved risks.

## Connected Context

Feed7 judgment across 409 accumulated Signals:

This extends cloud agents from requested jobs to persistent operational participants triggered by schedules and events. It narrows the sensible adoption path to bounded monitoring and handover tasks with confidence-based escalation, while making memory quality, least-privilege access, traceability, and cost limits prerequisites for unattended operation. Because the demonstration was synthetic, production reliability remains unconfirmed.

- [Scaling Managed Agents: Decoupling the brain from the hands](https://feed7.dev/p/managed-agents-00zpz67) — Anthropic’s separation of harness and replaceable sandboxes provides an infrastructure pattern for running the persistent background work described here.
- [MemLens: A Value-Aware Memory Management System with Interactive Analytics for LLM-based Agents](https://feed7.dev/p/2607-25992v1-0q2kxfl) — MemLens directly addresses the stale or indiscriminate shared-memory risk by making individual memories and their tradeoffs inspectable.
- [Agent Runs now available in the Vercel MCP and CLI](https://feed7.dev/p/agent-runs-vercel-mcp-cli-06cfo04) — Run traces covering tool calls and token use provide the observability needed to investigate and refine unattended operational agents from real behavior.
- [AI Gateway now supports team and project spend budgets](https://feed7.dev/p/ai-gateway-spend-budgets-and-alerts-1969711) — Hierarchical spend caps add a necessary failure boundary for scheduled and event-driven agents that can otherwise consume resources without an active operator.

## Context Map

- Layer: infra
- Domains: coding
- Topics: observability, cloud-agents, agent-memory

## Uncertainty

- The release example used a **fake environment**, and the talk reports no measured reliability, cost, or incident-reduction results. Persistent access to telemetry, Slack, and production knowledge also makes permission scope, stale memory, and false confidence important unresolved risks.

## Agent Instruction

Use this item as source-backed context. Do not invent claims beyond the linked source. If this item conflicts with another source, call out the conflict.