Absorb latest t3code desktop workflow improvements

[IchenDEV]

Summary

• harden local Usage parsing with Claude message/request deduplication, Codex delta-to-total reconciliation, provider timestamps, streaming reads, a 30-day scan boundary, and a bounded in-process file cache
• persist a Desktop project preference for new-session checkout/worktree mode while preserving CodeTwo's local-ref, pinned-SHA, no-fetch, no-fallback contract
• add versioned, validated, bounded per-project Browser recent sites recorded only after successful native navigation
• make supported workspace @ image references send both ACP pixels and an actionable relative path, with canonical workspace containment, a 16 MB cap, and extension/signature validation
• document an exhaustive 96-commit review of the latest t3code delta and the features deliberately not copied

Why

CodeTwo already had the surrounding UI and runtime seams, but several states were either transient or too trusting: Usage could overcount repeated transcript records and repeatedly rescan whole files, new-session workspace choices were not remembered per project, Browser tabs had no project-local recent history, and image mentions gave the provider pixels without a usable workspace path.

The implementation borrows the product invariants from Usage #5684, project defaults #5766, image paths #5757, and recent sites #5270, adapted to CodeTwo's Tauri/Rust and local-first architecture.

User impact

• Usage totals are more trustworthy and reopening the view avoids reparsing unchanged transcripts during the process lifetime.
• Each Desktop project can start new drafts in the project checkout, a worktree from HEAD, or a worktree from the local origin default ref.
• A blank Browser tab offers recent sites for the active project and lets users remove individual entries.
• Existing workspace image mentions remain canonical in the transcript while the provider receives both pixels and a workspace-relative path it can act on.

Scope and constraints

