feat(desktop): open threads via t3code:// deep links

[omegent-app]

Managed integration overlay

Role	Value
Base	fork/changes
Head	t3-discord/f7d37879-desktop-deeplinks
Composition	First overlay
Deployment scope	Desktop application

This PR intentionally remains open and draft. Do not merge it. Update the overlay directly, or
start a reviewable child PR with:

pnpm fork:stack overlay-start 10 <branch>

The stack workflow rebases this one-commit overlay and composes it into fork/integration.

Summary

Adds desktop deep-link support so external launchers can open a specific thread in T3 desktop without knowing environment UUIDs. The branch has been rebuilt as one feature commit on the latest fork/changes.

Contracts

t3code://open/thread?connection=t3vm&thread=<thread-uuid>
t3code://t3vm?thread=<thread-uuid>
t3code://t3vm.long.host?thread=<thread-uuid>

Environment resolution priority:

1. the explicitly configured/produced connection value
2. an exact connection-catalog label
3. a unique bidirectional short-host ↔ FQDN match

An exact label always beats a fallback. Different FQDNs never match solely because they share their first component, and multiple FQDN fallback candidates remain ambiguous.

• Navigate to the canonical Electron hash route #/$environmentId/$threadId
• Support cold start, running-instance second-instance, and macOS open-url delivery
• Unknown/ambiguous labels reveal the window without changing its route
• Register t3code as the OS protocol client in packaged builds

Verification

• vp test run apps/desktop/src/app/DesktopDeepLinks.test.ts apps/desktop/src/app/DesktopClerk.test.ts apps/desktop/src/window/DesktopWindow.test.ts (46 passed)
• vp run --filter @t3tools/desktop typecheck
• focused formatting passed

Manual follow-up

• cold start via both explicit and URL-like forms
• second-instance switches/focuses the existing window
• missing or ambiguous environment focuses without route change
• xdg-open after packaged install

opened by Patrick Roza in chat thread Discord · Prepare Desktop Deeplinks

[omegent-app]

Managed integration overlay

Role	Value
Base	fork/changes
Head	t3-discord/f7d37879-desktop-deeplinks
Composition	First overlay
Deployment scope	Desktop application

This PR intentionally remains open and draft. Do not merge it. Update the overlay directly, or
start a reviewable child PR with:

pnpm fork:stack overlay-start 10 <branch>

The stack workflow rebases this one-commit overlay and composes it into fork/integration.

Summary

Adds desktop deep-link support so external launchers can open a specific thread in T3 desktop without knowing environment UUIDs. The branch has been rebuilt as one feature commit on the latest fork/changes.

Contracts

t3code://open/thread?connection=t3vm&thread=<thread-uuid>
t3code://t3vm?thread=<thread-uuid>
t3code://t3vm.long.host?thread=<thread-uuid>

Environment resolution priority:

1. the explicitly configured/produced connection value
2. an exact connection-catalog label
3. a unique bidirectional short-host ↔ FQDN match

An exact label always beats a fallback. Different FQDNs never match solely because they share their first component, and multiple FQDN fallback candidates remain ambiguous.

• Navigate to the canonical Electron hash route #/$environmentId/$threadId
• Support cold start, running-instance second-instance, and macOS open-url delivery
• Unknown/ambiguous labels reveal the window without changing its route
• Register t3code as the OS protocol client in packaged builds

Verification

• vp test run apps/desktop/src/app/DesktopDeepLinks.test.ts apps/desktop/src/app/DesktopClerk.test.ts apps/desktop/src/window/DesktopWindow.test.ts (46 passed)
• vp run --filter @t3tools/desktop typecheck
• focused formatting passed

Manual follow-up

• cold start via both explicit and URL-like forms
• second-instance switches/focuses the existing window
• missing or ambiguous environment focuses without route change
• xdg-open after packaged install

opened by Patrick Roza in chat thread Discord · Prepare Desktop Deeplinks

