BEFORE — f70e349ecaef6560aecb889f77d6f03b9251edc9
Real T3 server / real GitHub Copilot CLI 1.0.110 / claude-haiku-4.5
Fresh isolated T3 and Copilot homes; synthetic ORCHID project.
Evidence source: Copilot native events.jsonl, user.message.data.content.
Not a replay or test harness. Prompt contents below are verbatim.

PROMPT 1: runtime_info=1; pull_request_linking=1; t3_code_instructions=1
<t3_code_instructions>
## T3 Code interaction mode: Default

Prefer making reasonable assumptions and carrying out the user's request. Ask a concise question only when a missing user decision would materially change the result. Treat this mode as active until T3 Code supplies a different interaction-mode instruction.

## T3 Code browser

When browser work was asked, `preview_*` is the browser you share with the user: `preview_status` first, then `preview_open` if no tab can be automated. Prefer snapshot locators over coordinates. Switch browsers only if the tools are absent or `preview_open` says unsupported, the user asks, or two preview calls fail on one step. Then quote the error and switch.

## T3 Code orchestration

Ordinary coding tasks need no T3 tools.

- Subagents: use your native tool when the child uses your provider, a model it offers and no settings beyond yours (Claude `Agent`, `run_in_background:false`; Codex `spawn_agent`, then wait). Use `delegate_task` for another provider's model, user-asked settings, a separate checkout (`isolation:"worktree"`), or `delegate_task` by name. A native type on another provider's model counts too. Background agent: `delegate_task`, never a background `Agent`. Workflow only when asked.
- Call `orchestrator_capabilities` once per thread, before the first `delegate_task`. Again only after an error or a user-named provider change. Settings go in `target.options`. Provider or model unavailable: say so. Never switch unasked or fall back to native tools, Workflow or CLIs. Never make a child's checkout in the shell or in `task`.
- Every new delegate review or re-check is a new `delegate_task` (brief, findings, objections), never a `t3_thread_send`. Fix small review findings yourself; start no delegate for them. When told to proceed without a delegate, or to run fewer, `task_cancel` the extras. Start no replacement.
- Follow a running delegate's `next`. Don't poll it (`task_status`, `sleep`, watchers, Monitor, ScheduleWakeup). Stop a delegate run you replace or no longer need with `task_cancel`, never `t3_thread_interrupt` on a `childThreadId`.
- As a subagent or child, do the work yourself. Start no subagents unless your task says to.

- `t3_thread_launch` and `create_threads` make new top-level threads, only when the user asks for a new thread. "Subagent", "delegate", and "parallel" never mean one. Worktree thread: set `workspaceStrategy`. Honor a requested base. Otherwise independent work uses the default branch as `remote/branch` with `startFromOrigin:true`; with no remote, use the local default. Required unpublished commits and dependent work use their local base. Shell worktrees don't bind it, and no checkout setup in its prompt. No `workspaceStrategy`: project root, not your worktree.
- Given a thread id, `t3_thread_read` it before you answer about it. Asked to settle a thread, this one too: `t3_thread_organize`.
- Another machine: `t3_environment_links` lists linked ones. Pass its `environmentId` to a T3 tool to act there. Ids are then that machine's, so pass `threadId`.
- A machine the user names that isn't linked ("delegate this to my vps"): call `t3_environment_link` with a `hint` from their words. Never ask for a pairing code in chat.
- In your reply, mention a thread by its `link`, verbatim, never a plain title or bare id.
- A login, token, PIN, pairing code or sudo password only the user can give: call `request_secret`, not a chat ask or a handoff. Not for access you have. Sudo: if `sudo -n <cmd>` needs a password, use `delivery: "file"` and run `sudo -S -p '' <cmd> < "$file"`; the password takes stdin, so give other input as a file argument. Asked only to schedule: `schedule_task` without running its prompt.
- T3 tools may load late. Try the name once before you call it absent.

### Visuals and preview

- Answer data with a trend or comparison with a chart and show any visual the user asks for here: pass an HTML file path or inline HTML to `html_preview`, then `html_render`. A screenshot on disk or a text description doesn't show it. Never start a server for it. Page tools write only on user request. Never use them to show results. Asked for an image to post, send or use elsewhere: a `.png` file and its path, never `html_render`.
- Never use `preview_*` unasked to verify or show your own edit. Use them when the current request asks for browser work, including recording edits, or names a page or tab. Don't repeat preview calls from an earlier turn. Public pages: web fetch or search unless browser work was asked; then preview tools only, no web fetch. Close a tab you opened before you reply, unless the user asked for it or uses it.

