subagent-env-handshake

name	subagent-env-handshake
description	Subagent environment-handshake contract for Claude Code Agent-tool dispatch. Use when a parent session dispatches a subagent that may make tree-grounded claims such as file existence, branch identity, or landed changes - the handshake lets the subagent verify its live working-tree view matches the parent's before it prosecutes tree-grounded findings. DO NOT USE FOR: research subagents that never touch git/tree state; Copilot subagent dispatch (execution model differs).
scope	claude-only

Subagent Environment Handshake (v1)

Shared contract for parent → subagent handoff of live working-tree state in Claude Code Agent-tool dispatch. Exists to eliminate the failure mode from #380 / #383 where a subagent confidently reported tree-grounded claims (file existence, branch identity) grounded in a stale <env> block injected once at dispatch time and never refreshed.

Survival: SMC-14 governs this handshake as per-dispatch: the block is prompt-carried, delegated/informational, and intentionally not persisted.

When to use

Use this handshake for any dispatch where the subagent may claim:

• file X exists / file X does not exist
• branch is Y
• commit Z landed / commit Z is not in this branch
• any equivalent tree-grounded assertion

Skip the handshake for dispatches that only consume task descriptions, web content, or passed-in documents without live-verifying against the working tree. The opt-in rubric keeps the prompt tax off research/non-tree subagents (ND-3).

Scope (ND-4)

The handshake covers exactly four working-tree facts that can appear stale in a subagent's injected <env> block:

In-scope fields:

• parent_head — parent's live git rev-parse HEAD
• parent_branch — parent's live git rev-parse --abbrev-ref HEAD
• parent_cwd — parent's live pwd
• parent_dirty_fingerprint — SHA-256 (first 12 hex chars) of git status --porcelain output with line endings normalized to LF

Explicitly out of scope:

• Environment variables (PATH, NODE_ENV, etc.) — subagent has its own shell env; not reflected in the <env> block.
• Tool versions (node, pwsh, gh) — orthogonal to tree-state divergence.
• Terminal/TTY state — not a tree property.
• File permissions, symlink targets — outside the symptom class.

A handshake covering additional fields is a v2 schema change, not a v1 extension.

Reserved values

