Coding profile

The coding profile is the domain profile for agents that work in a workspace. It covers what an agent did to the workspace: which files changed and how precisely those changes were recorded, which version-control actions happened, the state of each workspace root, and checkpoints. A session that changed nothing can still claim coding: a profile is a promise about what the producer records when things happen, not a statement that they happened (see Extensibility).

`file_change`

A file_change records changes to one or more files, as the source recorded them. Its changes[] array is authoritative and follows the diff structure of Agent Client Protocol (ACP) v2.

{
  "type": "file_change",
  "seq": 12,
  "id": "r12",
  "ts": "2026-10-26T14:02:31.012Z",
  "cause": {"callId": "toolu_01B"},
  "status": "applied",
  "precision": "hunks",
  "changes": [
    {
      "op": "modify",
      "root": "app",
      "path": "crates/parser/src/lib.rs",
      "fileType": "text"
    }
  ],
  "patch": {
    "format": "unified",
    "text": "@@ -41,1 +41,1 @@\n-        return Err(Error::Empty);\n+        return Ok(Vec::new());\n"
  }
}

{
  "type": "file_change",
  "seq": 205,
  "id": "r205",
  "cause": {"callId": "call_W2"},
  "status": "applied",
  "precision": "exact",
  "changes": [
    {
      "op": "add",
      "root": "repo",
      "path": "docs/parser.md",
      "fileType": "text",
      "after": {
        "objectId": "3b18e512dba79e4c8300dd08aeb37f8e728b8dad",
        "objectIdType": "git-blob-sha1",
        "representation": "worktree",
        "size": 12,
        "text": "hello world\n"
      }
    }
  ]
}

Field	Type	Req	Meaning
`cause`	object	no	What made the change (below).
`status`	string, open	yes	`applied`, `proposed`, `partial`, `failed`, `skipped` or `unknown`.
`precision`	string	yes	`exact`, `hunks`, `snippet` or `unknown` (below).
`changes`	array	yes	One entry per file (below). Authoritative.
`patch`	object	no	`{format, text? \| blob?}`: a patch for the changes.
`basis`	string, open	no	`net`: the record states the net difference between two states of the workspace (for example between two checkpoints), not one operation. Absent means not stated.
`endpoints`	object	no	`{from?, to?}`: refs to the records of the two states a `net` change lies between (for example two `checkpoint` records), when the source records them.
`moreFiles`	boolean	no	`true`: the source records that more files changed than `changes` lists.
`modifiedByUser`	boolean	no	`true`: the user edited the proposed change before it was applied (Claude Code’s `userModified`).

Capture state key: patch. ASR-450 A file_change MUST contain status, precision and a non-empty changes array. Status meanings:

Value	Meaning
`applied`	The source records the change as made (a successful edit result, an observed file change).
`proposed`	The change was shown or requested but is not known to have been made (for example while awaiting permission).
`partial`	Part of the change was made.
`failed`	The source records that the change failed.
`skipped`	A requested change was intentionally not made (for example a restore that skipped a file that had changed in the meantime).
`unknown`	The outcome is not known.

ASR-451 status MUST reflect the source’s evidence. A producer MUST NOT write applied when the source shows only a request or a proposal.

Cause

Form	Meaning
`{"callId": "<id>"}`	The tool call that made the change.
`{"actor": "human", "observed": true}`	A person changed the file outside the agent, and the source observed it. `actor` may also be `harness`, `hook`, or `external` (someone or something outside the agent that the source does not identify, as with Claude Code’s notice that a file changed on disk).
`{"restore": "<ref>"}`	A restoration requested by the referenced `rewind` or `checkpoint` record.

ASR-452 cause MUST contain exactly one of callId, actor or restore. When it contains actor, it MUST contain observed: true; a producer MUST NOT attribute a change to a person without the source’s observation, and uses external when the source observed a change without saying who made it. ASR-453 cause.callId SHOULD match the callId of a tool_call in the stream. cause.restore MUST resolve to a rewind or checkpoint record.

