PR #30786 runtime verification, Linux, 2026-11-04 main: 9e85538535; PR: 6c187e2bfa323029877a0c9f76a02d5ca42a2ed7 A real git repository was registered with Add project > Local folder in the web app. No mocks, fixtures, replay provider, or copied production data were used. Main and PR ran sequentially with the same app-created project and thread data. CLI below is node /apps/server/src/bin.ts with --base-dir . MAIN running dev server (web 8693, server 16733): cwd=/home/user/linked worktree $ t3 thread list --json exit 1: No T3 Code project matches '.'. Pass a project id or a path inside a project. $ t3 thread start . 'Reply exactly LINKED_OK. Do not change any files.' --provider codex --model gpt-6.1-sol --json exit 1: No T3 Code project matches '.'. Pass a project id or a path inside a project. Control: web thread in registered main checkout completed with MAIN_DIRECT_OK, model gpt-6.1-sol. PR running dev server (web 5733, server 13773): cwd=/home/user/linked worktree $ t3 thread list --json exit 0: returned the existing Direct Reply Request thread in project 39736eb8-0396-4b72-ae88-f3c1b1369ad6. $ t3 thread start . 'Reply exactly LINKED_OK. Do not change any files.' --provider codex --model gpt-6.1-sol --json --wait {"threadId":"mcp:67c7afdf-5c01-4d84-ba1c-f3bb981904ba","runId":"run:thread:mcp%3A67c7afdf-5c01-4d84-ba1c-f3bb981904ba:ordinal:1","status":"completed","reply":"LINKED_OK","error":null} exit 0. Opened the resulting thread in the web app and saw LINKED_OK. Sent a follow-up from its web composer; the same real model returned WEB_FOLLOWUP_OK. Created a T3-managed worktree through thread start --worktree main --branch verify-managed. Its provider ran pwd and reported: /home/user/t3code/.t3-verify/worktrees/verification-repo/verify-managed From that managed worktree, against the same running server: main CLI thread list --json: exit 1, No T3 Code project matches '.'. PR CLI thread list --json: exit 0, returned verification-repo threads. PR CLI thread start . --provider codex --model gpt-6.1-sol --json --wait: {"threadId":"mcp:8cba4d6c-e36a-4499-aae6-e26e1cca45a7","runId":"run:thread:mcp%3A8cba4d6c-e36a-4499-aae6-e26e1cca45a7:ordinal:1","status":"completed","reply":"MANAGED_RESOLVED_OK","error":null} exit 0. Opened this thread in the web app and saw MANAGED_RESOLVED_OK. Neighboring checks through the running server: - external worktree /src subdirectory: list exit 0, same project threads - symlink alias: list exit 0, same project threads - registered main checkout: list exit 0, same project threads - explicit project id from /tmp: list exit 0, same project threads - unregistered /tmp: exit 1, expected project-not-found error - web follow-up to CLI-created thread: completed successfully Blacksmith: vp test run apps/server/src/cli/thread.test.ts 1 test file passed, 8 tests passed. No source changes or pushes were needed. Existing head CI checks passed. Not exercised: native mobile/Electron clients, macOS/Windows, relay/tunnel connections.