[omegent-app]

Managed integration overlay

Role	Value
Base	fork/changes
Head	t3-discord/f7d37879-desktop-deeplinks
Composition	First overlay
Deployment scope	Desktop application

This PR intentionally remains open and draft. Do not merge it. Update the overlay directly, or
start a reviewable child PR with:

pnpm fork:stack overlay-start 10 <branch>

The stack workflow rebases this one-commit overlay and composes it into fork/integration.

Summary

Adds desktop deep-link support so external launchers can open a specific thread in T3 desktop without knowing environment UUIDs. The branch has been rebuilt as one feature commit on the latest fork/changes.

Contracts

t3code://open/thread?connection=t3vm&thread=<thread-uuid>
t3code://t3vm?thread=<thread-uuid>
t3code://t3vm.long.host?thread=<thread-uuid>

Environment resolution priority:

1. the explicitly configured/produced connection value
2. an exact connection-catalog label
3. a unique bidirectional short-host ↔ FQDN match

An exact label always beats a fallback. Different FQDNs never match solely because they share their first component, and multiple FQDN fallback candidates remain ambiguous.

• Navigate to the canonical Electron hash route #/$environmentId/$threadId
• Support cold start, running-instance second-instance, and macOS open-url delivery
• Unknown/ambiguous labels reveal the window without changing its route
• Register t3code as the OS protocol client in packaged builds

Verification

• vp test run apps/desktop/src/app/DesktopDeepLinks.test.ts apps/desktop/src/app/DesktopClerk.test.ts apps/desktop/src/window/DesktopWindow.test.ts (46 passed)
• vp run --filter @t3tools/desktop typecheck
• focused formatting passed

Manual follow-up

• cold start via both explicit and URL-like forms
• second-instance switches/focuses the existing window
• missing or ambiguous environment focuses without route change
• xdg-open after packaged install

opened by Patrick Roza in chat thread Discord · Prepare Desktop Deeplinks

[omegent-app]

Managed integration overlay

Role	Value
Base	fork/changes
Head	t3-discord/f7d37879-desktop-deeplinks
Composition	First overlay
Deployment scope	Desktop application

This PR intentionally remains open and draft. Do not merge it. Update the overlay directly, or
start a reviewable child PR with:

pnpm fork:stack overlay-start 10 <branch>

The stack workflow rebases this one-commit overlay and composes it into fork/integration.

Summary

Adds desktop deep-link support so external launchers can open a specific thread in T3 desktop without knowing environment UUIDs. The branch has been rebuilt as one feature commit on the latest fork/changes.

Contracts

t3code://open/thread?connection=t3vm&thread=<thread-uuid>
t3code://t3vm?thread=<thread-uuid>
t3code://t3vm.long.host?thread=<thread-uuid>

Environment resolution priority:

1. the explicitly configured/produced connection value
2. an exact connection-catalog label
3. a unique bidirectional short-host ↔ FQDN match

An exact label always beats a fallback. Different FQDNs never match solely because they share their first component, and multiple FQDN fallback candidates remain ambiguous.

• Navigate to the canonical Electron hash route #/$environmentId/$threadId
• Support cold start, running-instance second-instance, and macOS open-url delivery
• Unknown/ambiguous labels reveal the window without changing its route
• Register t3code as the OS protocol client in packaged builds

Verification

• vp test run apps/desktop/src/app/DesktopDeepLinks.test.ts apps/desktop/src/app/DesktopClerk.test.ts apps/desktop/src/window/DesktopWindow.test.ts (46 passed)
• vp run --filter @t3tools/desktop typecheck
• focused formatting passed

Manual follow-up

• cold start via both explicit and URL-like forms
• second-instance switches/focuses the existing window
• missing or ambiguous environment focuses without route change
• xdg-open after packaged install

opened by Patrick Roza in chat thread Discord · Prepare Desktop Deeplinks