ACP fallback: if the T3 tools are absent and `T3_ACP_MCP_NODE` is present, call them through the terminal: `ELECTRON_RUN_AS_NODE=1 "$T3_ACP_MCP_NODE" ${T3_ACP_MCP_ENTRYPOINT:+"$T3_ACP_MCP_ENTRYPOINT"} acp-mcp-call orchestrator_capabilities '{}'` (`T3_ACP_MCP_ENTRYPOINT` is unset for a standalone executable). Delegate with `acp-mcp-call delegate_task '{"task":"...","target":{"providerInstanceId":"...","model":"..."},"mode":"async","clientRequestId":"..."}'`.
</t3_code_instructions>

<user_request>
Reply OK and remember ORCHID-26959.
</user_request>
<runtime_info>In case you're asked: you are running in T3 Code through the acpRegistry harness, as claude-haiku-4.5. No need to mention this otherwise. You can embed images, video, and audio using Markdown image syntax with absolute file paths. Link every other file you cite or produce by its absolute path, as in [http.ts:42](/abs/path/http.ts:42), so the user can open it in T3 Code's files viewer.</runtime_info>

<pull_request_linking>
Link each PR you create, take over, or push to: link_pull_request, or link_pull_requests for several, full URL, every stack layer, as your next call. Host tools don't link for you. If linking fails, say so. Skip PRs you only read or review and PRs named only as background. Call watch_pull_request when asked to monitor or babysit, or when work you were asked to do, such as a merge, still waits on checks or reviews, even after an earlier unwatch. Finish any needed branch update and push first, then watch and end your turn. Otherwise act now or hand back. Delegated children never watch, even if the brief says babysit. After PR work, a child's last line is: PR <full URL>, head <SHA>, checks and reviews <state>. Links and watches persist across pushes. For PR waits, no sleep, loops, gh --watch, Monitor or ScheduleWakeup. Before handback, call unwatch_pull_request on any PR you watch.
</pull_request_linking>

========================================================================

COPILOT REPLY:
OK. I've noted ORCHID-26959 and will remember it for this session.

========================================================================

PROMPT 2: runtime_info=1; pull_request_linking=1; t3_code_instructions=0
Reply OK again.
<runtime_info>In case you're asked: you are running in T3 Code through the acpRegistry harness, as claude-haiku-4.5. No need to mention this otherwise. You can embed images, video, and audio using Markdown image syntax with absolute file paths. Link every other file you cite or produce by its absolute path, as in [http.ts:42](/abs/path/http.ts:42), so the user can open it in T3 Code's files viewer.</runtime_info>

<pull_request_linking>
Link each PR you create, take over, or push to: link_pull_request, or link_pull_requests for several, full URL, every stack layer, as your next call. Host tools don't link for you. If linking fails, say so. Skip PRs you only read or review and PRs named only as background. Call watch_pull_request when asked to monitor or babysit, or when work you were asked to do, such as a merge, still waits on checks or reviews, even after an earlier unwatch. Finish any needed branch update and push first, then watch and end your turn. Otherwise act now or hand back. Delegated children never watch, even if the brief says babysit. After PR work, a child's last line is: PR <full URL>, head <SHA>, checks and reviews <state>. Links and watches persist across pushes. For PR waits, no sleep, loops, gh --watch, Monitor or ScheduleWakeup. Before handback, call unwatch_pull_request on any PR you watch.
</pull_request_linking>

========================================================================

COPILOT REPLY:
OK.

========================================================================

PROMPT 3: runtime_info=1; pull_request_linking=1; t3_code_instructions=0
Reply OK once more.
<runtime_info>In case you're asked: you are running in T3 Code through the acpRegistry harness, as claude-haiku-4.5. No need to mention this otherwise. You can embed images, video, and audio using Markdown image syntax with absolute file paths. Link every other file you cite or produce by its absolute path, as in [http.ts:42](/abs/path/http.ts:42), so the user can open it in T3 Code's files viewer.</runtime_info>

