@selesai/code 0.13.9 → 0.13.11

package/docs/rpc.md

@@ -64,6 +64,14 @@ With images:
 
 If the agent is streaming and no `streamingBehavior` is specified, the command returns an error.
 
+**During compaction**: If the agent is compacting, the command is rejected unless `queueWhileCompacting` is set:
+
+```json
+{"type": "prompt", "message": "Follow-up", "queueWhileCompacting": true}
+```
+
+With `queueWhileCompacting: true` the prompt is accepted into a buffer (`success: true` is returned immediately) and auto-replayed in order after `compaction_end`. If compaction aborts or errors, the buffer is discarded.
+
 **Extension commands**: If the message is an extension command (e.g., `/mycommand`), it executes immediately even during streaming. Extension commands manage their own LLM interaction via `pi.sendMessage()`.
 
 **Input expansion**: Skill commands (`/skill:name`) and prompt templates (`/template`) are expanded before sending/queueing.
@@ -240,6 +248,14 @@ Cycle to the next available model. Returns `null` data if only one model availab
 {"type": "cycle_model"}
 ```
 
+Optional `direction` (defaults to `"forward"`):
+
+```json
+{"type": "cycle_model", "direction": "backward"}
+```
+
+`direction` is `"forward"` or `"backward"`.
+
 Response:
 ```json
 {
@@ -264,6 +280,12 @@ List all configured models.
 {"type": "get_available_models"}
 ```
 
+Optional `refresh` flag (TUI parity) re-fetches model catalogs before listing; a small timeout applies and the current snapshot is used if the network refresh fails:
+
+```json
+{"type": "get_available_models", "refresh": true}
+```
+
 Response contains an array of full [Model](#model) objects:
 ```json
 {
@@ -556,6 +578,11 @@ With custom path:
 {"type": "export_html", "outputPath": "/tmp/session.html"}
 ```
 
+Optional `themeName` selects the export theme (otherwise the current theme is used):
+```json
+{"type": "export_html", "outputPath": "/tmp/session.html", "themeName": "dark"}
+```
+
 Response:
 ```json
 {
@@ -702,6 +729,134 @@ Response:
 
 The current session name is available via `get_state` in the `sessionName` field. To set the initial name when starting RPC mode, pass `--name <name>` or `-n <name>` to the `pi --mode rpc` process.
 
+#### navigate_tree
+
+Navigate the session tree to a different entry (the TUI tree selector equivalent). Rejects while the agent is streaming; emits a `session_tree` event on success.
+
+```json
+{"type": "navigate_tree", "targetId": "abc123"}
+```
+
+Optional fields:
+- `summarize`: summarize the branch between the old leaf and the target before navigating.
+- `customInstructions`: custom summary instructions (with `summarize`).
+- `replaceInstructions`: replace (rather than append to) the default summary instructions.
+- `label`: attach the given label to the target entry.
+
+Response:
+```json
+{
+  "type": "response",
+  "command": "navigate_tree",
+  "success": true,
+  "data": {
+    "editorText": "...",
+    "cancelled": false,
+    "aborted": false,
+    "summaryEntry": null
+  }
+}
+```
+
+`editorText` is present when the target is a user message (it becomes the editor prefill). `aborted` is set when a `session_before_navigate`-style extension handler cancels the navigation. Fails with `Entry <id> not found` for unknown targets and `No model available for summarization` when `summarize` is requested but no model is configured.
+
+#### list_sessions
+
+List sessions. `scope` defaults to `"current"` (sessions in the current cwd/session dir); `"all"` searches the full session store.
+
+```json
+{"type": "list_sessions"}
+{"type": "list_sessions", "scope": "all"}
+```
+
+Response:
+```json
+{
+  "type": "response",
+  "command": "list_sessions",
+  "success": true,
+  "data": {
+    "sessions": [
+      {
+        "path": "/path/to/session.jsonl",
+        "id": "abc123",
+        "cwd": "/path/to/project",
+        "name": "my-feature-work",
+        "parentSessionPath": null,
+        "created": "2026-09-01T00:00:00.000Z",
+        "modified": "2026-09-01T01:00:00.000Z",
+        "messageCount": 42,
+        "firstMessage": "First user prompt..."
+      }
+    ]
+  }
+}
+```
+
+`name` is omitted when unset. `created`/`modified` are ISO strings; sessions with invalid timestamps (e.g. hand-written JSONL) are reported as epoch (`1970-01-01T00:00:00.000Z`).
+
+#### rename_session
+
+Rename a session by writing the name into its JSONL header. The file must exist; an empty name is rejected.
+
+```json
+{"type": "rename_session", "path": "/path/to/session.jsonl", "name": "my-feature-work"}
+```
+
+Response: `{"command": "rename_session", "success": true, "data": {"path": "/path/to/session.jsonl", "name": "my-feature-work"}}`
+
+#### delete_session
+
+Delete a session. Moves it to the operating system trash when available, else unlinks the file directly. Refuses to delete the currently active session.
+
+```json
+{"type": "delete_session", "path": "/path/to/session.jsonl"}
+```
+
+Response: `{"command": "delete_session", "success": true, "data": {"path": "/path/to/session.jsonl", "method": "trash"}}`
+
+`method` is `"trash"` or `"unlink"`.
+
+#### set_session_models
+
+Scope the session to a subset of models (mirrors the TUI session-only model scoping). Ephemeral: never writes settings files and does not affect the persistent scoped-model configuration. Pass an empty array to clear the session scope.
+
+```json
+{"type": "set_session_models", "enabled": ["anthropic/claude-sonnet-4-20250514", "anthropic/*"]}
+```
+
+`enabled` entries are concrete `provider/id` identifiers or scope/wildcard patterns (e.g. `"anthropic/*"`). `reorder` (a reordered pattern list) rebuilds the scope without changing which models are enabled. At least one of the two must be present.
+
+Response:
+```json
+{
+  "type": "response",
+  "command": "set_session_models",
+  "success": true,
+  "data": {
+    "enabled": ["anthropic/claude-sonnet-4-20250514"],
+    "models": [{...}]
+  }
+}
+```
+
+`enabled` is the resolved list of `provider/id` strings; `models` is the matching array of [Model](#model) objects.
+
+#### share_gist
+
+Export the session to HTML and share it as a private GitHub gist (requires the GitHub CLI authenticated via `gh auth login`).
+
+```json
+{"type": "share_gist"}
+```
+
+Optional `themeName` selects the export theme:
+```json
+{"type": "share_gist", "themeName": "dark"}
+```
+
+Response: `{"command": "share_gist", "success": true, "data": {"url": "https://github.com/user/...", "gistUrl": "https://gist.github.com/..."}}`
+
 ### Commands
 
 #### get_commands
@@ -742,6 +897,38 @@ Each command has:
 
 **Note**: Built-in TUI commands (`/settings`, `/hotkeys`, etc.) are included with `source: "builtin"` and `interactiveOnly: true`. They are display-only: they are handled only in interactive mode and would not execute if sent via `prompt`.
 
+#### get_skills
+
+Get the resolved skill catalog (one entry per discovered skill with its effective enablement) plus the raw `settings.skills` patterns for round-trip toggling. Enables the extension to mirror the TUI `/skills` toggle surface without reimplementing `isEnabledByOverrides` semantics.
+
+```json
+{"type": "get_skills"}
+```
+
+Response:
+```json
+{
+  "type": "response",
+  "command": "get_skills",
+  "success": true,
+  "data": {
+    "skills": [
+      {"name": "fix-tests", "description": "Fix failing tests", "scope": "global", "pattern": "fix-tests", "enabled": true}
+    ],
+    "patterns": ["+fix-tests", "-legacy-skill"]
+  }
+}
+```
+
+Each skill entry has:
+- `name`: Skill name (frontmatter `name`, falling back to the SKILL.md parent directory name)
+- `description`: Frontmatter description (optional)
+- `scope`: `"global"` (user-level) or `"project"` (project-level)
+- `pattern`: Path relative to the skill base dir — the same pattern the TUI writes as `+pattern`/`-pattern` into `settings.skills`
+- `enabled`: Resolved enablement per `isEnabledByOverrides` semantics (package-manager.ts)
+
+`patterns` is the raw merged `global + project` `settings.skills` array. To toggle a skill, write `set_settings {scope, values:{skills:[...]}}` with `+pattern`/`-pattern` entries applied, then send `reload` (the TUI reloads after every toggle).
+
 ## Events
 
 Events are streamed to stdout as JSON lines during agent operation. Events do not generally include an `id` field; `bash_execution_update` includes the `id` of its originating `bash` command when one was provided.
@@ -766,6 +953,7 @@ Events are streamed to stdout as JSON lines during agent operation. Events do no
 | `compaction_end` | Compaction completes |
 | `auto_retry_start` | Auto-retry begins (after transient error) |
 | `auto_retry_end` | Auto-retry completes (success or final failure) |
+| `session_tree` | Session tree navigated (new leaf, old leaf, optional summary entry) |
 | `extension_error` | Extension threw an error |
 
 ### agent_start
@@ -957,6 +1145,20 @@ If compaction was aborted, `result` is `null` and `aborted` is `true`.
 
 If compaction failed (e.g., API quota exceeded), `result` is `null`, `aborted` is `false`, and `errorMessage` contains the error description.
 
+### session_tree
+
+Emitted after a `navigate_tree` (or an extension-initiated tree navigation) moves the session to a new leaf. `oldLeafId`/`newLeafId` are the session tree leaves before and after the navigation; `summaryEntry` is present when the navigation summarized the branch. `fromExtension` is true when the navigation was initiated by an extension.
+
+```json
+{
+  "type": "session_tree",
+  "oldLeafId": "def456",
+  "newLeafId": "abc123",
+  "summaryEntry": null,
+  "fromExtension": false
+}
+```
+
 ### auto_retry_start / auto_retry_end
 
 Emitted when automatic retry is triggered after a transient error (overloaded, rate limit, 5xx).
@@ -1009,13 +1211,13 @@ Extensions can request user interaction via `ctx.ui.select()`, `ctx.ui.confirm()
 There are two categories of extension UI methods:
 
 - **Dialog methods** (`select`, `multiselect`, `confirm`, `input`, `editor`): emit an `extension_ui_request` on stdout and block until the client sends back an `extension_ui_response` on stdin with the matching `id`.
-- **Fire-and-forget methods** (`notify`, `setStatus`, `setWidget`, `setTitle`, `set_editor_text`): emit an `extension_ui_request` on stdout but do not expect a response. The client can display the information or ignore it.
+- **Fire-and-forget methods** (`notify`, `setStatus`, `setWidget`, `setTitle`, `set_editor_text`, `working`): emit an `extension_ui_request` on stdout but do not expect a response. The client can display the information or ignore it.
 
 If a dialog method includes a `timeout` field, the agent-side will auto-resolve with a default value when the timeout expires. The client does not need to track timeouts.
 
 Some `ExtensionUIContext` methods are not supported or degraded in RPC mode because they require direct TUI access:
 - `custom()` returns `undefined`
-- `setWorkingMessage()`, `setWorkingIndicator()`, `setFooter()`, `setHeader()`, `setEditorComponent()`, `setToolsExpanded()` are no-ops
+- `setWorkingMessage()`, `setWorkingVisible()`, `setWorkingIndicator()` emit a `working` extension_ui_request (see below); `setFooter()`, `setHeader()`, `setEditorComponent()`, `setToolsExpanded()` are no-ops
 - `getEditorText()` returns `""`
 - `getToolsExpanded()` returns `false`
 - `pasteToEditor()` delegates to `setEditorText()` (no paste/collapse handling)
@@ -1187,6 +1389,28 @@ Set the text in the input editor. Fire-and-forget.
 }
 ```
 
+#### working
+
+Control the streaming "working" loader row. Fire-and-forget; the host renders the loader. This mirrors the TUI's `setWorkingMessage()` / `setWorkingVisible()` / `setWorkingIndicator()` extension methods.
+
+```json
+{
+  "type": "extension_ui_request",
+  "id": "uuid-10",
+  "method": "working",
+  "message": "Analyzing repository...",
+  "visible": true,
+  "frames": ["⠋", "⠙", "⠹"],
+  "intervalMs": 80
+}
+```
+
+Fields (all optional, applied as a patch):
+- `message`: phase text shown next to the loader. Omit to keep (or restore to default).
+- `visible`: show/hide the loader row.
+- `frames`: custom animation frames for the normal streaming loader. An empty array hides the indicator; omitting restores the default spinner. Compaction/retry loaders keep their built-in styling.
+- `intervalMs`: frame interval in milliseconds for animated indicators.
+
 ### Extension UI Responses (stdin)
 
 Responses are sent for dialog methods only (`select`, `multiselect`, `confirm`, `input`, `editor`). The `id` must match the request.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@selesai/code",
-  "version": "0.13.9",
+  "version": "0.13.11",
   "description": "Maintained, extension-first Pi coding agent with built-in workflows, subagents, web research, questions, skills, and an enhanced terminal UI.",
   "type": "module",
   "repository": {

package/dist/extensions/pi-subagents/agents/architect.md

@@ -1,170 +0,0 @@
----
-name: architect
-description: Read-only architecture and implementation planning
-tools: read, grep, find, ls
-acceptanceRole: read-only
-systemPromptMode: replace
-inheritProjectContext: true
-inheritSkills: false
-skill: ponytail, planger
-defaultContext: fork
-output: plan.md
----
-
-## Goal
-
-Create implementation plans that can be executed by a small coding model with:
-
-- Limited context window
-- No project knowledge
-- No memory of previous conversation
-- Weak architectural understanding
-- No ability to infer missing steps
-
-Assume the executor only knows what is written in the plan. Return the complete plan in your final response. The runtime persists it as `plan.md` so the next workflow stage can read it.
-
-# Core Principles
-
-## Discovery First
-
-Never assume:
-
-- File names
-- File locations
-- Ownership of behavior
-- Existing abstractions
-- Existing utilities
-
-If the code has not been inspected, the plan must begin with discovery.
-Inspect the repository directly with your available read/search tools and capture findings and decisions into a comprehensive plan. This iterative approach catches edge cases and non-obvious requirements BEFORE implementation begins. Unresolved user-owned decisions must be listed explicitly in the returned plan; do not try to ask the user questions or launch a child agent to resolve them.
-
-## Simplicity First
-
-Prefer the smallest maintainable solution that satisfies the requirement.
-
-Avoid:
-
-- New abstractions
-- New services
-- New dependencies
-- Large refactors
-- Generic frameworks
-- Future-proofing for hypothetical requirements
-
-Choose the lowest-complexity solution that works.
-
-## Reuse Before Build
-
-Before creating anything new, inspect the repository directly with your read/search tools:
-
-- Search for existing implementations
-- Search for existing utilities
-- Search for existing patterns
-- Search for existing tests
-
-Reuse existing code when reasonable.
-
-Do not duplicate behavior unless duplication is clearly preferable.
-
-## Scope Discipline
-
-Only modify code required for the task.
-
-Allowed:
-
-- Small cleanup in touched files
-- Remove unused imports
-- Remove obvious dead code
-- Improve nearby naming
-
-Not allowed:
-
-- Unrelated refactors
-- Architecture changes
-- Broad cleanup efforts
-- Dependency migrations
-
-# Task Structure
-
-Every implementation task must contain:
-
-## 1. Discovery
-
-Describe:
-
-- What to search for
-- Where to search
-- How to identify relevant code
-
-Example:
-
-Search for:
-
-- Authorization
-- Bearer
-- Interceptor
-- Refresh token
-
-Inspect matching files and identify where authentication headers are attached.
-
-## 2. Identification
-
-Describe:
-
-- Exact file(s) to modify
-- Why those files own the behavior
-- Why other files should not be modified
-
-## 3. Change
-
-Describe:
-
-- Exact modification required
-- Functions/classes affected
-- Existing code to reuse
-- New code to add
-- Code explicitly not to add
-
-The executor should know exactly what to implement.
-
-## 4. Verification
-
-Include:
-
-### Success Cases
-
-Expected working behavior.
-
-### Failure Cases
-
-Expected error behavior.
-
-### Regression Checks
-
-Existing behavior that must remain unchanged.
-
-# Granularity Rule
-
-A task is too large if it can be split into smaller independently verifiable work.
-
-Keep decomposing until each task:
-
-- Has one objective
-- Has clear ownership
-- Can be implemented independently
-- Can be verified independently
-
-Prefer 5 small tasks over 1 large task.
-
-# Final Review
-
-Before returning a plan verify:
-
-- Discovery exists
-- Ownership is justified
-- Solution is the simplest acceptable approach
-- Existing code is reused when possible
-- No unnecessary abstractions are introduced
-- Scope remains limited
-- Verification is included
-- Every step is executable without additional assumptions

package/dist/extensions/pi-subagents/agents/builder.md

@@ -1,37 +0,0 @@
----
-name: builder
-description: Mutation-capable scoped implementation
-acceptanceRole: writer
-thinking: high
-systemPromptMode: replace
-tools: read, grep, find, ls, bash, edit, write
-inheritSkills: false
-skill: ponytail, implanger
-inheritProjectContext: true
-defaultContext: fresh
-output: implementation.md
-defaultReads: context.md, research.md, plan.md, implementation.md, review.md
----
-
-You are `builder`, the sole writer for the delegated task. The main agent and user remain the decision authority. The runtime persists your final report as `implementation.md` for review and fix stages.
-
-Read the supplied task, artifacts, and relevant code before changing anything. Implement the smallest correct change in the active workspace, follow existing patterns, and run focused validation.
-
-Rules:
-- Make only approved, in-scope changes. Do not add speculative scaffolding, placeholders, wrappers, fallback paths, or unrelated refactors.
-- Trace callers when changing shared behavior; fix the shared cause rather than patching one path.
-- If a required product, architecture, or scope decision is not approved: when the injected bridge instructions make `contact_supervisor` available, use it with `reason: "need_decision"` and wait; otherwise stop, do not guess, and report the exact blocking decision in your final response.
-- Do not launch subagents. Do not send routine completion handoffs.
-- Do not claim success without making the requested edits, unless you are blocked and report why.
-- If the task specifies a progress file path, append a `## Round N` entry to that file before finishing (use the round number from the task; if none is given, count existing `## Round` entries and add one). The entry must list every file you changed (`Files:`), a short summary of the work (`Summary:`), and the validation you ran (`Validation:`). If the task names no progress file, skip this.
-
-Before finishing, verify the requirement, changed files, and relevant tests/checks.
-
-Final response:
-
-Implemented: ...
-Progress:
-Files: ... (every file changed)
-Summary: ... (one or two lines on what was done)
-Validation: ... (checks run and outcome)
-Open risks/questions: ...

package/dist/extensions/pi-subagents/agents/claude-code-writer.md

@@ -1,15 +0,0 @@
----
-name: claude-code-writer
-description: Explicit file-writing Claude Code CLI mode; requires local authentication and trusted user settings/hooks
-runner:
-  type: external-cli
-  adapter: claude-code-writer
-  command: claude
-  promptDelivery: stdin
-async: true
-systemPromptMode: replace
-inheritProjectContext: true
-inheritSkills: false
----
-
-Prerequisites: the local Claude Code CLI is authenticated, and the operator trusts its user-level settings and hooks. Use only the code-owned Read, Write, Edit, Glob, and Grep tools. Make the requested file changes, report validation evidence, and do not request wider access.

package/dist/extensions/pi-subagents/agents/claude-code.md

@@ -1,15 +0,0 @@
----
-name: claude-code
-description: Read-only Claude Code CLI analysis; requires local authentication and trusted user settings/hooks
-runner:
-  type: external-cli
-  adapter: claude-code
-  command: claude
-  promptDelivery: stdin
-async: true
-systemPromptMode: replace
-inheritProjectContext: true
-inheritSkills: false
----
-
-Prerequisites: the local Claude Code CLI is authenticated, and the operator trusts its user-level settings and hooks. Analyze only the supplied handoff in no-tools mode. Return a concise final answer with evidence. Do not edit files or request wider access.

package/dist/extensions/pi-subagents/agents/codex-exec-writer.md

@@ -1,15 +0,0 @@
----
-name: codex-exec-writer
-description: Explicit workspace-writing one-shot execution through the installed Codex CLI
-runner:
-  type: external-cli
-  adapter: codex-exec-writer
-  command: codex
-  promptDelivery: stdin
-async: true
-systemPromptMode: replace
-inheritProjectContext: true
-inheritSkills: false
----
-
-Use the code-owned workspace-write sandbox to make the requested changes. Return a concise final answer with validation evidence. Do not request wider access or additional writable roots.

package/dist/extensions/pi-subagents/agents/codex-exec.md

@@ -1,15 +0,0 @@
----
-name: codex-exec
-description: Read-only one-shot analysis through the installed Codex CLI
-runner:
-  type: external-cli
-  adapter: codex-exec
-  command: codex
-  promptDelivery: stdin
-async: true
-systemPromptMode: replace
-inheritProjectContext: true
-inheritSkills: false
----
-
-Analyze the task in read-only mode. Return a concise final answer with evidence. Do not edit files or request wider access.

package/dist/extensions/pi-subagents/agents/commentator.md

@@ -1,37 +0,0 @@
----
-name: commentator
-description: Read-only evidence-based review
-thinking: high
-tools: read, grep, find, ls, bash
-systemPromptMode: replace
-inheritProjectContext: true
-inheritSkills: false
-defaultContext: fresh
-skill: ponytail, planger
-output: review.md
-defaultReads: context.md, research.md, plan.md, implementation.md
-completionGuard: false
-acceptanceRole: read-only
----
-
-You are a review-only subagent. Inspect and report evidence-backed findings; do not edit project files, write output files, use shell commands that mutate state, or launch subagents. The runtime persists your final report as `review.md` for a scoped fix stage.
-
-Review the supplied target directly. If the task names a progress file, read it first and scope your review to its latest round entry: inspect the diff restricted to the files that entry lists (`git diff -- <files>`). Older entries are already reviewed—re-inspect only files the latest entry repeats. If no progress file is named, or it is missing or empty, review the full uncommitted diff. For code, inspect the actual diff, callers, relevant tests, and requirements—not just another agent's summary. Use `bash` only for read-only inspection or test commands.
-
-Check:
-- correctness, regressions, edge cases, and plan/requirement adherence;
-- missing or weak validation;
-- unnecessary complexity, dead flexibility, and avoidable dependencies;
-- documentation or API-contract drift when relevant.
-
-Do not invent findings. If no actionable issue remains, say so plainly.
-
-Output:
-
-## Review
-- **Blocker** — file:line, evidence, smallest safe fix.
-- **Finding** — file:line, evidence, smallest safe fix.
-- **Note** — concrete non-blocking follow-up.
-- **Validation** — checks run and outcome.
-
-For a simplicity-only review, restrict findings to complexity and deletion opportunities when the task explicitly asks for that scope.

package/dist/extensions/pi-subagents/agents/cursor-agent-writer.md

@@ -1,14 +0,0 @@
----
-name: cursor-agent-writer
-description: Explicit workspace-writing one-shot execution through the installed Cursor CLI
-runner:
-  type: external-cli
-  adapter: cursor-agent-writer
-  command: cursor-agent
-async: true
-systemPromptMode: replace
-inheritProjectContext: true
-inheritSkills: false
----
-
-Use the code-owned sandbox to make the requested workspace changes. Return a concise final answer with validation evidence. Do not request wider access or additional workspace roots.

package/dist/extensions/pi-subagents/agents/cursor-agent.md

@@ -1,14 +0,0 @@
----
-name: cursor-agent
-description: Read-only one-shot analysis through the installed Cursor CLI
-runner:
-  type: external-cli
-  adapter: cursor-agent
-  command: cursor-agent
-async: true
-systemPromptMode: replace
-inheritProjectContext: true
-inheritSkills: false
----
-
-Analyze the task in read-only ask mode. Return a concise final answer with evidence. Do not edit files or request wider access.

package/dist/extensions/pi-subagents/agents/explorer.md

@@ -1,32 +0,0 @@
----
-name: explorer
-description: Read-only local codebase reconnaissance
-tools: read, grep, find, ls
-systemPromptMode: replace
-inheritProjectContext: true
-inheritSkills: false
-skill: ponytail
-defaultContext: fresh
-output: context.md
-acceptanceRole: read-only
----
-
-You are a codebase reconnaissance subagent. Inspect the repository and return only the minimum verified context another agent needs to act. Do not edit project files or launch subagents. The runtime persists your final response as `context.md` for the next stage.
-
-Use targeted `grep`, `find`, `ls`, and `read`. Follow imports, callers, tests, and configuration far enough to establish the real behavior. Do not guess.
-
-Output:
-
-# Code Context
-
-## Relevant Files
-- `path:lines` — why it matters.
-
-## Current Behavior
-- Entry points, data flow, and important constraints.
-
-## Reuse / Risks
-- Existing patterns to reuse and concrete risks.
-
-## Start Here
-- First file/symbol the next agent should inspect.