[omegent-app]

Managed integration overlay

Role	Value
Base	fork/changes
Head	t3-discord/f7d37879-desktop-deeplinks
Composition	First overlay
Deployment scope	Desktop application

This PR intentionally remains open and draft. Do not merge it. Update the overlay directly, or
start a reviewable child PR with:

pnpm fork:stack overlay-start 10 <branch>

The stack workflow rebases this one-commit overlay and composes it into fork/integration.

Summary

Adds desktop deep-link support so external launchers can open a specific thread in T3 desktop without knowing environment UUIDs. The branch has been rebuilt as one feature commit on the latest fork/changes.

Contracts

t3code://open/thread?connection=t3vm&thread=<thread-uuid>
t3code://t3vm?thread=<thread-uuid>
t3code://t3vm.long.host?thread=<thread-uuid>

Environment resolution priority:

1. the explicitly configured/produced connection value
2. an exact connection-catalog label
3. a unique bidirectional short-host ↔ FQDN match

An exact label always beats a fallback. Different FQDNs never match solely because they share their first component, and multiple FQDN fallback candidates remain ambiguous.

• Navigate to the canonical Electron hash route #/$environmentId/$threadId
• Support cold start, running-instance second-instance, and macOS open-url delivery
• Unknown/ambiguous labels reveal the window without changing its route
• Register t3code as the OS protocol client in packaged builds

Verification

• vp test run apps/desktop/src/app/DesktopDeepLinks.test.ts apps/desktop/src/app/DesktopClerk.test.ts apps/desktop/src/window/DesktopWindow.test.ts (46 passed)
• vp run --filter @t3tools/desktop typecheck
• focused formatting passed

Manual follow-up

• cold start via both explicit and URL-like forms
• second-instance switches/focuses the existing window
• missing or ambiguous environment focuses without route change
• xdg-open after packaged install

opened by Patrick Roza in chat thread Discord · Prepare Desktop Deeplinks

[omegent-app]

Managed integration overlay

Role	Value
Base	fork/changes
Head	t3-discord/f7d37879-desktop-deeplinks
Composition	First overlay
Deployment scope	Desktop application

This PR intentionally remains open and draft. Do not merge it. Update the overlay directly, or
start a reviewable child PR with:

pnpm fork:stack overlay-start 10 <branch>

The stack workflow rebases this one-commit overlay and composes it into fork/integration.

Summary

Adds desktop deep-link support so external launchers can open a specific thread in T3 desktop without knowing environment UUIDs. The branch has been rebuilt as one feature commit on the latest fork/changes.

Contracts

t3code://open/thread?connection=t3vm&thread=<thread-uuid>
t3code://t3vm?thread=<thread-uuid>
t3code://t3vm.long.host?thread=<thread-uuid>

Environment resolution priority:

1. the explicitly configured/produced connection value
2. an exact connection-catalog label
3. a unique bidirectional short-host ↔ FQDN match

An exact label always beats a fallback. Different FQDNs never match solely because they share their first component, and multiple FQDN fallback candidates remain ambiguous.

• Navigate to the canonical Electron hash route #/$environmentId/$threadId
• Support cold start, running-instance second-instance, and macOS open-url delivery
• Unknown/ambiguous labels reveal the window without changing its route
• Register t3code as the OS protocol client in packaged builds

Verification

• vp test run apps/desktop/src/app/DesktopDeepLinks.test.ts apps/desktop/src/app/DesktopClerk.test.ts apps/desktop/src/window/DesktopWindow.test.ts (46 passed)
• vp run --filter @t3tools/desktop typecheck
• focused formatting passed

Manual follow-up

• cold start via both explicit and URL-like forms
• second-instance switches/focuses the existing window
• missing or ambiguous environment focuses without route change
• xdg-open after packaged install

opened by Patrick Roza in chat thread Discord · Prepare Desktop Deeplinks

