[Bug]: Session import silently skips many sessions (30-day window, excluded folders) and cannot be re-run or refreshed

[thnk2wn]

Summary

The Claude Code / Codex session import skips many sessions with no explanation, and once it has run there's no supported way to re-run it or to refresh threads whose source session has since been continued.

Environment

• T3 Code 0.1.5 (beta, desktop), macOS 26.7.2
• Claude Code 2.1.314 with cleanupPeriodDays: 90; Codex Desktop

What happened

The import created 82 threads from 161 local Claude Code transcripts and 10 from the Codex sessions. The UI reported "3 failed" with no reason, but far more than 3 sessions were missing. Comparing local transcripts against the imported threads, every missing session falls into one of these silent filters in the session scanner:

1. Hard-coded 30-day window. RECENT_THREAD_WINDOW_MS = 2592e6: only transcripts modified in the last 30 days are eligible. Claude Code's cleanupPeriodDays is not considered, so users who keep 60–90+ days of history lose everything older (about 50 sessions in my case).
2. Excluded working directories. Sessions whose cwd is the home directory, the OS temp dir, /tmp, /private/tmp, or under ~/Downloads / ~/Documents/Codex are dropped (excludedProjectRoots / excludedProjectAncestors). Excluding these as projects makes sense, but the sessions just vanish. This includes Codex Desktop's default ~/Documents/Codex/<date>/… folders and Claude Desktop sessions run from home.
3. cwd no longer exists, or is a git worktree. These sessions are skipped too, with no mention.
4. Per-import budgets (MAX_IMPORT_TRANSCRIPTS = 100, MAX_IMPORT_RECORDS = 1e5) return Skipped once exhausted. That didn't affect me, but it would affect big projects silently.

None of these appear in the result. The UI only shows a "failed" count without reasons.

No way to re-import or refresh

• Import is only reachable from the /welcome onboarding wizard. After onboarding, the only way back that I found was changing the URL to the welcome route from dev tools.
• Imported threads are a one-time snapshot. If a session is continued in Claude Code or Codex afterwards, there's no action to refresh the T3 thread with the new messages. The scanner's sameTranscriptIdentity (size/mtime/inode) check looks like it could detect the change, but nothing exposes a re-scan.

Suggestions

• After import, show a summary of skipped sessions grouped by reason (too old, excluded folder, missing folder, worktree, budget), and give real reasons for failures.
• Make the recent window configurable, or default it to Claude's cleanupPeriodDays.
• Offer a way to import sessions from excluded folders (for example into the "no project" bucket) instead of dropping them.
• Add a "Re-import / refresh sessions" action in settings or per project, and incremental refresh for imported threads whose source transcript changed.