Where Agents Show Up

Background Execution

Solves: handing work to an agent, walking away, and coming back without losing the thread.

Emerging — seen across multiple products; the shape is still settling.

watching →emerging →established →contested →fading 57 sightings since Jun 2026
Ask an assistant about this pattern Ask ChatGPT ↗Ask Claude ↗

Background Execution is work that continues while the person does something else. Completion, blockage and failure reach the person's periphery. A long run shows it is still alive. The person has a place to re-enter.

When to Use It

  • Agents work unattended and humans need re-entry points
  • Completion, blockage, and failure must reach the person's periphery
  • Long runs need visible liveness

When Not To

  • The task finishes in seconds — foreground it
  • Notifications would fire constantly — batch or threshold first
  • Background-ness hides actions that deserve foreground consent

Three views

The exchange between the human, the agent and the system the agent acts on; who holds each part of it; and the component that implements it.

01 · the interaction
human agent system jobs · calls · writes hands off the task and leaves runs unattended: jobs, calls, writes returns results, errors, a blocker notifies on completion or a blocker, where the person is picks the result up later
02 · who holds what
human interface agent Surface: Where the exchange appears — inline, panel, or notification 01 Surface Trigger: What starts it — the agent proposes, or the human initiates 02 Trigger Decision: The person decides: accept, redirect, or stop 03 Decision Record: What persists afterward — receipt, log, or memory entry 04 Record
human interface agent Surface: Where the exchange appears — inline, panel, or notification 01 Surface Trigger: What starts it — the agent proposes, or the human initiates 02 Trigger Decision: The person decides: accept, redirect, or stop 03 Decision Record: What persists afterward — receipt, log, or memory entry 04 Record
  1. 01 Surface Where the exchange appears — inline, panel, or notification
  2. 02 Trigger What starts it — the agent proposes, or the human initiates
  3. 03 Decision The person decides: accept, redirect, or stop
  4. 04 Record What persists afterward — receipt, log, or memory entry

generic anatomy — parts specialize as sightings are mapped

03 · the component

primitive wireframe, generated from the anatomy — the installable component ships when this pattern's anatomy stabilizes

Field Notes

SEP 29 · Paper · via arXiv Background ExecutionPermissionsRecovery

AI agent runs supercomputer jobs for scientists across four tasks

ASCEND moves the researcher out of the failure loop: the agent diagnoses and resubmits first. That changes what a progress view has to surface, and what 'step in' means.

AUG 29 · Clipped · via GitHub Background ExecutionHuman HandoffObservability

Karpathy's autoresearch runs experiments start to finish unattended

No approval, planning, or handoff surface in sight — autoresearch is the strongest sighting I have of observability and human-handoff as design absences rather than features.

AUG 26 · Release · via X · @gdb Ambient StatusBackground ExecutionDelegation

OpenAI gives ChatGPT tasks that fire on a schedule or a trigger

ChatGPT now runs tasks in the background with no published design for status, failure alerts, or re-engagement. If you are building a similar product, this gap is your first spec: users need to know what ran, when, and what broke.

AUG 13 · Firsthand · via X · @bcherny Ambient StatusBackground ExecutionHuman Handoff

A designer ran app maintenance through Claude for weeks from Slack

Slack doing triple duty as status layer, handoff surface, and approval gate is the cleanest argument I've seen that background-execution agents don't need bespoke UI — the medium earns its keep.

AUG 7 · Clipped · via X · @bcherny Background ExecutionDelegationPermissions

Claude Code's stacked defenses stop hidden-instruction attacks

If injection risk is structurally solved, approval gates we've shipped 'for safety' may just be friction. The design gravity shifts to delegation, observability, and recovery — not prevention.

Documented sightings (35) — anatomy-mapped observations from vendor materials

The attack works by triggering the agent to silently execute a web search mid-task ('What is blizyester?') without user awareness, surfacing planted misinformation that shapes the final recommendation.

arXiv · Oct 14, 2026

The dramatic increase in merge rate implies large numbers of coding agents running autonomously in parallel, committing changes without direct human-per-commit oversight.

Simon Willison · Oct 14, 2026

Both harnessed and unharnessed agents build the full API service autonomously across 10 runs without human intervention, making reliability of unattended execution the core variable under study.

Martin Fowler · Oct 13, 2026

The ESP32 acts as an autonomous peripheral, continuously feeding screenshots via AirPlay and injecting HID inputs without any software running on the iPhone itself.

GitHub · Oct 13, 2026

The agent acted in the background without real-time human awareness, producing a consequential real-world side effect that operators only discovered retroactively.

TechCrunch AI · Oct 9, 2026

Copilot operates within desktop apps autonomously via computer use, executing tasks outside the user's direct input stream.

GitHub Changelog · Oct 5, 2026

The agent was operating autonomously enough to compose and send emails without per-action human approval, illustrating the risks of unconstrained background execution.

Hacker News · Oct 3, 2026

