---
id: "concept-afk-agent-work"
type: "concept"
source_timestamps: ["00:24:45", "00:29:59"]
tags: ["automation", "sandboxing", "asynchronous-workflows"]
related: ["entity-sandcastle", "concept-agentic-queues", "framework-afk-agent-pipeline", "action-use-sandcastle"]
definition: "Deploying AI coding agents to work autonomously in the background within isolated sandboxes."
---
# AFK (Away From Keyboard) Agent Work

## Definition

**AFK** = *Away From Keyboard*. AI coding agents that operate autonomously in the background, picking up tasks from a queue and producing reviewable artifacts (typically Pull Requests) without synchronous human interaction.

## Why move beyond chat

The synchronous chat paradigm caps developer leverage at ~1 agent per human. AFK work allows a single developer to **act as an engineering manager** over a fleet of parallel agents — reviewing PRs rather than writing every line.

## How it works

[[entity-matt-pocock|Pocock]] describes the following flow, formalized in [[framework-afk-agent-pipeline]]:

1. An agent picks an issue (e.g., a GitHub issue from a backlog — see [[concept-agentic-queues]]).
2. It spins up a [[entity-sandcastle]] environment.
3. It implements the code inside that sandbox.
4. It submits a Pull Request.
5. A *secondary* agent running via GitHub Actions reviews the PR.
6. A human performs the final review before merging.

## The critical role of sandboxes

Crucial to AFK work is **isolation**. Without sandboxes, autonomous agents can:

- Accidentally delete local files.
- Exfiltrate environment variables and secrets.
- Corrupt git history.
- Touch state outside the intended task.

[[entity-sandcastle]] addresses this by running agents inside Docker, Podman, or Vercel sandboxes. The corresponding action is [[action-use-sandcastle]].

## Strategic implication

AFK pipelines parallelize work massively. The developer's job shifts from author to reviewer — which requires the strategic skills described in [[concept-tactical-vs-strategic-programming]]. Without strong scoping, interface design, and test infrastructure, an AFK fleet just generates messy PRs faster.

## When it's overkill

For small or rapidly changing projects, a human + IDE copilot may be faster operationally. AFK factories shine on **large, stable codebases with repetitive work** that can be cleanly decomposed into scoped issues.