• Project defaults currently initialize Desktop drafts only; .codetwo.json, global fallback, TUI, and remote-client consumption are not included.
• Usage does not add provider/model/day/cost UI, a durable cache, cross-environment fingerprinting, or LiteLLM pricing.
• Image support applies to existing workspace @ references. It does not add arbitrary clipboard/drag attachments, an app-owned attachment directory, or workspace-external grants. Signature checks are not a full image decoder, and canonicalize-to-open retains the usual local TOCTOU boundary.
• Invested drafts and manual pin ordering remain follow-up work.
• The newly merged t3code mobile Usage dashboard (#5743) is documented but not copied because CodeTwo has no mobile client surface.

Validation

• cargo test --workspace — 349 passed, 0 failed
• cargo check --workspace
• bun run test — 72 passed, 208 assertions across 10 files
• bun run build — TypeScript and Vite production build passed; only the existing large-chunk warning remains
• selected changed Rust files passed rustfmt --check
• git diff --check
• research report covers 96/96 upstream commits and all 22 relative links resolve
• rendered Project settings and Browser fallback states at default and 680 px widths with a clean console; the non-Tauri browser run did not exercise populated native-webview history

Research

See docs/research/t3code-latest-delta-2026-08-09.md for the frozen upstream boundary, evidence, exclusions, and complete commit classification.

[IchenDEV]

Summary

• harden local Usage parsing with Claude message/request deduplication, Codex delta-to-total reconciliation, provider timestamps, streaming reads, a 30-day scan boundary, and a bounded in-process file cache
• persist a Desktop project preference for new-session checkout/worktree mode while preserving CodeTwo's local-ref, pinned-SHA, no-fetch, no-fallback contract
• add versioned, validated, bounded per-project Browser recent sites recorded only after successful native navigation
• make supported workspace @ image references send both ACP pixels and an actionable relative path, with canonical workspace containment, a 16 MB cap, and extension/signature validation
• document an exhaustive 96-commit review of the latest t3code delta and the features deliberately not copied

Why

CodeTwo already had the surrounding UI and runtime seams, but several states were either transient or too trusting: Usage could overcount repeated transcript records and repeatedly rescan whole files, new-session workspace choices were not remembered per project, Browser tabs had no project-local recent history, and image mentions gave the provider pixels without a usable workspace path.

The implementation borrows the product invariants from Usage #5684, project defaults #5766, image paths #5757, and recent sites #5270, adapted to CodeTwo's Tauri/Rust and local-first architecture.

User impact

• Usage totals are more trustworthy and reopening the view avoids reparsing unchanged transcripts during the process lifetime.
• Each Desktop project can start new drafts in the project checkout, a worktree from HEAD, or a worktree from the local origin default ref.
• A blank Browser tab offers recent sites for the active project and lets users remove individual entries.
• Existing workspace image mentions remain canonical in the transcript while the provider receives both pixels and a workspace-relative path it can act on.

Scope and constraints

• Project defaults currently initialize Desktop drafts only; .codetwo.json, global fallback, TUI, and remote-client consumption are not included.
• Usage does not add provider/model/day/cost UI, a durable cache, cross-environment fingerprinting, or LiteLLM pricing.
• Image support applies to existing workspace @ references. It does not add arbitrary clipboard/drag attachments, an app-owned attachment directory, or workspace-external grants. Signature checks are not a full image decoder, and canonicalize-to-open retains the usual local TOCTOU boundary.
• Invested drafts and manual pin ordering remain follow-up work.
• The newly merged t3code mobile Usage dashboard (#5743) is documented but not copied because CodeTwo has no mobile client surface.

Validation

• cargo test --workspace — 349 passed, 0 failed
• cargo check --workspace
• bun run test — 72 passed, 208 assertions across 10 files
• bun run build — TypeScript and Vite production build passed; only the existing large-chunk warning remains
• selected changed Rust files passed rustfmt --check
• git diff --check
• research report covers 96/96 upstream commits and all 22 relative links resolve
• rendered Project settings and Browser fallback states at default and 680 px widths with a clean console; the non-Tauri browser run did not exercise populated native-webview history

Research

See docs/research/t3code-latest-delta-2026-08-09.md for the frozen upstream boundary, evidence, exclusions, and complete commit classification.

[IchenDEV]

Summary

• harden local Usage parsing with Claude message/request deduplication, Codex delta-to-total reconciliation, provider timestamps, streaming reads, a 30-day scan boundary, and a bounded in-process file cache
• persist a Desktop project preference for new-session checkout/worktree mode while preserving CodeTwo's local-ref, pinned-SHA, no-fetch, no-fallback contract
• add versioned, validated, bounded per-project Browser recent sites recorded only after successful native navigation
• make supported workspace @ image references send both ACP pixels and an actionable relative path, with canonical workspace containment, a 16 MB cap, and extension/signature validation
• document an exhaustive 96-commit review of the latest t3code delta and the features deliberately not copied

Why

CodeTwo already had the surrounding UI and runtime seams, but several states were either transient or too trusting: Usage could overcount repeated transcript records and repeatedly rescan whole files, new-session workspace choices were not remembered per project, Browser tabs had no project-local recent history, and image mentions gave the provider pixels without a usable workspace path.

The implementation borrows the product invariants from Usage #5684, project defaults #5766, image paths #5757, and recent sites #5270, adapted to CodeTwo's Tauri/Rust and local-first architecture.

User impact

• Usage totals are more trustworthy and reopening the view avoids reparsing unchanged transcripts during the process lifetime.
• Each Desktop project can start new drafts in the project checkout, a worktree from HEAD, or a worktree from the local origin default ref.
• A blank Browser tab offers recent sites for the active project and lets users remove individual entries.
• Existing workspace image mentions remain canonical in the transcript while the provider receives both pixels and a workspace-relative path it can act on.

Scope and constraints

• Project defaults currently initialize Desktop drafts only; .codetwo.json, global fallback, TUI, and remote-client consumption are not included.
• Usage does not add provider/model/day/cost UI, a durable cache, cross-environment fingerprinting, or LiteLLM pricing.
• Image support applies to existing workspace @ references. It does not add arbitrary clipboard/drag attachments, an app-owned attachment directory, or workspace-external grants. Signature checks are not a full image decoder, and canonicalize-to-open retains the usual local TOCTOU boundary.
• Invested drafts and manual pin ordering remain follow-up work.
• The newly merged t3code mobile Usage dashboard (#5743) is documented but not copied because CodeTwo has no mobile client surface.

Validation

• cargo test --workspace — 349 passed, 0 failed
• cargo check --workspace
• bun run test — 72 passed, 208 assertions across 10 files
• bun run build — TypeScript and Vite production build passed; only the existing large-chunk warning remains
• selected changed Rust files passed rustfmt --check
• git diff --check
• research report covers 96/96 upstream commits and all 22 relative links resolve
• rendered Project settings and Browser fallback states at default and 680 px widths with a clean console; the non-Tauri browser run did not exercise populated native-webview history

Research

See docs/research/t3code-latest-delta-2026-08-09.md for the frozen upstream boundary, evidence, exclusions, and complete commit classification.

[IchenDEV]

Summary

• harden local Usage parsing with Claude message/request deduplication, Codex delta-to-total reconciliation, provider timestamps, streaming reads, a 30-day scan boundary, and a bounded in-process file cache
• persist a Desktop project preference for new-session checkout/worktree mode while preserving CodeTwo's local-ref, pinned-SHA, no-fetch, no-fallback contract
• add versioned, validated, bounded per-project Browser recent sites recorded only after successful native navigation
• make supported workspace @ image references send both ACP pixels and an actionable relative path, with canonical workspace containment, a 16 MB cap, and extension/signature validation
• document an exhaustive 96-commit review of the latest t3code delta and the features deliberately not copied

Why

CodeTwo already had the surrounding UI and runtime seams, but several states were either transient or too trusting: Usage could overcount repeated transcript records and repeatedly rescan whole files, new-session workspace choices were not remembered per project, Browser tabs had no project-local recent history, and image mentions gave the provider pixels without a usable workspace path.

The implementation borrows the product invariants from Usage #5684, project defaults #5766, image paths #5757, and recent sites #5270, adapted to CodeTwo's Tauri/Rust and local-first architecture.

User impact

• Usage totals are more trustworthy and reopening the view avoids reparsing unchanged transcripts during the process lifetime.
• Each Desktop project can start new drafts in the project checkout, a worktree from HEAD, or a worktree from the local origin default ref.
• A blank Browser tab offers recent sites for the active project and lets users remove individual entries.
• Existing workspace image mentions remain canonical in the transcript while the provider receives both pixels and a workspace-relative path it can act on.

Scope and constraints

• Project defaults currently initialize Desktop drafts only; .codetwo.json, global fallback, TUI, and remote-client consumption are not included.
• Usage does not add provider/model/day/cost UI, a durable cache, cross-environment fingerprinting, or LiteLLM pricing.
• Image support applies to existing workspace @ references. It does not add arbitrary clipboard/drag attachments, an app-owned attachment directory, or workspace-external grants. Signature checks are not a full image decoder, and canonicalize-to-open retains the usual local TOCTOU boundary.
• Invested drafts and manual pin ordering remain follow-up work.
• The newly merged t3code mobile Usage dashboard (#5743) is documented but not copied because CodeTwo has no mobile client surface.

Validation

• cargo test --workspace — 349 passed, 0 failed
• cargo check --workspace
• bun run test — 72 passed, 208 assertions across 10 files
• bun run build — TypeScript and Vite production build passed; only the existing large-chunk warning remains
• selected changed Rust files passed rustfmt --check
• git diff --check
• research report covers 96/96 upstream commits and all 22 relative links resolve
• rendered Project settings and Browser fallback states at default and 680 px widths with a clean console; the non-Tauri browser run did not exercise populated native-webview history

Research

See docs/research/t3code-latest-delta-2026-08-09.md for the frozen upstream boundary, evidence, exclusions, and complete commit classification.

[IchenDEV]

Summary

• harden local Usage parsing with Claude message/request deduplication, Codex delta-to-total reconciliation, provider timestamps, streaming reads, a 30-day scan boundary, and a bounded in-process file cache
• persist a Desktop project preference for new-session checkout/worktree mode while preserving CodeTwo's local-ref, pinned-SHA, no-fetch, no-fallback contract
• add versioned, validated, bounded per-project Browser recent sites recorded only after successful native navigation
• make supported workspace @ image references send both ACP pixels and an actionable relative path, with canonical workspace containment, a 16 MB cap, and extension/signature validation
• document an exhaustive 96-commit review of the latest t3code delta and the features deliberately not copied

Why

CodeTwo already had the surrounding UI and runtime seams, but several states were either transient or too trusting: Usage could overcount repeated transcript records and repeatedly rescan whole files, new-session workspace choices were not remembered per project, Browser tabs had no project-local recent history, and image mentions gave the provider pixels without a usable workspace path.

The implementation borrows the product invariants from Usage #5684, project defaults #5766, image paths #5757, and recent sites #5270, adapted to CodeTwo's Tauri/Rust and local-first architecture.

User impact

• Usage totals are more trustworthy and reopening the view avoids reparsing unchanged transcripts during the process lifetime.
• Each Desktop project can start new drafts in the project checkout, a worktree from HEAD, or a worktree from the local origin default ref.
• A blank Browser tab offers recent sites for the active project and lets users remove individual entries.
• Existing workspace image mentions remain canonical in the transcript while the provider receives both pixels and a workspace-relative path it can act on.

Scope and constraints

• Project defaults currently initialize Desktop drafts only; .codetwo.json, global fallback, TUI, and remote-client consumption are not included.
• Usage does not add provider/model/day/cost UI, a durable cache, cross-environment fingerprinting, or LiteLLM pricing.
• Image support applies to existing workspace @ references. It does not add arbitrary clipboard/drag attachments, an app-owned attachment directory, or workspace-external grants. Signature checks are not a full image decoder, and canonicalize-to-open retains the usual local TOCTOU boundary.
• Invested drafts and manual pin ordering remain follow-up work.
• The newly merged t3code mobile Usage dashboard (#5743) is documented but not copied because CodeTwo has no mobile client surface.

Validation

• cargo test --workspace — 349 passed, 0 failed
• cargo check --workspace
• bun run test — 72 passed, 208 assertions across 10 files
• bun run build — TypeScript and Vite production build passed; only the existing large-chunk warning remains
• selected changed Rust files passed rustfmt --check
• git diff --check
• research report covers 96/96 upstream commits and all 22 relative links resolve
• rendered Project settings and Browser fallback states at default and 680 px widths with a clean console; the non-Tauri browser run did not exercise populated native-webview history

Research

See docs/research/t3code-latest-delta-2026-08-09.md for the frozen upstream boundary, evidence, exclusions, and complete commit classification.

[IchenDEV]

Summary

• harden local Usage parsing with Claude message/request deduplication, Codex delta-to-total reconciliation, provider timestamps, streaming reads, a 30-day scan boundary, and a bounded in-process file cache
• persist a Desktop project preference for new-session checkout/worktree mode while preserving CodeTwo's local-ref, pinned-SHA, no-fetch, no-fallback contract
• add versioned, validated, bounded per-project Browser recent sites recorded only after successful native navigation
• make supported workspace @ image references send both ACP pixels and an actionable relative path, with canonical workspace containment, a 16 MB cap, and extension/signature validation
• document an exhaustive 96-commit review of the latest t3code delta and the features deliberately not copied

Why

CodeTwo already had the surrounding UI and runtime seams, but several states were either transient or too trusting: Usage could overcount repeated transcript records and repeatedly rescan whole files, new-session workspace choices were not remembered per project, Browser tabs had no project-local recent history, and image mentions gave the provider pixels without a usable workspace path.

The implementation borrows the product invariants from Usage #5684, project defaults #5766, image paths #5757, and recent sites #5270, adapted to CodeTwo's Tauri/Rust and local-first architecture.

User impact

• Usage totals are more trustworthy and reopening the view avoids reparsing unchanged transcripts during the process lifetime.
• Each Desktop project can start new drafts in the project checkout, a worktree from HEAD, or a worktree from the local origin default ref.
• A blank Browser tab offers recent sites for the active project and lets users remove individual entries.
• Existing workspace image mentions remain canonical in the transcript while the provider receives both pixels and a workspace-relative path it can act on.

Scope and constraints

• Project defaults currently initialize Desktop drafts only; .codetwo.json, global fallback, TUI, and remote-client consumption are not included.
• Usage does not add provider/model/day/cost UI, a durable cache, cross-environment fingerprinting, or LiteLLM pricing.
• Image support applies to existing workspace @ references. It does not add arbitrary clipboard/drag attachments, an app-owned attachment directory, or workspace-external grants. Signature checks are not a full image decoder, and canonicalize-to-open retains the usual local TOCTOU boundary.
• Invested drafts and manual pin ordering remain follow-up work.
• The newly merged t3code mobile Usage dashboard (#5743) is documented but not copied because CodeTwo has no mobile client surface.

Validation

• cargo test --workspace — 349 passed, 0 failed
• cargo check --workspace
• bun run test — 72 passed, 208 assertions across 10 files
• bun run build — TypeScript and Vite production build passed; only the existing large-chunk warning remains
• selected changed Rust files passed rustfmt --check
• git diff --check
• research report covers 96/96 upstream commits and all 22 relative links resolve
• rendered Project settings and Browser fallback states at default and 680 px widths with a clean console; the non-Tauri browser run did not exercise populated native-webview history

Research

See docs/research/t3code-latest-delta-2026-08-09.md for the frozen upstream boundary, evidence, exclusions, and complete commit classification.

[IchenDEV]

Summary

• harden local Usage parsing with Claude message/request deduplication, Codex delta-to-total reconciliation, provider timestamps, streaming reads, a 30-day scan boundary, and a bounded in-process file cache
• persist a Desktop project preference for new-session checkout/worktree mode while preserving CodeTwo's local-ref, pinned-SHA, no-fetch, no-fallback contract
• add versioned, validated, bounded per-project Browser recent sites recorded only after successful native navigation
• make supported workspace @ image references send both ACP pixels and an actionable relative path, with canonical workspace containment, a 16 MB cap, and extension/signature validation
• document an exhaustive 96-commit review of the latest t3code delta and the features deliberately not copied

Why

CodeTwo already had the surrounding UI and runtime seams, but several states were either transient or too trusting: Usage could overcount repeated transcript records and repeatedly rescan whole files, new-session workspace choices were not remembered per project, Browser tabs had no project-local recent history, and image mentions gave the provider pixels without a usable workspace path.

The implementation borrows the product invariants from Usage #5684, project defaults #5766, image paths #5757, and recent sites #5270, adapted to CodeTwo's Tauri/Rust and local-first architecture.

User impact

• Usage totals are more trustworthy and reopening the view avoids reparsing unchanged transcripts during the process lifetime.
• Each Desktop project can start new drafts in the project checkout, a worktree from HEAD, or a worktree from the local origin default ref.
• A blank Browser tab offers recent sites for the active project and lets users remove individual entries.
• Existing workspace image mentions remain canonical in the transcript while the provider receives both pixels and a workspace-relative path it can act on.

Scope and constraints

• Project defaults currently initialize Desktop drafts only; .codetwo.json, global fallback, TUI, and remote-client consumption are not included.
• Usage does not add provider/model/day/cost UI, a durable cache, cross-environment fingerprinting, or LiteLLM pricing.
• Image support applies to existing workspace @ references. It does not add arbitrary clipboard/drag attachments, an app-owned attachment directory, or workspace-external grants. Signature checks are not a full image decoder, and canonicalize-to-open retains the usual local TOCTOU boundary.
• Invested drafts and manual pin ordering remain follow-up work.
• The newly merged t3code mobile Usage dashboard (#5743) is documented but not copied because CodeTwo has no mobile client surface.

Validation

• cargo test --workspace — 349 passed, 0 failed
• cargo check --workspace
• bun run test — 72 passed, 208 assertions across 10 files
• bun run build — TypeScript and Vite production build passed; only the existing large-chunk warning remains
• selected changed Rust files passed rustfmt --check
• git diff --check
• research report covers 96/96 upstream commits and all 22 relative links resolve
• rendered Project settings and Browser fallback states at default and 680 px widths with a clean console; the non-Tauri browser run did not exercise populated native-webview history

Research

See docs/research/t3code-latest-delta-2026-08-09.md for the frozen upstream boundary, evidence, exclusions, and complete commit classification.

[IchenDEV]

Summary

• harden local Usage parsing with Claude message/request deduplication, Codex delta-to-total reconciliation, provider timestamps, streaming reads, a 30-day scan boundary, and a bounded in-process file cache
• persist a Desktop project preference for new-session checkout/worktree mode while preserving CodeTwo's local-ref, pinned-SHA, no-fetch, no-fallback contract
• add versioned, validated, bounded per-project Browser recent sites recorded only after successful native navigation
• make supported workspace @ image references send both ACP pixels and an actionable relative path, with canonical workspace containment, a 16 MB cap, and extension/signature validation
• document an exhaustive 96-commit review of the latest t3code delta and the features deliberately not copied

Why

CodeTwo already had the surrounding UI and runtime seams, but several states were either transient or too trusting: Usage could overcount repeated transcript records and repeatedly rescan whole files, new-session workspace choices were not remembered per project, Browser tabs had no project-local recent history, and image mentions gave the provider pixels without a usable workspace path.

The implementation borrows the product invariants from Usage #5684, project defaults #5766, image paths #5757, and recent sites #5270, adapted to CodeTwo's Tauri/Rust and local-first architecture.

User impact

• Usage totals are more trustworthy and reopening the view avoids reparsing unchanged transcripts during the process lifetime.
• Each Desktop project can start new drafts in the project checkout, a worktree from HEAD, or a worktree from the local origin default ref.
• A blank Browser tab offers recent sites for the active project and lets users remove individual entries.
• Existing workspace image mentions remain canonical in the transcript while the provider receives both pixels and a workspace-relative path it can act on.

Scope and constraints

• Project defaults currently initialize Desktop drafts only; .codetwo.json, global fallback, TUI, and remote-client consumption are not included.
• Usage does not add provider/model/day/cost UI, a durable cache, cross-environment fingerprinting, or LiteLLM pricing.
• Image support applies to existing workspace @ references. It does not add arbitrary clipboard/drag attachments, an app-owned attachment directory, or workspace-external grants. Signature checks are not a full image decoder, and canonicalize-to-open retains the usual local TOCTOU boundary.
• Invested drafts and manual pin ordering remain follow-up work.
• The newly merged t3code mobile Usage dashboard (#5743) is documented but not copied because CodeTwo has no mobile client surface.

Validation

• cargo test --workspace — 349 passed, 0 failed
• cargo check --workspace
• bun run test — 72 passed, 208 assertions across 10 files
• bun run build — TypeScript and Vite production build passed; only the existing large-chunk warning remains
• selected changed Rust files passed rustfmt --check
• git diff --check
• research report covers 96/96 upstream commits and all 22 relative links resolve
• rendered Project settings and Browser fallback states at default and 680 px widths with a clean console; the non-Tauri browser run did not exercise populated native-webview history

Research

See docs/research/t3code-latest-delta-2026-08-09.md for the frozen upstream boundary, evidence, exclusions, and complete commit classification.