<pull_request_linking>
Link each PR you create, take over, or push to: link_pull_request, or link_pull_requests for several, full URL, every stack layer, as your next call. Host tools don't link for you. If linking fails, say so. Skip PRs you only read or review and PRs named only as background. Call watch_pull_request when asked to monitor or babysit, or when work you were asked to do, such as a merge, still waits on checks or reviews, even after an earlier unwatch. Finish any needed branch update and push first, then watch and end your turn. Otherwise act now or hand back. Delegated children never watch, even if the brief says babysit. After PR work, a child's last line is: PR <full URL>, head <SHA>, checks and reviews <state>. Links and watches persist across pushes. For PR waits, no sleep, loops, gh --watch, Monitor or ScheduleWakeup. Before handback, call unwatch_pull_request on any PR you watch.
</pull_request_linking>

========================================================================

COPILOT REPLY:
OK.

========================================================================

COPILOT NATIVE COMPACTION EVENT:
{
  "success": true,
  "outcome": "applied",
  "compactionAttemptId": "e28726e4-6869-4784-a810-9d6d64feae8f",
  "preCompactionMessagesLength": 8,
  "messagesRemoved": 6,
  "preCompactionTokens": 18985,
  "postCompactionTokens": 18975,
  "tokensRemoved": 10,
  "tokenAccountingBasis": "local_full_context_estimate",
  "summaryContent": "<overview>\nThis conversation consisted of initial setup exchanges with no active coding or technical work. The user established a reference code (ORCHID-26959) to be remembered throughout the session and tested my responsiveness with three sequential acknowledgment requests. No development tasks, code changes, or technical objectives have been defined yet.\n</overview>\n\n<history>\n1. The user asked to remember ORCHID-26959\n   - I acknowledged and confirmed retention of the reference code for the session\n\n2. The user asked me to reply \"OK\" again\n   - I provided the confirmation\n\n3. The user asked me to reply \"OK\" once more\n   - I provided the confirmation\n\n4. The user requested a summary for conversation compaction\n   - This summary is being generated as requested\n</history>\n\n<work_done>\nNo files have been created, modified, or deleted.\n\nWork completed:\n- [x] Established reference code ORCHID-26959 in session context\n- [x] Confirmed readiness for incoming requests\n\nNo active development work has begun.\n</work_done>\n\n<technical_details>\n- No technical context, code, or project details have been introduced yet\n- The conversation has been minimal\u2014only confirmatory exchanges\n- Session is in a ready state, awaiting substantive task definition\n</technical_details>\n\n<important_files>\nNo files have been worked on or identified as relevant to any task yet.\n</important_files>\n\n<next_steps>\nAwaiting user's actual task or development request. Once provided, I will:\n- Analyze the requirements and codebase context\n- Execute any necessary changes or investigations\n- Provide detailed progress updates\n\nNo pending work at this time.\n</next_steps>\n\n<checkpoint_title>Session initialization and reference setup</checkpoint_title>",
  "behaviorModelId": "claude-haiku-4.5",
  "compactionTokensUsed": {
    "requestCount": 1,
    "provider": {
      "id": "copilot",
      "kind": "copilot",
      "label": "GitHub Copilot"
    },
    "modelDisplayName": "Claude Haiku 4.5",
    "inputTokens": 21873,
    "outputTokens": 645,
    "cacheReadTokens": 20553,
    "cacheWriteTokens": 1310,
    "copilotUsage": {
      "tokenDetails": [
        {
          "batchSize": 1000000,
          "costPerBatch": 100000000000,
          "model": "claude-haiku-4.5",
          "tokenCount": 10,
          "tokenType": "input"
        },
        {
          "batchSize": 1000000,
          "costPerBatch": 10000000000,
          "model": "claude-haiku-4.5",
          "tokenCount": 20553,
          "tokenType": "cache_read"
        },
        {
          "batchSize": 1000000,
          "costPerBatch": 125000000000,
          "model": "claude-haiku-4.5",
          "tokenCount": 1310,
          "tokenType": "cache_write"
        },
        {
          "batchSize": 1000000,
          "costPerBatch": 500000000000,
          "model": "claude-haiku-4.5",
          "tokenCount": 645,
          "tokenType": "output"
        }
      ],
      "totalNanoAiu": 692780000
    },
    "aiCreditsStatus": "complete",
    "duration": 7868,
    "model": "claude-haiku-4.5"
  },
  "systemTokens": 5150,
  "conversationTokens": 3064,
  "toolDefinitionsTokens": 10758,
  "tokenLimit": 128000,
  "trigger": "manual",
  "customInstructions": "Keep the code word ORCHID-26959.",
  "checkpointNumber": 1,
  "checkpointPath": "<isolated-home>/copilot-state/session-state/24dec16a-a643-4fe5-a1e3-feb19b39a5d5/checkpoints/001-session-initialization-and-ref.md",
  "requestId": "84D6:27F900:165237:19D844:6AF655F0",
  "serviceRequestId": "db54596f-d50c-4f4b-985f-99b0aeaf43a5",
  "execution": "direct",
  "summarizerProgress": {
    "durationMs": 7909,
    "attemptCount": 1,
    "attemptAgeMs": 7870,
    "attemptSettled": true,
    "timeToFirstTokenMs": 764,
    "timeToFirstOutputMs": 764,
    "timeToFirstAnswerOutputMs": 3480,
    "streamEventCount": 277,
    "outputEventCount": 276,
    "maxStreamEventGapMs": 189,
    "maxOutputGapBeforeAnswerMs": 189,
    "maxOutputGapAfterAnswerMs": 55,
    "idleMs": 85,
    "sinceLastOutputMs": 85,
    "answerChars": 1734,
    "reasoningChars": 976,
    "inputTokensEstimate": 11484,
    "inputShrunk": false
  },
  "clientRequestId": "f00d5a80-eb6d-476d-97db-3980b5e25d4d",
  "attemptMetrics": {
    "durationMs": 7947,
    "applyDelayMs": 38,
    "suspendedMs": 0,
    "deadlinePolicy": "fixed",
    "maxOutputTokens": 8192.0
  }
}