• workspace_mode: 'shared' — default. Parent and subagent share a working tree (Claude Code's default dispatch model per the Claude Code subagents docs).
• workspace_mode: 'worktree' — reserved, not defined in v1. The isolation: worktree frontmatter opt-in exists in Claude Code, but v1 subagent-side verifiers MUST treat workspace_mode: worktree as an error path (equivalent to missing handshake). v2 will define worktree-specific verification rules.

Schema (v1)

Authoritative schema block — the dispatch prompt-text carrier. Consumer scripts and prose templates below grep between the sentinel comment lines to build or verify the block.

# --- subagent-env-handshake v1 schema begin ---
parent_head: <sha> # string, 40 hex chars, output of `git rev-parse HEAD` in the parent
parent_branch: <branch-name> # string, output of `git rev-parse --abbrev-ref HEAD` in the parent
# Note: on detached HEAD, this field is the literal string `HEAD` on both sides — comparison succeeds; commit identity is still verified via `parent_head`
parent_cwd: <absolute-path> # string, output of `pwd` in the parent
parent_dirty_fingerprint: <12-hex> # string, SHA-256(LF-normalized `git status --porcelain`) truncated :12
workspace_mode: <shared|worktree> # enum. v1: 'shared' is the only active value; 'worktree' is reserved → error path.
handshake_issued_at: <iso-8601-utc> # string, parent-side `(Get-Date).ToUniversalTime().ToString('o')` or equivalent
# --- subagent-env-handshake v1 schema end ---

Six fields, no optional fields. The block is emitted as a Markdown HTML-comment-wrapped fenced code region (see template below) so it survives intact through prompt concatenation.

Inline prompt template (prose form)

Parent dispatch code that cannot invoke PowerShell (e.g., the markdown in commands/plan.md) constructs the handshake block directly from Bash-captured values. Copy this template verbatim, substitute the six values, and prepend to the Agent tool prompt parameter:

<!-- subagent-env-handshake v1 -->

parent_head: 0000000000000000000000000000000000000000
parent_branch: main
parent_cwd: /absolute/path/to/repo
parent_dirty_fingerprint: 000000000000
workspace_mode: shared
handshake_issued_at: 1970-01-01T00:00:00.0000000Z

<!-- /subagent-env-handshake -->

Field names and order MUST match the schema block above. Drift is locked by the schema-parity Pester test in .github/scripts/Tests/subagent-env-handshake.Tests.ps1.

Subagent contract — match / mismatch / error / missing-handshake

When a dispatched subagent loads, its first action (before shared-body load, before any tree-grounded claim) is:

1. Parse the <!-- subagent-env-handshake v1 --> block from the dispatch prompt. If absent → missing-handshake path.
2. Run live git verification via Bash:
   • git rev-parse HEAD
   • git rev-parse --abbrev-ref HEAD
   • pwd
   • LF-normalized SHA-256 :12 of git status --porcelain
3. If any of those commands exits non-zero (covers git binary missing, repo-outside, permission errors uniformly) → error path.
4. If workspace_mode is worktree → error path (reserved in v1).
5. Compare observed to handshake field-by-field.

Match path

All four working-tree fields match. The subagent proceeds to shared-body load / role work with no environmental caveat. Tree-grounded findings carry implicit environmental consistency because the handshake matched.

Mismatch path (ND-2 default: halt)

One or more of parent_head, parent_branch, parent_cwd, parent_dirty_fingerprint differs. The subagent emits exactly one finding using the template below verbatim and halts role work. No tree-grounded claims are produced on this dispatch.

## Finding: environment-divergence (halting)

**Expected (from parent handshake):**

- HEAD: {parent_head}
- branch: {parent_branch}
- CWD: {parent_cwd}
- dirty fingerprint: {parent_dirty_fingerprint}

**Observed (live git verification):**

- HEAD: {observed_head}
- branch: {observed_branch}
- CWD: {observed_cwd}
- dirty fingerprint: {observed_dirty_fingerprint}

**Diverged fields:** {comma-separated list}

The subagent halted role work because its live environment does not match
the parent's dispatched handshake. No tree-grounded claims are emitted
on this dispatch. The parent session should reconcile the divergence
(e.g., commit pending edits, re-dispatch from the intended branch, or
explicitly acknowledge the mismatch) and re-dispatch.

Error path (unverified)

Handshake block is missing, unparseable, or any live-verification command returned non-zero, OR workspace_mode is worktree. The subagent MAY proceed with role work but MUST tag every tree-grounded finding with environment-unverified. Non-tree-grounded findings (claims sourced from the task description, passed-in content, or non-tree web/file lookups) remain untagged.

Tree-grounded vs non-tree-grounded findings

The error-path tag applies only to tree-grounded findings. The distinction:

• Tree-grounded finding — any claim whose truth depends on the current working-tree state. Canonical forms: "file X exists / does not exist at path P", "branch is Y", "commit Z landed / is not in this branch", "file F currently contains Q". These require live git / filesystem verification against the parent's tree.
• Non-tree-grounded finding — a claim sourced from the dispatch prompt's task description, from passed-in document content, from a web fetch, or from reasoning that does not reference the working tree. Example: "the proposed API in the spec document has inconsistent field naming." These are unaffected by <env> staleness.

Subagent authors: if a finding would read the same whether the subagent was looking at the parent's tree or a stale snapshot, it is non-tree-grounded. Otherwise assume tree-grounded and tag accordingly in the error path.

Parent-side construction — three helper forms

The SKILL exposes three carriers for block construction. Choose the form that fits your caller:

1. Get-FreshHandshake (canonical capture-then-construct entry point): skills/subagent-env-handshake/scripts/New-SubagentDispatchPrompt.ps1. Dot-source and call Get-FreshHandshake to live-capture all four fields and produce a ready-to-prepend block in one call. Captures parent_head, parent_branch, and parent_dirty_fingerprint via git -C $RepoRoot invocations; captures parent_cwd via bash -c 'pwd' from the caller's working directory (not from RepoRoot). Override params (-HeadShaOverride, -BranchOverride, -CwdOverride, -PorcelainOutput) enable DI-based testing without Pester Mock. Use this form from PowerShell scripts that control their own dispatch flow.

2. New-SubagentDispatchPrompt (explicit-field form): dot-sourceable from the same file. Use when you have already captured the four values via Bash commands and want to pass them explicitly. Deterministic output given fixed inputs; unit-tested for fingerprint stability and field order.

3. Inline prose template (above): construct from Bash values in markdown command files that cannot invoke PowerShell. Field order must match the schema block.

All three forms produce field-identical output for identical inputs. Scenario (f) validates field names and order, and covers Get-FreshHandshake with DI override params.

Per-dispatch recapture policy

Before each downstream Agent dispatch that uses this handshake, the parent MUST construct a fresh block by live-recapturing HEAD (parent_head), branch (parent_branch), CWD (parent_cwd via pwd), and dirty fingerprint (parent_dirty_fingerprint) immediately before that dispatch. Mutable orchestration trees can change between prosecution, defense, judge, and specialist calls, so the parent MUST NOT reuse or carry forward a command-entry, entry-time, single, or earlier handshake for a later Agent dispatch.

Capture ordering

Rule: Capture MUST occur AFTER all parent-side mutations and as close to the Agent dispatch as possible. Capturing before the final round of edits produces a stale dirty fingerprint that diverges from the live state the subagent will observe.

Non-atomicity: The four capture invocations (git rev-parse HEAD, git rev-parse --abbrev-ref HEAD, pwd, git status --porcelain | sha256sum) are separate subprocess calls, not a single atomic snapshot. If the working tree changes between capture commands — for example because an edit tool fires in an interleaved async turn — the fingerprint will be inconsistent with the other fields. This is an inherent property of sequential captures; minimize the window by capturing all four immediately before the parallel emit (see Parallel-batch dispatch).

Counter-example (#429): In the pre-PR hook work (issue #429), the Code-Conductor captured a handshake at command-entry time and then wrote the credit-ledger comment to the branch. The post-write dirty fingerprint diverged from the pre-write fingerprint stored in the handshake, triggering a spurious ND-2 halt on every downstream specialist dispatch in that run. The fix was to move the capture to after the final write, immediately before the Agent call.

If a downstream shell does not yet implement Step 0 environment-handshake verification, the parent may pass freshly captured values only as contextual metadata. Do not label that metadata as a verified handshake.

Parallel-batch dispatch

When a parent emits multiple Agent calls in one parallel tool-use block (for example commands/plan.md and commands/orchestra-review.md prosecution × 3), per-dispatch recapture is satisfied by a single live recapture immediately before the parallel block, with one handshake block constructed per dispatch from those captured values. Each dispatch's handshake block carries its own UTC ISO-8601 handshake_issued_at timestamp; the four parent-side fields (parent_head, parent_branch, parent_cwd, parent_dirty_fingerprint) are field-identical across the batch.

This is consistent with the per-dispatch policy because, while sibling subagents in workspace_mode: shared share the working tree and could theoretically mutate it, our load-bearing guarantee relies on strict subagent working-tree discipline to ensure no tree mutation occurs between members of one parallel tool-use block.

The single-capture-per-batch rule does NOT extend across pipeline stages. Sequential stages (e.g. parallel prosecution → defense → judge in /orchestra:review) MUST recapture between stages because the tree may have mutated. The single-capture-per-batch rule applies only within one parallel tool-use block.

Failure Mode

When subagents dispatched in parallel do not maintain working-tree discipline, they may generate concurrent tree mutations (e.g. redirecting analysis output to files in the repository). In workspace_mode: shared, these untracked files will be visible during other sibling subagents' Step 0 verification, causing a mismatch in the observed dirty fingerprint and triggering a halting environment-divergence finding. See ### Subagent working-tree discipline (under workspace_mode: shared) for the strict discipline that prevents this.

Dispatch sites

We classify all parallel-batch dispatch sites based on whether they are analysis-only (in scope for working-tree discipline) or editor-required (out of scope):

• In-Scope (Analysis-Only):
  • commands/plan.md prosecution × 3 parallel block
  • commands/orchestra-review.md prosecution × 3 parallel block
  • skills/design-exploration/SKILL.md design-challenge × 3 parallel block

Out of scope

• Out-of-Scope (Editor-Parallel):
  • Code-Conductor Execution Mode: parallel Code-Smith ↔ Test-Writer parallel batches (see skills/parallel-execution/SKILL.md § Requirement Contract coordination)
  • Parallel Doc-Keeper batches (see skills/parallel-execution/SKILL.md § Requirement Contract coordination)

Until v2 worktree mode lands, editor-parallel batches under workspace_mode: shared may produce ND-2 cascades equivalent to those described above; there is no documented recovery clause for these batches in v1 — see issue #606 for tracking.

Diagnostic Note

In parallel dispatches, attributing the root cause of an ND-2 halt is limited because multiple subagents execute concurrently. When a halt occurs, the divergent dirty fingerprint indicates that at least one sibling subagent mutated the shared tree, but the system logs might not isolate which specific subagent introduced the mutation.

Forward-Compatibility Note

Future versions of this handshake contract will support workspace_mode: worktree (v2) to run each parallel subagent in an isolated git worktree environment. This structural isolation will completely eliminate inter-subagent tree mutations and the associated ND-2 environment-divergence cascades, removing the reliance on manual working-tree discipline.

Subagent working-tree discipline (under workspace_mode: shared)

To ensure parallel subagent dispatches under workspace_mode: shared do not trigger environment-divergence halts, we establish a strict read-only-during-analysis discipline. Dispatched subagents operating in parallel batches under workspace_mode: shared MUST NOT write or redirect any output to the working tree of this repository during their analysis phase. Any temporary artifacts, logging, or scratch space must be written outside the repository root. For POSIX platforms, subagents should allocate temporary space using mktemp -d or the /tmp directory. For Windows systems, they should use $env:TEMP/$(New-Guid) or the system temp directory. Subagents must avoid using Bash shell redirects (e.g. > or >>) to paths within the working tree, as sibling subagents running in the same parallel block will observe these untracked files during their own Step 0 verification, causing their dirty fingerprints to diverge.

This discipline is a scope: claude-only requirement that complements the Copilot exemption documented under the Copilot exemption clause, as tree-view divergence does not occur in Copilot's sequential or isolated environments. The working-tree discipline is explicitly conditional on workspace_mode: shared because the reserved workspace_mode: worktree (v2) provides complete isolation and eliminates this inter-subagent tree mutation dependency. Furthermore, we maintain a one-line cross-reference to issue #485 for cost-completeness tempfile-exception coordination, ensuring that any allowed tempfile patterns are aligned with this discipline, with temporary files meeting these criteria fully coordinated outside the repository root. Implementing this discipline is consistent with our design intent, and empirical confirmation is gathered via the CE Gate Scenario S1 functional scenario.

Parent-side error handling

If the parent's git invocations fail during construction (non-zero exit on git rev-parse HEAD, etc.), the parent SHOULD skip handshake construction entirely and dispatch without the block. The subagent's error path takes over at that point — tagging tree-grounded findings environment-unverified. The parent is not responsible for emitting the environment-divergence finding; that is the subagent's role on mismatch.

Related

Current adoption guidance: Claude parent surfaces that dispatch tree-dependent subagents MUST adopt this handshake as follows:

1. Parent-side construction: construct the handshake via New-SubagentDispatchPrompt (or the inline prose template) in the dispatch prose, prepended to the Agent tool prompt parameter as its first content.
2. Subagent-side verification: include a ## Step 0: Environment Handshake Verification H2 in the subagent shell (or equivalent first-action section) that executes before shared-body load. The Step 0 prose directs parse → live-verify → branch (match/mismatch/error).
3. ND-2 finding template: quote the ND-2 ## Finding: environment-divergence (halting) template verbatim from the block in this SKILL. Do not paraphrase — the schema-parity test enforces byte parity.

Research or non-tree-dependent dispatches may skip the handshake entirely; opt-in is intentional (ND-3).

Subagent shells that implement Step 0 environment-handshake verification use the same first-action contract. If a downstream shell does not yet implement Step 0 verification, the parent may pass freshly captured values only as contextual metadata per the per-dispatch recapture policy above.

CWD capture (Windows): Always capture parent_cwd using pwd in the Bash tool, not (Get-Location).Path in PowerShell. On Windows, PowerShell produces C:\Users\... while the Bash tool produces /c/Users/...; these formats will never compare equal and will trigger a mismatch halt.

Cross-references:

• Pilot site (this feature): commands/plan.md → agents/issue-planner.md (the only existing real Agent-tool dispatch in the Claude plugin as of 2026-04-20).
• Related plan hygiene: #389 — plugin version bump required for cache invalidation when this skill ships.
• Copilot exemption: scope: claude-only — Copilot's subagent model shares the parent workspace with different tool bindings, so tree-view divergence does not arise. No Copilot-side port is planned.

Gotchas

• CWD format mismatch (Windows): Always capture parent_cwd using pwd in the Bash tool, not (Get-Location).Path in PowerShell. PowerShell produces C:\Users\...; Bash produces /c/Users/.... They will never compare equal and will cause a spurious mismatch halt on every Windows dispatch.
• Detached HEAD: When the parent is in detached-HEAD state, git branch --show-current returns an empty string. parent_branch will be recorded as HEAD (or empty depending on the capture command). The subagent's live branch check must tolerate this — do not assume parent_branch is always a branch name.
• sha256sum availability: sha256sum is not available on macOS by default (use shasum -a 256 instead) and may be absent in some CI images. The parent-side helper must guard against missing commands; on failure, skip dirty-fingerprint construction and dispatch without the field rather than halting the parent.
• Missing-handshake is not an error: Subagents dispatched without a handshake block (research tasks, Copilot dispatch, pre-adoption callers) route to missing-handshake → environment-unverified, not to error. Do not conflate the two paths.
• Schema-parity test enforces byte identity: The Pester contract test verifies that the ## Finding: environment-divergence (halting) block in the verifier stub is byte-identical to the copy in this SKILL.md. If you edit the finding template here, you must update the fixture too (and vice versa), or the test will fail.

• Short-hash or log-based HEAD capture: Using git log -1 --format=%h (short hash) or git log -1 --format=%H when git is configured with log.abbrevCommit=true can produce a short or abbreviated SHA rather than the required 40-char full hex. A short hash will never compare equal to a 40-char parent_head stored in the handshake, causing every dispatch to trigger a spurious mismatch halt. Fix: Always use git rev-parse HEAD (produces exactly 40 hex chars regardless of git config) to capture parent_head, and always compare against the full 40-char hex.

Reproducer Evidence (from design phase)

Pinned from the ND-5 reproducer run during the #383 design phase (2026-04-20). This appendix lives in-repo so the evidence is durably grep-able, not dependent on the rotating GitHub issue timeline.

Original hypothesis (from issue body): the Claude Agent tool spawns subagents against a worktree snapshot taken at conversation start; subagents therefore see a frozen tree that diverges from the parent's live edits.

Reproducer — Claude Code official docs (code.claude.com/docs/en/sub-agents, verified 2026-04-20):

• Line 225 (default dispatch model): "A subagent starts in the main conversation's current working directory. Within a subagent, cd commands do not persist between Bash or PowerShell tool calls and do not affect the main conversation's working directory." → The default is shared live working tree, not a snapshot.
• Line 246 (opt-in isolation): "[isolation: worktree] runs the subagent in a temporary git worktree, giving it an isolated copy of the repository." → Worktree isolation is a frontmatter opt-in, not the default.
• Line 223 (injected env context): "Subagents receive only this system prompt (plus basic environment details like working directory), not the full Claude Code system prompt." → The subagent receives a small <env> block (working dir, branch, status, recent commits) injected once at dispatch time.

In-session parent evidence: the parent session's own injected <env> block captured at conversation start became stale within the session — at dispatch time the <env> said feature/issue-382-runtime-shared-body-enforcement / HEAD a9bc897, while the live git rev-parse HEAD returned feature/issue-383-subagent-env-consistency / HEAD 6bf7aaa. Divergence reproduced live.

Reproduced mechanism: the divergence is not "subagent runs on a snapshot." It is "LLM trusts stale injected <env> context instead of running live git verification." The <env> block is captured once and never refreshes. Any tree-grounded claim the subagent makes that relies on the injected <env> rather than on a live git call will be wrong whenever the parent has switched branches or committed since the <env> was captured.

Why four fields (ND-4), not one: HEAD, branch, CWD, and dirty-tree state each appear in the injected <env> block and each can go stale independently. A handshake that covered only HEAD would miss the CWD-drift and uncommitted-edit failure modes the reproducer exposed.