AIYINGFrom AI Awareness to Accomplishment
Showing posts with label Long-Running Agents. Show all posts
Showing posts with label Long-Running Agents. Show all posts

Tuesday, November 17, 2026

AI Agent Harness Engineering: Resume Work with Verified Checkpoints

AIYING · ALL OF AI FOR ALL OF US · HARNESS & LOOP ENGINEERING · C46 — ANNOTATED ARTIFACT #001



How Should an AI Agent Resume Work After a Session Ends?

By Ravindra Dastikop

Give the next session a checkpoint it can verify

A long-running agent needs more than an instruction to “continue.” Its next session should identify the actual workspace, inspect recorded progress, verify the current baseline, and select a bounded next task.

Here, harness means the surrounding software that provides tools, state, execution controls, and lifecycle management. The loop is the repeated cycle of observing, choosing an action, executing it, and checking the result.

Anthropic’s Effective harnesses for long-running agents describes a coding setup using initial environment preparation, progress artifacts, version history, incremental work, and verification at the start of subsequent sessions. Its demonstration concerns web-app development; it does not establish a universal design for every agent.

Our practical adaptation: a checkpoint that points to evidence instead of asking the next session to trust a narrative summary.

Example: the interrupted document-search builder

Imagine an agent building a document-search service. Ingestion works, retrieval is partly implemented, and the session ends before an empty-result case is tested. This is a fictional development scenario.

The next session receives this illustrative checkpoint:

{
  "schema_version": 1,
  "task_id": "retrieval-04",
  "workspace_revision": "record-the-actual-commit-id",
  "status": "in_progress",
  "completed": ["Local fixture ingestion verified"],
  "last_check": {
    "name": "retrieval_smoke",
    "result": "passed",
    "evidence": "artifacts/run-042/retrieval-smoke.txt"
  },
  "unverified": ["Empty-result behaviour"],
  "next_action": "Test a query with no matching documents",
  "stop_condition": "Pause if the baseline check fails"
}

These field names are an example design, not an SDK standard. Replace the revision placeholder with the actual commit identifier. Evidence paths must point to artifacts your harness really preserved.

What the checkpoint tells the next session
Field How to use it
workspace_revision Compare with the actual revision and inspect uncommitted changes. A commit ID alone does not describe a dirty workspace.
last_check Inspect the saved evidence and rerun the relevant baseline. A previous pass does not prove the present state works.
unverified Keep incomplete verification visible instead of treating implementation as completion.
next_action / stop_condition Bound the next increment and define when the loop should pause.

Run one controlled resume drill

  1. Prepare: use a disposable checkout with a small fixture. Preserve a checkpoint, revision, and test evidence through the harness.
  2. Resume: start a fresh session without the previous conversation. Supply the task, normal tool access, and checkpoint location.
  3. Verify: require inspection of the working tree and a baseline check before new edits. If recorded and actual state disagree, surface the mismatch before proceeding.
  4. Advance: complete one bounded task, verify it, and persist an updated checkpoint.
  5. Challenge: in another disposable trial, change the workspace after writing the checkpoint. Check whether the agent detects the stale record.

The harness must explicitly load or retrieve the checkpoint; writing a file does not make it appear automatically in a future context. Persist it through a reliable write mechanism. A hard interruption can occur before a checkpoint is updated, so reconciliation remains necessary.

Do not infer permission for external actions from a progress note. If the workflow can send messages, charge accounts, or change production data, inspect authoritative action records before replaying an interrupted step.

Your turn: If your agent restarted now, what evidence would distinguish “completed,” “attempted,” and “not yet tested”?

Source and scope: Anthropic, Effective harnesses for long-running agents, 26 November 2025; checked 17 November 2026. The checkpoint schema and resume drill are AIYING design proposals, not executed results or a claim of crash-safe production recovery.

AIYING · Ravindra Dastikop
See differently. Generate possibilities. Accomplish what matters.

Accomplish with AI

Powered by Blogger.

Featured post

How do I AI my first attempt? A Practical Guide to Getting Started

AIYING · HOW TO AI · EPISODE 001 How do I AI my first attempt? Turn an unfinished idea into one small version you can exa...

Search This Blog

List of blogs

Search This Blog

About

Translate

Instant Stories

Read in Your Language

Test

share this

ShareThis

Popular Posts