Changes

Field	Type	Req	Meaning
`op`	string, open	yes	`add`, `delete`, `modify`, `move`, `copy` or `unknown`.
`root`	string or null	yes	Root ID, or `null` for a file outside every root.
`path`	string	yes	The file’s path (see Path encoding); for `move` and `copy`, the destination.
`nativePath`	string	no	The native spelling, when it differs.
`oldRoot`	string or null	no	For `move` and `copy`, the source root when it differs from `root`.
`oldPath`	string	depends	For `move` and `copy`, the source path.
`fileType`	string, open	no	`text`, `binary`, `directory` or `symlink`.
`mimeType`	string	no	Media type of the content.
`before`	object	no	The file state before the change (below).
`after`	object	no	The file state after the change (below).

ASR-454 Each change MUST contain op, root and path. A move or copy MUST contain oldPath. unknown requires evidence that a change occurred without a known operation. A first observed file version is a checkpoint, not evidence of a change.

Precision

precision says how completely the record determines the change, independently of which hashes or blobs are present.

Value	Meaning
`exact`	For every change, the after state is fully determined: complete content (`after.text` or `after.content`) or an object ID for added, modified or copied files; nothing further for deletions and pure moves.
`hunks`	Diff hunks for the changed regions (a unified diff, a Git patch, or structured hunks rendered as one), without complete file content.
`snippet`	Only an edit snippet: replaced and replacement text, without positions or enough context to form hunks.
`unknown`	The record does not hold the change content.

ASR-455 precision MUST be the least precise level among the record’s changes, in the order exact, hunks, snippet, unknown. A producer MUST NOT claim more precision than the source supports; an edit recorded only as replaced and replacement strings is snippet.

Patch

`format`	Meaning
`git_patch`	Git `--patch` text, possibly for several files, as used by ACP v2.
`unified`	Unified-diff hunks for a single file.

ASR-456 patch MUST contain format and exactly one of text or blob. unified MUST be used only when changes has exactly one entry. changes is authoritative: a patch MUST be consistent with it, and where they disagree readers MUST follow changes. Paths inside patch text are kept as the source wrote them (ACP v2 patches use absolute paths). Root substitution (writing a root ID and a relative path in place of an absolute path) does not apply to them.

File states and object IDs

Field	Type	Meaning
`objectId`	string	A content hash of the file, as lowercase hex.
`objectIdType`	string	`git-blob-sha1`, `git-blob-sha256` or `sha256`.
`representation`	string	`worktree` (the bytes in the working-tree file) or `git_object` (the bytes as stored in the repository, after clean filters such as line-ending normalization or large-file pointers).
`size`	integer	Size in bytes of the hashed representation.
`text`	string	The content, inline, for text files.
`content`	BlobRef	The content as a blob.

ASR-457 A file state with objectId MUST have objectIdType, and the object ID MUST be 40 lowercase hex digits for git-blob-sha1 and 64 for the others. A file state MUST NOT contain both text and content. ASR-458 Object IDs MUST be computed as follows: git-blob-sha1 is the SHA-1 of the Git blob framing (blob, a space, the size in decimal, a NUL byte, then the bytes); git-blob-sha256 is the same framing hashed with SHA-256; sha256 is the SHA-256 of the bytes alone. ASR-459 An object ID read from a repository (an index entry, a tree, a commit) MUST be labeled git_object. A producer MUST NOT relabel it as worktree, because clean filters can make the two differ. representation SHOULD be present whenever objectId is. ASR-460 A producer MUST NOT hash a file’s current content and record it as a historical before or after state unless it observed that content at the edit boundary (for example a native writer hashing the file immediately after its own edit). ASR-461 Object IDs are optional (SHOULD, where the producer has them). Consumers MUST NOT require them. Precision and artifact availability are independent: a hunks change needs no object ID, and exact content needs no hash. ASR-462 A matching object ID between a recorded after state and a committed file is strong evidence for attribution, not proof that the session caused the commit. Consumers MUST NOT present it as proof of causation.

