[leomontigatti]

T3 update review: 0.1.7-nightly.20261101.4016 → 0.1.7-nightly.20261102.4066 (4 releases)

Needs you

• Quit T3 and open it from the desktop before you install the next update (shared,
  deb-update-relaunch-no-new-privs). The running app has NoNewPrivs: 1 (checked 2026-11-02 on
  4066), so its next "Restart to install" would fail with no password prompt. The fix,
  #15387, is still open.

Breaks / changes

No active entry stopped holding. Three changes in behaviour, recorded under their entries:

• shared, thread-launch-workspace: #28582
  "The scoped base fetch passes --no-tags", so a new thread's checkout can lag the remote's
  tags. No project's agent docs or t3.json run git describe. Proposed edit, not in this diff:
  AGENTS.md § Tag a release says to read the latest tag with git ls-remote --tags origin.
• shared, login-shell-path: #28556 starts the
  desktop on a cached PATH and probes the login shell in the background. A ~/.profile change
  reaches sessions started after that probe finishes, and a provider process started earlier keeps
  its PATH until it restarts. The entry holds. No edit to a skill or hook.
• shared, delegate-task-reviews: #28516 "Dangerous-removal
  safety checks in bypass mode reject the command with the original warning". The agent then goes
  on without the removal and reports it. Skills name only git worktree remove, so no edit.

Improves

Fixes that need no adoption, recorded under their entries:

• shared, delegate-task-reviews and delegate-task-worktrees:
  #27468, a parent no longer hangs on a child
  that left an unawaited Monitor running.
  #28520, Stop ends a run whose provider turn
  already finished, which task_cancel reaches too.
• shared, scheduled-reviews: #28474, an
  interrupt no longer leaves a task busy until a restart, which made scheduled polls skip it.
• shared, pr-watch-is-native: #22022, T3 keeps
  the last known mergeability through GitHub's transient unknown.
• shared, storage-cleanup-removes-thread-worktrees:
  #27175, repositories with no remote get
  unchanged-worktree cleanup. Every project here has a remote.
• shared, preview-tools-verification: #28027,
  preview_open takes a dev-server target. PREVIEW.md's URL route works and costs the same
  one call, so no edit. ServerBrowserPage.ts is unchanged, so no snapshot fault moved.

The proactive pass proposes no new entry.

Drift

• shared, skills/t3-update-review/scripts/changes.py: rubens' agent-memory-limit cites
  apps/server/src/process/agentScope.ts, which WATCHED_PATHS lacked. Added, with
  apps/desktop/src/shell/DesktopShellEnvironment.ts and docs/user/permission-modes.md, which
  this review's entries now cite. agentScope.ts has no change in this range.

Every Used by file and heading exists on its repo's default branch, and the grep found no
uncovered T3 rule. infra has no docs/agents/, so the review leaves it out.

Still ready

• shared, preview-tools-verification: adoption step one has been under way since 2026-10-26.
  Step two (dropping the browser CLI) waits for ten PRs verified with preview_snapshot and no
  lost click. The file's count is unchanged.

Every Watch: issue, PR and discussion is still open or unchanged, so no watching entry moved
to ready. Checked with no effect on us:

• #27197: managed policy. This machine has no
  /etc/t3code/policy.json; a sentence under scheduled-reviews records it.
• #29026 and
  #29068: Codex gets t3_thread_wait from a
  second MCP server. No skill, agent or hook names a mcp__t3 prefix or that tool.
• #28410: CLAUDE_CODE_ENTRYPOINT=t3-code, seen
  in this session. No hook, skill or project agent file reads it.
• #28604: Codex sessions get T3CODE_THREAD_ID.
  No workflow reads it; own-thread-readable holds.
• #29053: thread tags hide threads in the UI
  only; "MCP is unchanged".

No project's behaviour changes, and none has to add or rename anything. Proposed edits stay proposals: only t3-dependencies.md and the watched paths are in this diff.

Review

Tier: readback+correctness, reviewed 6435037

• readback (Luna): nothing surprising
• correctness (Sol): 1 finding, fixed; a running provider process keeps the PATH it started with, now stated in login-shell-path (a docs sentence, so no fix round)

Readback

The commit adds three T3 paths to the watched-path list and updates t3-dependencies.md with behaviour changes and observations from T3 builds through 0.1.7-nightly.20261102.4066. Nothing surprising. Would merge: yes.

🤖 Generated with Claude Code