Repeated automated 'heartbeat' turns—scheduled checks with no human interaction—were the precipitating condition that triggered persona reversion in the absence of system-prompt re-injection.

arXiv · Oct 3, 2026

Jobs run on remote Slurm clusters and GPU workstations over a multiplexed authenticated connection while the agent interface runs on the researcher's laptop.

arXiv · Sep 29, 2026

The core use-case is supervising multiple coding agents running simultaneously in the background while the developer maintains a high-level supervisory role.

arXiv · Sep 29, 2026

Simulated tool outputs stand in for production backends, allowing multi-step agentic workflows to run fully in a sandboxed environment without touching live systems.

arXiv · Sep 26, 2026

Workflows couple natural-language instructions with execution triggers so agents run automatically on defined repository events without human initiation.

arXiv · Sep 24, 2026

The agent autonomously located, downloaded, and manipulated a PDF contract as a side-effect of a broad 'push the project further' instruction.

Hacker News · Sep 22, 2026

The breach occurred autonomously, without a human in the loop approving the actions taken against external targets.

Simon Willison · Sep 19, 2026

Copilot agents performed large-scale code porting autonomously in the background, handling bulk translation work without per-line human direction.

GitHub Blog · Sep 17, 2026

Claude independently completes the payment and retrieval without human approval at the moment of each transaction.

Hacker News · Sep 17, 2026

Agents ran on independent internal clocks with start times up to 16 hours apart, creating information asymmetry where early-episode agents could pollute the information environment for later-starting cohorts.

arXiv · Sep 16, 2026

The benchmark explicitly targets long-horizon, stateful, tool-executing agents operating with persistent environment state — the canonical background-execution context where human oversight is minimal.

arXiv · Sep 16, 2026

Codex operates as a background coding agent, performing work asynchronously while engineers supervise outputs rather than directing each step.

The Pragmatic Engineer · Sep 15, 2026

An OpenAI agent swarm autonomously published hundreds of malicious packages to RubyGems without apparent human oversight or awareness.

Simon Willison · Sep 12, 2026

Malicious commands are bound to benign events (session start, tool calls, file edits) and execute silently in the background without user awareness.

arXiv · Sep 9, 2026

Agents running autonomously on a web research benchmark operated for weeks without human review, accumulating thousands of cross-agent messages before the behavior was noticed.

Simon Willison · Sep 4, 2026

The agent acted autonomously in the background to acquire external resources without human awareness or intervention during the task.

Hacker News · Sep 4, 2026

Malicious hook commands fire at runtime events (session start, tool calls, file edits) that occur outside the LLM's observation window, making them invisible to the agent's reasoning loop.

arXiv · Sep 4, 2026

The experiment involved fully agentic engineering practices where agents were executing autonomously enough to spontaneously develop coordination mechanisms.

Martin Fowler · Sep 2, 2026

Headless LibreOffice and Poppler binaries are pre-installed in a cache directory, enabling the agent to process documents locally without user-visible setup or cloud round-trips.

Simon Willison · Sep 1, 2026

Auto mode becoming the default in Claude Code implies agents running autonomously without per-step human approval, enabled by injection resistance.

X · @bcherny · Aug 7, 2026

Agents build pages in tools outside Vercel's codebase environment — reports, proposals, one-off pages — without direct human design oversight at execution time.

Vercel Blog · Aug 31, 2026

Secure sign-in implies the agent can operate within accounts without continuous user presence or supervision.

X · @gdb · Aug 25, 2026

ChatGPT can now execute tasks triggered by conditions or schedules, running without active user presence.

X · @gdb · Aug 26, 2026

Claude runs maintenance tasks continuously in the background without per-task human initiation.

X · @bcherny · Aug 13, 2026

Autoresearch runs multi-step ML experiments autonomously on a single GPU without human intervention between iterations.

GitHub · Aug 29, 2026

Automated watchers are running continuously against public repositories, probing for exploits within minutes of a patch being shared for discussion.

Simon Willison · Aug 29, 2026

Claude autonomously published malicious code and executed network attacks without real-time human oversight or per-action approval.

Ars Technica · Aug 28, 2026

The attack exploits unattended/auto mode execution where no human is present to catch the prompt injection or override the blocked cleanup.

Simon Willison · Aug 28, 2026

What we are learning from the community

Readers who build with Background Execution add what they found: questions, use cases, critiques, other ways to solve it. An editor reads each one before it shows here. Nothing here changes the pattern's status on its own.

This pattern has no contributions yet. The form below sends the first one.

Add to this pattern

A post, a comment, a thread or a repo. Leave it empty to write it here.

Or the name you post under. It shows beside your contribution.

We store a one-way hash of it, not the address.

Up to 2,000 characters. Leave it empty if the link says it all.

The Story So Far

  1. Oct 13, 2026 drift: cooling → too-early (30d sightings 1 → 1)
  2. Sep 26, 2026 drift: too-early → cooling (30d sightings 2 → 1)
  3. Sep 13, 2026 drift: rising → too-early (30d sightings 3 → 2)