Santa Augmentcode Intent Ep.4

Source: Dev.to

The Problem

In the early Workshop days all the Elves shared one big table. It seemed efficient—until it wasn’t.

• Jingle sanded a wheel just as Jangle reached for it.
• Twinkle’s paint ended up on Tinkle’s train set.
• The great Christmas Collision of 1889 (I do not wish to speak of it).

The solution was obvious in retrospect: give every Elf their own workbench—isolated, private, but connected to the same Master Gift List.

Augment Intent does the same thing. It just calls them workspaces.

When multiple agents (or multiple humans) work on the same set of files at the same time, collisions are inevitable.

Agent A modifies auth-middleware.ts at line 47
Agent B modifies the same file at line 52

Neither agent knows the other is there, so a merge conflict appears.
The conflict isn’t a bug in either agent’s reasoning; it’s a coordination failure—the absence of isolation.

Why Git’s Classic Workflow Falls Short

Git was designed for humans working mostly in series:

# Classic git workflow (one checkout)
git checkout feat/jwt-auth
# … work, commit, push

A branch is opened, worked on for days or weeks, then merged. The assumption is that the pace of change is human‑paced.

AI agents are not human‑paced. They can modify dozens of files in minutes. Under parallel multi‑agent execution, the conflict rate rises faster than any team can manage manually.

Worktrees: Git’s Built‑in Isolation

Intent solves this with isolated workspaces backed by Git worktrees.

A worktree is a lesser‑known Git feature that lets you check out multiple branches of the same repository simultaneously, each in its own directory.

• They share the repository’s object store (no duplicated data).
• Each worktree has its own working tree and index.

# Git worktree (multiple simultaneous checkouts)
git worktree add ../api-gateway-worktree   feat/jwt-auth
git worktree add ../auth-service-worktree  feat/auth-service
# Both directories exist simultaneously, sharing one .git object store

Intent automates all of this. When the Coordinator spawns a Specialist, Intent creates a dedicated worktree for that agent automatically. The Elf gets its own workbench; other Elves cannot see its in‑progress files. Files remain isolated until the Coordinator integrates the work.

Example: Three Specialist Agents

Workshop Floor
├── Auth Token Elf          → worktree: feat/auth-token-service
├── Gateway Middleware Elf → worktree: feat/gateway-middleware
└── Test Suite Elf         → worktree: feat/integration-tests (waiting)

Each worktree contains a copy of the relevant files at the point the Elf starts.

Changes made by Auth Token Elf in auth-service/src/token-service.ts are invisible to Gateway Middleware Elf until they are explicitly integrated—no accidental clobberings, no race conditions on file writes.

The Coordinator tracks the state of each worktree. When both implementation Elves finish, it orchestrates the merge—resolving any conflicts at the spec level (because the interface contracts were declared there) rather than discovering them at the file level.

Temporal Isolation

Father Christmas also values temporal isolation: the ability to close the Workshop at night and find it exactly as you left it in the morning.

In most AI tools, closing the window ends the session—context is lost and agents forget.

Intent’s workspaces are resumable. When you close the application and reopen it the next morning, every agent is exactly where it was. The spec is unchanged, the worktrees are intact, and the in‑progress commits are safe.

How it works: Intent uses auto‑commit—as agents complete units of work, their changes are committed to their branch automatically. The persistent state is the Git history itself, which survives any restart.

Intent workspace state on close:
├── spec: JWT auth — 6/9 tasks complete
├── Auth Token Elf: feat/auth-token-service — all commits saved
├── Gateway Middleware Elf: feat/gateway-middleware — all commits saved
└── Test Suite Elf: feat/integration-tests — waiting to start

Intent workspace state on reopen (next morning):
└── [identical to above — nothing lost]

For Father Christmas, this means stepping away on December 23rd, returning on the 24th, and finding every Elf at their bench with their gifts half‑wrapped exactly as left. The Workshop never forgets.

One‑Window Experience

Isolation does not mean fragmentation. Intent keeps everything visible in one window:

• Code editor – shows the active agent’s files.
• Built‑in Chrome browser – previews localhost changes in real time.
• Terminal – runs builds, tests, and scripts.
• Git integration – handles staging, committing, and branch management.

You don’t need to switch between VS Code, iTerm, Chrome, and SourceTree. The Workshop floor is one room with everything on it.

This matters for agent work because agents need to see results immediately. A Specialist that modifies a React component can open the browser preview in the same window, verify the rendering, and either commit or adjust—without handing off to a human to check.

SIPOC Overview

Workshop Analogy

At End

No collisions, no broken gifts, always resumable
Quality Control, Head Elf Pepper, the Sleight

Father Christmas has one firm rule about workbenches: an elf’s work stays on their bench until it is finished and verified. Premature merges cause half‑built toys to appear in the main inventory, confusing other elves.

In Intent terms

The Coordinator should not merge a Specialist’s branch until:

1. The Specialist has reported completion.
2. The Verifier Agent has confirmed compliance with the spec.
3. Any interface contracts with other elves have been respected.

The spec is the checklist. When all boxes are ticked, the merge is safe.

In Episode 5, Father Christmas will explain Spec‑Driven Development — the philosophical shift that puts the living spec at the centre of the workflow and uses it to ensure everything finishes in time for Christmas. This is the why behind everything we have built so far.

A tidy workbench is the sign of an organised mind. And an organised workshop is the sign of gifts arriving on time.

Ho ho ho! 🎅

Part of the Santa Augmentcode Intent series. Published on dev.to under the the‑software‑s‑journey organisation.