Net changes and incomplete lists

T3 Code records the files a turn changed as the difference between the checkpoints before and after the turn. Such a record overlaps the records of the individual edits in that turn.

{
  "type": "file_change",
  "seq": 160,
  "id": "r160",
  "turnId": "run:thread:5b2f0c4e-1111-4a2b-9c3d-000000000001:ordinal:3",
  "basis": "net",
  "endpoints": {"from": "r121", "to": "r159"},
  "status": "applied",
  "precision": "unknown",
  "changes": [
    {
      "op": "modify",
      "root": "app",
      "path": "crates/parser/src/lib.rs",
      "fileType": "text"
    },
    {
      "op": "add",
      "root": "app",
      "path": "crates/parser/tests/empty.rs",
      "fileType": "text"
    }
  ]
}

ASR-474 Consumers MUST NOT add a file_change with basis: "net" to the changes of the operations it spans, and MUST NOT count the files it lists again. endpoints refs, when present, MUST resolve to records with a lower seq. ASR-475 moreFiles and modifiedByUser MUST come from the source. When moreFiles is true, consumers MUST NOT treat changes as the complete list of changed files.

`vcs`

A vcs record describes a version-control action performed in the session, such as a commit, a push, a checkout or opening a pull request.

{
  "type": "vcs",
  "seq": 20,
  "id": "r20",
  "ts": "2026-10-26T14:03:02.877Z",
  "action": "commit",
  "root": "app",
  "commitPrefix": "8e2f4a6",
  "branch": "main",
  "cause": {"callId": "toolu_01D"},
  "evidence": "parsed_output"
}

{
  "type": "vcs",
  "seq": 214,
  "id": "r214",
  "ts": "2026-10-26T15:07:44.210Z",
  "action": "pr_open",
  "root": "repo",
  "branch": "fix/parser-empty",
  "pr": {
    "url": "https://github.com/acme/app/pull/482",
    "number": 482,
    "repository": "acme/app"
  },
  "cause": {"callId": "call_Y7"},
  "evidence": "observed"
}

The first record was parsed from the output of git commit, which prints an abbreviated commit ID, so only commitPrefix is known.

Field	Type	Req	Meaning
`action`	string, open	yes	`commit`, `amend`, `push`, `checkout`, `branch_create`, `merge`, `rebase`, `cherry_pick`, `revert`, `reset`, `pr_open`, `pr_update`, `pr_merge`, `pr_comment`, `pr_close`, `pr_reopen`, `pr_ready`, `pr_draft` or `pr_link`.
`root`	string	no	The root the action applies to.
`commit`	string	no	The resulting (or affected) commit’s full object ID.
`commitPrefix`	string	no	An abbreviated commit ID, when only that is known.
`parents`	string[]	no	Full IDs of the commit’s parents.
`branch`	string	no	Branch name.
`remote`	string	no	Remote name or URL, as recorded.
`pr`	object	no	`{url?, number?, repository?}` for pull request actions.
`cause`	object	no	`{callId}` or `{actor, observed: true}`, as for `file_change`.
`evidence`	string, open	yes	`observed`, `parsed_output` or `reported` (below).

Evidence	Meaning
`observed`	The source observed the action and its result directly: its own VCS integration, a repository hook, or a tool’s structured result that the tool itself produced.
`parsed_output`	The result was parsed from a command’s output text, by the producer or by the source itself (Claude Code parses `git` output into its own structured field).
`reported`	The source recorded the association without showing how it was established (for example a stored pull request link).

pr_ready marks a draft pull request ready for review; pr_draft turns it back into a draft. pr_link is not an action: it records that the source linked the session to a pull request (Claude Code’s pr-link, T3 Code’s pull request links), without saying that the session opened it.

