Forensics · Agent workflow

Reconstruct an agent workflow

Read the ordered assignment, dependency, attempt, action, verification, review, handoff, delivery, and outcome records without turning missing joins into a story.

For: engineers investigating AI-assisted work, reviewers deciding what the evidence establishes, and team owners checking the same record across devices

What it does, and why it helps

The workflow strip projects the case's recorded chain. Inferred edges are labelled, child attempts keep their own exposure state, and pagination preserves attempts beyond the first 500 instead of silently clipping them.

The pain. A flat transcript hides delegation and makes the last visible action look causal.

The point of view. Show the chain and its provenance, then let a person dispute a link.

What gets easier. Finding the handoff, failed dependency, and verification receipt that changed the outcome.

When it helps. A case spans a parent session, subagents, tools, or multiple repositories.

Its limits. Ordering and recorded edges do not prove intent; unavailable source evidence remains unavailable.

Where to find it

Desktop: Today, open a case and its workflow strip; the textual alternative follows the visual chain.
Hosted: /team/agent-incidents, open the same case.
API: GET /api/ai-incidents/detail

When to use it

Follow a failed delegation

Situation. An AI-assisted change needs an answer that another reviewer can reproduce.

What you do. Open Today, select the case, and expand the workflow strip past the parent attempt.

What you see. Each attempt names its parent or says the relationship is inferred, plus its completion and verification state.

What it establishes. The reviewer can point to the exact handoff and receipt rather than cite transcript prose.

Before you start

Supported versions: RepoOps v0.3.1, verified against the 2026-09-17 completion worktree.
Where it runs: The local view needs a tracked repository. The team view needs a bound device and an authenticated team membership.
Permissions: Local evidence follows the repository's own access. Hosted reads are tenant and repository scoped before rows, counts, filters, or exports are built.
Connections: Local inspection works offline. Team delivery needs the device binding and repoops.ai; a failed delivery keeps its cursor and reports the failure.
Plan: Local deterministic analysis is available without a paid runner. Hosted compute, private runners, and model analysis are disabled by default and never silently substituted.

Configure it

Capture the session on its owning machine.
This establishes the scope before any conclusion is computed.
Open the workflow strip and inspect disputed or inferred edges.
The receipt records the decision and the evidence ids it used.

Setting	Where	A sensible choice	Why it matters

ⓘ

To stop or undo

Disable capture to stop new workflow records; existing case evidence is unchanged.

What you should see

A complete recorded chain

Configuration. Use a tracked repository and leave every unknown or disputed input in its real state.

Expect. The strip contains the root, nested attempts, actions, verification, and the final outcome in order.

Verify. The textual alternative names the same nodes and marks inferred edges.

Data and cost

What is captured: Identifiers, timestamps, versioned adapter facts, parent joins, action states, and evidence pointers; no prompt body in the hosted case.
Who can see it: Local detail stays local unless its whitelisted record family is enabled for the team.
How long it is kept: Case lifetime locally and by team/case deletion hosted; related prevention records use the 365-day coherent window.
What leaves the machine: Only enabled, redacted record families cross the device channel.
What it costs: Projection is deterministic and model-free.

When the result differs

Symptom	Likely cause	Next action
A child appears unrelated.	The adapter did not emit a supported parent join.	Read the adapter capability and treat the edge as unsupported or inferred; do not manually relabel it observed.

Disable: Stop the relevant capture or prevention toggle in Settings; already recorded evidence remains a historical record.
Roll back: Restore the earlier package version or withdraw the disputed edge. Append the correction; do not rewrite the earlier decision.
Revoke access: Revoke the device or transcript grant. Later reads become restricted while identifiers and non-secret receipts remain auditable.
Delete: Delete the owning case or team through its deletion flow. Prevention groups also expire coherently after 365 days of inactivity.

Maintenance evidence

Feature id: agent-workflow (spine leaf agent-workflow)
Owner: Forensics runtime and public-story owners (LDG-0695 through LDG-0699, LDG-0722)
Supported product version: RepoOps v0.3.1
Last verified: 2026-09-17
Example fixtures: Deterministic unit and integration fixtures cited by the source modules; external acceptance gates remain named separately.
Source references: lib/agent-workflow-projection.mjs, lib/home-content.mjs, lib/agent-capture-codex.mjs, website/components/incident-workspace-queue.tsx
Documentation review: Claims checked against the implementation and dated evidence. Unknown, disputed, restricted, not-run, and unavailable states are retained.
Video review: No licensed rendered story is published for this guide yet. The guide does not render a placeholder player.

Last updated September 18, 2026