Can I just run coding agents in the background on my laptop?

You can, and many teams do: multiple terminals, git worktrees, maybe a Mac Mini in the corner. But that's agents running in the background, not background agents. There's no event triggering, no governance, no audit trail, and everything stops when the machine sleeps. The gap between those two things is where most organizations stall.

What infrastructure do background agents need?

Three things that don't exist on your laptop: isolated compute environments that spin up on demand, an event system that routes triggers (PR opened, CVE published, Slack message, cron schedule) to the right agent, and a governance layer for permissions, audit trails, and blast-radius controls.

Are background agents safe?

Background agents are as safe as the infrastructure and governance you put around them. The key controls are sandboxed environments, human review gates on all output via pull requests, audit trails for every action, and bounded blast radius so a single agent failure can't cascade.

Do background agents replace developers?

No. They shift what developers do. Instead of writing every line, developers move 'on the loop', reviewing agent output, calibrating behavior, designing systems, and focusing on work that requires judgment. You still look at the code. You still own the decisions. The difference is you're reviewing work, not doing it keystroke by keystroke.

What are common use cases for background agents?

The highest-value use cases are repetitive, well-defined tasks with bounded blast radius: dependency updates across hundreds of repos, CVE remediation within hours of disclosure, CI pipeline migrations, lint and standards enforcement, test coverage expansion, and code review triage.

How are background agents different from CI/CD pipelines?

CI/CD pipelines execute predefined steps: build, test, deploy. They don't make decisions or generate new code. Background agents are autonomous: they receive a trigger, reason about the problem, write code, run tests, and open a pull request.

The Self-Driving Codebase

Background agents are AI coding agents that run autonomously on cloud infrastructure, triggered by events, schedules, or system signals to perform development tasks across the software delivery lifecycle without a developer at the keyboard.

The Problem: Localhost Is the Ceiling

Autocomplete became coding agents. Coding agents became three coding agents running in parallel on your laptop. But localhost wasn't built for this. Agents fight over machine state, secrets become exposed, and everything stops when the machine sleeps. That works for indie-hackers, but is untenable for professional engineering.

The False Summit

Individual speed ≠ organizational velocity. You rolled out coding agents. Engineers are faster. PRs flood in. Yet cycle time doesn't budge. DORA metrics are flat. The backlog grows. Gains are compounding with the individual, not the organization.

What Is a Background Agent

A coding agent needs your machine and your attention. A background agent needs neither. It runs in its own development environment in the cloud: full toolchain, test suite, everything. Completely decoupled from your device and your session. Kick one off from your laptop, check the result from your phone.

Step 01: Establish Background Agent Primitives

Autonomous agents need infrastructure that doesn't exist on your laptop: sandboxed execution environments, governance enforced at runtime, context and connectivity to internal systems, event-driven triggers, and fleet coordination.

Sandboxed Execution — Isolated, reproducible environments with full toolchains.
Governance — Identity, permissions, audit trails enforced at the execution layer, not via prompts.
Context & Connectivity — Agents that can reach internal APIs, database replicas, private registries behind your firewall.
Triggers — Scheduled agents, event-driven agents, agent fleets, agent swarms, mobile triggers.
Fleet Coordination — Parallel provisioning across hundreds of repos with progress tracking.

Step 02: Find Your Systems Bottlenecks

Survey your developers, sit with your teams, map where time goes. High-value starting points: code review backlogs, CI failure triage, merge conflicts, CVE remediation, test coverage gaps, code standards enforcement, release notes.

Step 03: Scale Your Software Factory

The engineering organization is an industrial system. Background agents change the operating model. Engineers move on the loop instead of in it — reviewing agent output, calibrating behavior, designing systems.

FAQ

Can I just run coding agents in the background on my laptop?: You can, but that's agents running in the background, not background agents. There's no event triggering, no governance, no audit trail, and everything stops when the machine sleeps.
What infrastructure do background agents need?: Isolated compute environments on demand, an event system that routes triggers to the right agent, and a governance layer for permissions, audit trails, and blast-radius controls.
Are background agents safe?: They're as safe as the infrastructure you put around them. Key controls: sandboxed environments, human review gates via pull requests, audit trails, bounded blast radius.
Do background agents replace developers?: No. They shift what developers do — from writing every line to reviewing, calibrating, and designing.
How are background agents different from CI/CD pipelines?: CI/CD pipelines execute predefined steps. Background agents are autonomous: they receive a trigger, reason about the problem, write code, run tests, and open a pull request.

Resources

Published by Ona — infrastructure for background agents.