[BUG] Desktop app session list omits sessions with entrypoint: sdk-ts (Orca-launched), and worktree-switch also fails for them

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

Sessions created via the Claude Agent SDK (entrypoint: "sdk-ts", e.g. launched by Orca with agent-hooks/claude-hook.cmd) are written to disk in the same project directory as native Desktop sessions (~/.claude/projects/<project>/<sessionId>.jsonl), but do not appear in the Claude Desktop session list/sidebar. The session file is valid and complete — it can be found by session ID or content search — but Desktop's session index appears to filter by entrypoint, silently excluding anything not tagged claude-desktop.

Additionally, attempting to switch to the worktree associated with one of these sessions from the Desktop UI fails/is blocked, likely for the same reason (the UI's worktree-switch logic probably also depends on the session being recognized as native).

Steps to reproduce

1. Launch a Claude Code session via the Agent SDK / Orca (entrypoint: sdk-ts) against a project already open in Claude Desktop.
2. Let the session run and complete (session file appears under ~/.claude/projects/<project>/<sessionId>.jsonl with valid content).
3. Open Claude Desktop and look at the session list for that project.

Expected
The SDK-launched session appears in the list (or is at least discoverable/switchable), since the underlying session file exists and is well-formed.

Actual

• The session does not appear in Desktop's session list at all.
• Session Details panel (when somehow surfaced, e.g. via a linked view) shows a numeric-looking Session ID display and an "Extension ID" field rather than resolving cleanly, which is confusing since the underlying file uses a standard UUID sessionId.
• Attempting to switch to that session's worktree from Desktop fails.

Environment

• Claude Desktop / Claude Code version: 2.1.275 (native session) / 2.1.257 (SDK session)
• Model: claude-sonnet-5
• OS: Windows 11 Pro 10.0.26200
• Session entrypoints involved: claude-desktop (working) vs sdk-ts (not shown)

What Should Happen?

The SDK-launched session appears in the list (or is at least discoverable/switchable), since the underlying session file exists and is well-formed.

Error Messages/Logs

Steps to Reproduce

1. Launch a Claude Code session via the Agent SDK / Orca (entrypoint: sdk-ts) against a project already open in Claude Desktop.
2. Let the session run and complete (session file appears under ~/.claude/projects/<project>/<sessionId>.jsonl with valid content).
3. Open Claude Desktop and look at the session list for that project.

Claude Model

None

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.275

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

_No response_