{
  "type": "vcs",
  "seq": 219,
  "id": "r219",
  "ts": "2026-10-26T15:09:12.003Z",
  "action": "pr_link",
  "root": "app",
  "pr": {
    "url": "https://github.com/acme/app/pull/482",
    "number": 482,
    "repository": "acme/app"
  },
  "evidence": "reported"
}

ASR-463 A vcs record MUST contain action and evidence. commit and every element of parents MUST be 40 or 64 lowercase hex digits; commitPrefix MUST be 4 to 39 lowercase hex digits; a record MUST NOT contain both commit and commitPrefix. ASR-464 A producer MUST write vcs records only for actions performed in the session (by its tool calls, its harness, or observed in its workspace while it ran), and for links to pull requests that the source records (pr_link). A commit or pull request merely mentioned in content is not a vcs record, and consumers MUST NOT treat a mention as evidence that the session produced it. ASR-465 evidence MUST say how the producer knows: a value parsed from command output MUST be parsed_output, not observed, whether the producer or the source parsed it. ASR-476 A pr_link record MUST have evidence: "reported". Consumers MUST NOT treat a pr_link as evidence that the session opened, changed or merged the pull request.

`workspace_state`

A workspace_state records the state of a root when the source records a change to that state: a new HEAD, a branch switch, the working tree becoming dirty or clean, or a new working directory.

{
  "type": "workspace_state",
  "seq": 215,
  "id": "r215",
  "ts": "2026-10-26T15:07:44.902Z",
  "root": "repo",
  "head": "8e2f4a6c1b3d5e7f9a0b2c4d6e8f1a3b5c7d9e0f",
  "branch": "fix/parser-empty",
  "dirty": false
}

Field	Type	Req	Meaning
`root`	string	depends	Root ID. Required unless `cwd` is present.
`cwd`	PathRef	no	The agent’s working directory from this point on.
`head`	string	no	Full commit ID of HEAD.
`branch`	string	no	Current branch.
`detached`	boolean	no	HEAD is detached.
`dirty`	boolean	no	The working tree has uncommitted changes.
`dirtyPaths`	string[]	no	Root-relative paths with uncommitted changes.
`worktree`	object	no	`{linked?, name?}`: whether the root is a linked worktree, and its name.

ASR-466 A workspace_state MUST contain root or cwd, and its members MUST come from the source (ASR-159 applies). head follows the format of vcs.commit.

{
  "type": "workspace_state",
  "seq": 61,
  "id": "r61",
  "ts": "2026-10-26T14:11:02.418Z",
  "cwd": {"root": "app", "path": "crates/parser"}
}

`checkpoint`

A checkpoint records a snapshot the source took of workspace files, typically so that a rewind can restore them: a commit in a shadow repository (a separate repository used for snapshots), a commit under a hidden ref in the workspace’s own repository, a snapshot ID, a stash.

{
  "type": "checkpoint",
  "seq": 13,
  "id": "r13",
  "kind": "snapshot",
  "ref": "b7e1c9d4-2f3a-4e5b-8c6d-7a9f0e1b2c3d",
  "root": "app",
  "files": [
    {
      "root": "app",
      "path": "crates/parser/src/lib.rs",
      "version": "1",
      "blob": {
        "blob": "sha256:7a3c9e1f5b2d8a4c6e0f1b3d5a7c9e2f4b6d8a0c1e3f5b7d9a2c4e6f8b0d1a3c",
        "size": 4127,
        "mimeType": "text/plain"
      }
    }
  ],
  "cause": {"callId": "toolu_01B"}
}

{
  "type": "checkpoint",
  "seq": 159,
  "id": "r159",
  "turnId": "run:thread:5b2f0c4e-1111-4a2b-9c3d-000000000001:ordinal:3",
  "kind": "git_ref",
  "ref": "refs/t3/orchestration-v2/checkpoints/9c1e7a42",
  "root": "app",
  "status": "missing",
  "files": ["crates/parser/src/lib.rs", "crates/parser/tests/empty.rs"]
}

The second record comes from a T3 Code thread. T3 Code keeps checkpoints as commits under hidden refs; this one was no longer present when the source last checked.

Field	Type	Req	Meaning
`kind`	string, open	yes	`shadow_git`, `git_ref` (a commit under a ref in the workspace’s own repository), `snapshot`, `vcs_stash` or `other`.
`ref`	string	yes	The checkpoint’s native identifier.
`root`	string	no	Root ID.
`status`	string, open	no	`ready` (available), `missing` (unavailable), `error` (checkpoint operation failed) or `stale` (outdated). Unmapped native statuses go in `native` or `_meta` (ASR-619).
`files`	array	no	The files covered: root-relative paths, or PathRef objects `{root, path, nativePath?, version?, blob?}` when the source keeps a version or a backup of each file.
`cause`	object	no	`{callId}` when a tool call triggered it.
`label`	string	no	A label, as recorded.

ASR-467 A checkpoint MUST contain kind and ref. Each element of files MUST be a root-relative string or a PathRef object with root and path; version, when present, MUST be a string or nonnegative safe integer (ASR-042), and blob MUST be a BlobRef.

Path encoding

ASR uses one structured path encoding everywhere a path is a field: file_change changes, exec.cwd, tool_call.locations, instructions.source, terminal.cwd, workspace_state.cwd, plan.source, memory_change.target.path, config_change.sandbox.writableRoots and checkpoint file objects.

{"root": "app", "path": "crates/parser/src/lib.rs"}

Field	Type	Req	Meaning
`root`	string or null	yes	A root ID, or `null` for a path outside every root.
`path`	string	yes	Relative to the root when `root` is set; absolute when `root` is `null`.
`nativePath`	string	no	The native spelling, when it differs from `path`.

ASR-468 root, when not null, MUST name a root declared earlier in the stream (ASR-166). ASR-469 When root is not null, path MUST be a relative path with / separators: it MUST NOT begin with /, MUST NOT contain empty, . or .. segments, and is exactly . for the root itself. ASR-470 When root is null, path MUST be absolute, with / separators: /srv/data/x, a drive form such as C:/Users/x, or a UNC form such as //server/share/x. ASR-471 When the native spelling differs from path (backslashes, a different absolute form, characters that do not survive conversion), the producer SHOULD record it in nativePath. Producers MUST NOT resolve symbolic links, change case or apply Unicode normalization to path. ASR-477 A producer SHOULD decode a native file: URI to a path using the source’s own rules for URIs, including authorities and Windows conventions, and keep the original URI in nativePath. It MUST NOT guess using the path rules of the machine the export runs on. When decoding is uncertain, it MUST keep the native evidence rather than invent a normalized path. A producer SHOULD express a path relative to a root whenever the native absolute path lies inside a declared root. ASR-472 Root substitution applies only to path fields. Paths inside tool inputs, commands, output text, patches and content MUST be kept exactly as the source wrote them. Consumers and redaction tools MUST NOT assume that a stream with redacted roots contains no absolute paths. ASR-473 A native path that is not valid UTF-8 cannot be represented exactly. The producer MUST replace invalid byte sequences with U+FFFD and MUST declare the loss path.encoding.

Introduction

Format

Records

Trust

Extending and conforming

Agent registry

`file_change`

Cause

Changes

Precision

Patch

File states and object IDs

Net changes and incomplete lists

`vcs`

`workspace_state`

`checkpoint`

Path encoding

​file_change

​Cause

​Changes

​Precision

​Patch

​File states and object IDs

​Net changes and incomplete lists

​vcs

​workspace_state

​checkpoint

​Path encoding

`file_change`

Cause

Changes

Precision

Patch

File states and object IDs

Net changes and incomplete lists

`vcs`

`workspace_state`

`checkpoint`

Path encoding