[omegent-app]

Managed integration overlay

Role	Value
Base	fork/changes
Head	t3-discord/f7d37879-desktop-deeplinks
Composition	First overlay
Deployment scope	Desktop application

This PR intentionally remains open and draft. Do not merge it. Update the overlay directly, or
start a reviewable child PR with:

pnpm fork:stack overlay-start 10 <branch>

The stack workflow rebases this one-commit overlay and composes it into fork/integration.

Summary

Adds desktop deep-link support so external launchers can open a specific thread in T3 desktop without knowing environment UUIDs. The branch has been rebuilt as one feature commit on the latest fork/changes.

Contracts

t3code://open/thread?connection=t3vm&thread=<thread-uuid>
t3code://t3vm?thread=<thread-uuid>
t3code://t3vm.long.host?thread=<thread-uuid>

Environment resolution priority:

1. the explicitly configured/produced connection value
2. an exact connection-catalog label
3. a unique bidirectional short-host ↔ FQDN match

An exact label always beats a fallback. Different FQDNs never match solely because they share their first component, and multiple FQDN fallback candidates remain ambiguous.

• Navigate to the canonical Electron hash route #/$environmentId/$threadId
• Support cold start, running-instance second-instance, and macOS open-url delivery
• Unknown/ambiguous labels reveal the window without changing its route
• Register t3code as the OS protocol client in packaged builds

Verification

• vp test run apps/desktop/src/app/DesktopDeepLinks.test.ts apps/desktop/src/app/DesktopClerk.test.ts apps/desktop/src/window/DesktopWindow.test.ts (46 passed)
• vp run --filter @t3tools/desktop typecheck
• focused formatting passed

Manual follow-up

• cold start via both explicit and URL-like forms
• second-instance switches/focuses the existing window
• missing or ambiguous environment focuses without route change
• xdg-open after packaged install

opened by Patrick Roza in chat thread Discord · Prepare Desktop Deeplinks

[omegent-app]

Managed integration overlay

Role	Value
Base	fork/changes
Head	t3-discord/f7d37879-desktop-deeplinks
Composition	First overlay
Deployment scope	Desktop application

This PR intentionally remains open and draft. Do not merge it. Update the overlay directly, or
start a reviewable child PR with:

pnpm fork:stack overlay-start 10 <branch>

The stack workflow rebases this one-commit overlay and composes it into fork/integration.

Summary

Adds desktop deep-link support so external launchers can open a specific thread in T3 desktop without knowing environment UUIDs. The branch has been rebuilt as one feature commit on the latest fork/changes.

Contracts

t3code://open/thread?connection=t3vm&thread=<thread-uuid>
t3code://t3vm?thread=<thread-uuid>
t3code://t3vm.long.host?thread=<thread-uuid>

Environment resolution priority:

1. the explicitly configured/produced connection value
2. an exact connection-catalog label
3. a unique bidirectional short-host ↔ FQDN match

An exact label always beats a fallback. Different FQDNs never match solely because they share their first component, and multiple FQDN fallback candidates remain ambiguous.

• Navigate to the canonical Electron hash route #/$environmentId/$threadId
• Support cold start, running-instance second-instance, and macOS open-url delivery
• Unknown/ambiguous labels reveal the window without changing its route
• Register t3code as the OS protocol client in packaged builds

Verification

• vp test run apps/desktop/src/app/DesktopDeepLinks.test.ts apps/desktop/src/app/DesktopClerk.test.ts apps/desktop/src/window/DesktopWindow.test.ts (46 passed)
• vp run --filter @t3tools/desktop typecheck
• focused formatting passed

Manual follow-up

• cold start via both explicit and URL-like forms
• second-instance switches/focuses the existing window
• missing or ambiguous environment focuses without route change
• xdg-open after packaged install

opened by Patrick Roza in chat thread Discord · Prepare Desktop Deeplinks