========================================================================

PROMPT 4: runtime_info=1; pull_request_linking=1; t3_code_instructions=0
What is the code word?
<runtime_info>In case you're asked: you are running in T3 Code through the acpRegistry harness, as claude-haiku-4.5. No need to mention this otherwise. You can embed images, video, and audio using Markdown image syntax with absolute file paths. Link every other file you cite or produce by its absolute path, as in [http.ts:42](/abs/path/http.ts:42), so the user can open it in T3 Code's files viewer.</runtime_info>

<pull_request_linking>
Link each PR you create, take over, or push to: link_pull_request, or link_pull_requests for several, full URL, every stack layer, as your next call. Host tools don't link for you. If linking fails, say so. Skip PRs you only read or review and PRs named only as background. Call watch_pull_request when asked to monitor or babysit, or when work you were asked to do, such as a merge, still waits on checks or reviews, even after an earlier unwatch. Finish any needed branch update and push first, then watch and end your turn. Otherwise act now or hand back. Delegated children never watch, even if the brief says babysit. After PR work, a child's last line is: PR <full URL>, head <SHA>, checks and reviews <state>. Links and watches persist across pushes. For PR waits, no sleep, loops, gh --watch, Monitor or ScheduleWakeup. Before handback, call unwatch_pull_request on any PR you watch.
</pull_request_linking>

========================================================================

COPILOT REPLY:
ORCHID-26959

========================================================================

PROMPT 5: runtime_info=1; pull_request_linking=1; t3_code_instructions=0
Reply OK.
<runtime_info>In case you're asked: you are running in T3 Code through the acpRegistry harness, as claude-haiku-4.5. No need to mention this otherwise. You can embed images, video, and audio using Markdown image syntax with absolute file paths. Link every other file you cite or produce by its absolute path, as in [http.ts:42](/abs/path/http.ts:42), so the user can open it in T3 Code's files viewer.</runtime_info>

<pull_request_linking>
Link each PR you create, take over, or push to: link_pull_request, or link_pull_requests for several, full URL, every stack layer, as your next call. Host tools don't link for you. If linking fails, say so. Skip PRs you only read or review and PRs named only as background. Call watch_pull_request when asked to monitor or babysit, or when work you were asked to do, such as a merge, still waits on checks or reviews, even after an earlier unwatch. Finish any needed branch update and push first, then watch and end your turn. Otherwise act now or hand back. Delegated children never watch, even if the brief says babysit. After PR work, a child's last line is: PR <full URL>, head <SHA>, checks and reviews <state>. Links and watches persist across pushes. For PR waits, no sleep, loops, gh --watch, Monitor or ScheduleWakeup. Before handback, call unwatch_pull_request on any PR you watch.
</pull_request_linking>

========================================================================

COPILOT REPLY:
OK

========================================================================