Skip to content

[Feature]: Search previous threads across all harnesses in the command palette, and within a single harness #33816

Closed as not planned

Description

@thesobercoder

Before submitting

  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.

Area

apps/web

Problem

I drive several harnesses through T3 Code: Claude Code, Codex, and others. Finding an earlier thread should work the same way whichever harness ran it. Today the command palette can't search by harness:

  • Across harnesses: I want one search that finds any previous thread, whether Claude Code, Codex, Cursor, OpenCode, Pi, or something else ran it, and opens or resumes it.
  • Within one harness: I want to narrow the search to a single harness, for example "my Codex threads about the auth refactor".

Current behavior (main @ fa2f4ff)

Expected behavior

  1. Unified search: Cmd+K finds previous threads from every harness in one ranked list. Each row shows its harness, and Enter opens or resumes the thread.
  2. Harness scoping: typing the harness name, or a filter token such as @codex / @claude, or using a chip or Tab-to-scope, narrows results to that harness. This also works for provider instances (for example two Claude accounts) and could combine with the project and environment filters.
  3. (Follow-up) Sessions started outside T3 in a supported harness also show up in this search and resume as a T3 thread when you open them, with no separate import step. This builds on [Bug]: Session import is unreachable after onboarding, so externally started sessions can never be imported #10961 and its PRs fix(web): import sessions from connected computers #22411 and fix(web): import agent sessions from project settings after onboarding #23122.

Impact

Major degradation or frequent failure

Version or commit

Latest main (fa2f4ff)

Environment

macOS desktop app, with several providers (Claude Code, Codex) used daily

Related

Activity

  1. juliusmarminge commented on Nov 10, 2026

    @juliusmarminge
    Member

    Thanks for writing this up. It asks for new behaviour rather than reporting a defect, so it does not belong in the bug tracker and I'm closing it as not planned here. Feature ideas are discussed in Discussions: please post it there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions