Draft: two-way teleport with native CLI sessions

[baanish]

Draft. Do not merge. Exploration of two-way teleport. Opened as one PR because GitHub cannot stack cross-fork bases on this repo.

What Changed

T3 Code can list, import, and export native CLI sessions for Codex, and Claude.
Native files stay native. Import copies a CLI session onto a T3 thread. Export writes the thread back. Presence (t3 vs native) swaps Import/Export so both sides are not writers at once.
Codex export writes session_meta the CLI can resume. OpenCode imports text turns only, does not treat live opencode.db as a foreign lock, and does not match parent cwds into sibling codex / claude / grok folders. Stop settles Working when the turn is aborted, when there is no live session, or when interrupt fails.

UI

Import lives on the new-thread / sessions view. Export lives in the chat header. Composer send is disabled while the thread is in the native CLI.

New UI

Hover

Composer disabled after Teleport Out

Recordings

Codex

Claude

Why

Two-way teleport needs a shared engine, UI, and one adapter per CLI. This PR is that whole stack in one diff because stacked bases have to exist on pingdotgg/t3code.

UI Changes

Import lives on the new-thread / sessions view. Export lives in the chat header. Composer send is disabled while the thread is in the native CLI.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes

Relates to #207, #5146, #5741, and #6590.

Note

Add two-way teleport between app threads and native CLI sessions

• Introduces a full teleport system allowing threads to be exported to native CLI sessions (Claude, Codex, Grok, OpenCode) and imported back, with message history synchronization via new thread.history.replace and thread.teleport.set orchestration commands.
• Adds TeleportService with list/import/export session RPCs (teleport.listSessions, teleport.importSessions, teleport.exportSession) wired into the WS layer with scope-based authorization.
• Adds per-provider JSONL/directory format adapters with schema-version gating, file-lock detection, and atomic writes; a registry pattern enables runtime format registration.
• Extends the command palette and chat UI with session browsing, import flows, a TeleportOutButton in the chat header, and composer/send disabling when a thread is teleported-out.
• Adds DB migration 041 adding teleport_json to projection_threads with backfill from existing runtime telemetry.
• Risk: thread.turn.start now fails with OrchestrationCommandInvariantError if the thread's teleport presence is native, blocking turn creation on teleported-out threads.

📊 Macroscope summarized 18ed3c0. 52 files reviewed, 0 issues evaluated, 0 issues filtered, 0 comments posted

🗂️ Filtered Issues

No issues evaluated.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 8a86460d-dc34-4a24-9c87-02e715f5dd10

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Two small consistency findings in the new teleport UI. Everything else in the changed web files (command palette views, composer disabled/placeholder handling, ChatView toast) follows the existing primitives and layout conventions.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Effect service conventions review of the new TeleportService (plus its contract errors). Four convention violations found; details inline.

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

One finding: the new header control's disabled state suppresses the tooltip that explains why it is unavailable.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Two error-modeling convention issues in the new teleport code: message stored as data when it is a fixed template over existing attributes, and a helper whose only behavior is constructing that error.

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

Reviewed the new teleport service against the Effect service conventions. Service shape (Context.Service with inline interface, exported make/layer), dependency acquisition via yield*, and Effect.catchTags usage all look right now. Three remaining error-modelling issues below.

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

One finding: the new chat-header teleport button loses the themed toolbar control styling because the tooltip wrapper overwrites data-slot="button". See the inline comment for the one-attribute fix.

^{Posted via Macroscope — UI Consistency}

[t3-code]

closing because this is explicitly marked Draft. Do not merge. and documents cross-fork teleport exploration rather than merge-ready work.

[baanish]

Draft. Do not merge. Exploration of two-way teleport. Opened as one PR because GitHub cannot stack cross-fork bases on this repo.

What Changed

T3 Code can list, import, and export native CLI sessions for Codex, and Claude.
Native files stay native. Import copies a CLI session onto a T3 thread. Export writes the thread back. Presence (t3 vs native) swaps Import/Export so both sides are not writers at once.
Codex export writes session_meta the CLI can resume. OpenCode imports text turns only, does not treat live opencode.db as a foreign lock, and does not match parent cwds into sibling codex / claude / grok folders. Stop settles Working when the turn is aborted, when there is no live session, or when interrupt fails.

UI

Import lives on the new-thread / sessions view. Export lives in the chat header. Composer send is disabled while the thread is in the native CLI.

New UI

Hover

Composer disabled after Teleport Out

Recordings

Codex

Claude

Why

Two-way teleport needs a shared engine, UI, and one adapter per CLI. This PR is that whole stack in one diff because stacked bases have to exist on pingdotgg/t3code.

UI Changes

Import lives on the new-thread / sessions view. Export lives in the chat header. Composer send is disabled while the thread is in the native CLI.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes

Relates to #207, #5146, #5741, and #6590.

Note

Add two-way teleport between app threads and native CLI sessions

• Introduces a full teleport system allowing threads to be exported to native CLI sessions (Claude, Codex, Grok, OpenCode) and imported back, with message history synchronization via new thread.history.replace and thread.teleport.set orchestration commands.
• Adds TeleportService with list/import/export session RPCs (teleport.listSessions, teleport.importSessions, teleport.exportSession) wired into the WS layer with scope-based authorization.
• Adds per-provider JSONL/directory format adapters with schema-version gating, file-lock detection, and atomic writes; a registry pattern enables runtime format registration.
• Extends the command palette and chat UI with session browsing, import flows, a TeleportOutButton in the chat header, and composer/send disabling when a thread is teleported-out.
• Adds DB migration 041 adding teleport_json to projection_threads with backfill from existing runtime telemetry.
• Risk: thread.turn.start now fails with OrchestrationCommandInvariantError if the thread's teleport presence is native, blocking turn creation on teleported-out threads.

📊 Macroscope summarized 18ed3c0. 52 files reviewed, 0 issues evaluated, 0 issues filtered, 0 comments posted

🗂️ Filtered Issues

No issues evaluated.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 8a86460d-dc34-4a24-9c87-02e715f5dd10

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Two small consistency findings in the new teleport UI. Everything else in the changed web files (command palette views, composer disabled/placeholder handling, ChatView toast) follows the existing primitives and layout conventions.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Effect service conventions review of the new TeleportService (plus its contract errors). Four convention violations found; details inline.

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

One finding: the new header control's disabled state suppresses the tooltip that explains why it is unavailable.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Two error-modeling convention issues in the new teleport code: message stored as data when it is a fixed template over existing attributes, and a helper whose only behavior is constructing that error.

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

Reviewed the new teleport service against the Effect service conventions. Service shape (Context.Service with inline interface, exported make/layer), dependency acquisition via yield*, and Effect.catchTags usage all look right now. Three remaining error-modelling issues below.

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

One finding: the new chat-header teleport button loses the themed toolbar control styling because the tooltip wrapper overwrites data-slot="button". See the inline comment for the one-attribute fix.

^{Posted via Macroscope — UI Consistency}

[t3-code]

closing because this is explicitly marked Draft. Do not merge. and documents cross-fork teleport exploration rather than merge-ready work.

[baanish]

Draft. Do not merge. Exploration of two-way teleport. Opened as one PR because GitHub cannot stack cross-fork bases on this repo.

What Changed

T3 Code can list, import, and export native CLI sessions for Codex, and Claude.
Native files stay native. Import copies a CLI session onto a T3 thread. Export writes the thread back. Presence (t3 vs native) swaps Import/Export so both sides are not writers at once.
Codex export writes session_meta the CLI can resume. OpenCode imports text turns only, does not treat live opencode.db as a foreign lock, and does not match parent cwds into sibling codex / claude / grok folders. Stop settles Working when the turn is aborted, when there is no live session, or when interrupt fails.

UI

Import lives on the new-thread / sessions view. Export lives in the chat header. Composer send is disabled while the thread is in the native CLI.

New UI

Hover

Composer disabled after Teleport Out

Recordings

Codex

Claude

Why

Two-way teleport needs a shared engine, UI, and one adapter per CLI. This PR is that whole stack in one diff because stacked bases have to exist on pingdotgg/t3code.

UI Changes

Import lives on the new-thread / sessions view. Export lives in the chat header. Composer send is disabled while the thread is in the native CLI.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes

Relates to #207, #5146, #5741, and #6590.

Note

Add two-way teleport between app threads and native CLI sessions

• Introduces a full teleport system allowing threads to be exported to native CLI sessions (Claude, Codex, Grok, OpenCode) and imported back, with message history synchronization via new thread.history.replace and thread.teleport.set orchestration commands.
• Adds TeleportService with list/import/export session RPCs (teleport.listSessions, teleport.importSessions, teleport.exportSession) wired into the WS layer with scope-based authorization.
• Adds per-provider JSONL/directory format adapters with schema-version gating, file-lock detection, and atomic writes; a registry pattern enables runtime format registration.
• Extends the command palette and chat UI with session browsing, import flows, a TeleportOutButton in the chat header, and composer/send disabling when a thread is teleported-out.
• Adds DB migration 041 adding teleport_json to projection_threads with backfill from existing runtime telemetry.
• Risk: thread.turn.start now fails with OrchestrationCommandInvariantError if the thread's teleport presence is native, blocking turn creation on teleported-out threads.

📊 Macroscope summarized 18ed3c0. 52 files reviewed, 0 issues evaluated, 0 issues filtered, 0 comments posted

🗂️ Filtered Issues

No issues evaluated.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 8a86460d-dc34-4a24-9c87-02e715f5dd10

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Two small consistency findings in the new teleport UI. Everything else in the changed web files (command palette views, composer disabled/placeholder handling, ChatView toast) follows the existing primitives and layout conventions.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Effect service conventions review of the new TeleportService (plus its contract errors). Four convention violations found; details inline.

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

One finding: the new header control's disabled state suppresses the tooltip that explains why it is unavailable.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Two error-modeling convention issues in the new teleport code: message stored as data when it is a fixed template over existing attributes, and a helper whose only behavior is constructing that error.

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

Reviewed the new teleport service against the Effect service conventions. Service shape (Context.Service with inline interface, exported make/layer), dependency acquisition via yield*, and Effect.catchTags usage all look right now. Three remaining error-modelling issues below.

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

One finding: the new chat-header teleport button loses the themed toolbar control styling because the tooltip wrapper overwrites data-slot="button". See the inline comment for the one-attribute fix.

^{Posted via Macroscope — UI Consistency}

[t3-code]

closing because this is explicitly marked Draft. Do not merge. and documents cross-fork teleport exploration rather than merge-ready work.

[baanish]

Draft. Do not merge. Exploration of two-way teleport. Opened as one PR because GitHub cannot stack cross-fork bases on this repo.

What Changed

T3 Code can list, import, and export native CLI sessions for Codex, and Claude.
Native files stay native. Import copies a CLI session onto a T3 thread. Export writes the thread back. Presence (t3 vs native) swaps Import/Export so both sides are not writers at once.
Codex export writes session_meta the CLI can resume. OpenCode imports text turns only, does not treat live opencode.db as a foreign lock, and does not match parent cwds into sibling codex / claude / grok folders. Stop settles Working when the turn is aborted, when there is no live session, or when interrupt fails.

UI

Import lives on the new-thread / sessions view. Export lives in the chat header. Composer send is disabled while the thread is in the native CLI.

New UI

Hover

Composer disabled after Teleport Out

Recordings

Codex

Claude

Why

Two-way teleport needs a shared engine, UI, and one adapter per CLI. This PR is that whole stack in one diff because stacked bases have to exist on pingdotgg/t3code.

UI Changes

Import lives on the new-thread / sessions view. Export lives in the chat header. Composer send is disabled while the thread is in the native CLI.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes

Relates to #207, #5146, #5741, and #6590.

Note

Add two-way teleport between app threads and native CLI sessions

• Introduces a full teleport system allowing threads to be exported to native CLI sessions (Claude, Codex, Grok, OpenCode) and imported back, with message history synchronization via new thread.history.replace and thread.teleport.set orchestration commands.
• Adds TeleportService with list/import/export session RPCs (teleport.listSessions, teleport.importSessions, teleport.exportSession) wired into the WS layer with scope-based authorization.
• Adds per-provider JSONL/directory format adapters with schema-version gating, file-lock detection, and atomic writes; a registry pattern enables runtime format registration.
• Extends the command palette and chat UI with session browsing, import flows, a TeleportOutButton in the chat header, and composer/send disabling when a thread is teleported-out.
• Adds DB migration 041 adding teleport_json to projection_threads with backfill from existing runtime telemetry.
• Risk: thread.turn.start now fails with OrchestrationCommandInvariantError if the thread's teleport presence is native, blocking turn creation on teleported-out threads.

📊 Macroscope summarized 18ed3c0. 52 files reviewed, 0 issues evaluated, 0 issues filtered, 0 comments posted

🗂️ Filtered Issues

No issues evaluated.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 8a86460d-dc34-4a24-9c87-02e715f5dd10

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Two small consistency findings in the new teleport UI. Everything else in the changed web files (command palette views, composer disabled/placeholder handling, ChatView toast) follows the existing primitives and layout conventions.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Effect service conventions review of the new TeleportService (plus its contract errors). Four convention violations found; details inline.

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

One finding: the new header control's disabled state suppresses the tooltip that explains why it is unavailable.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Two error-modeling convention issues in the new teleport code: message stored as data when it is a fixed template over existing attributes, and a helper whose only behavior is constructing that error.

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

Reviewed the new teleport service against the Effect service conventions. Service shape (Context.Service with inline interface, exported make/layer), dependency acquisition via yield*, and Effect.catchTags usage all look right now. Three remaining error-modelling issues below.

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

One finding: the new chat-header teleport button loses the themed toolbar control styling because the tooltip wrapper overwrites data-slot="button". See the inline comment for the one-attribute fix.

^{Posted via Macroscope — UI Consistency}

[t3-code]

closing because this is explicitly marked Draft. Do not merge. and documents cross-fork teleport exploration rather than merge-ready work.

[baanish]

Draft. Do not merge. Exploration of two-way teleport. Opened as one PR because GitHub cannot stack cross-fork bases on this repo.

What Changed

T3 Code can list, import, and export native CLI sessions for Codex, and Claude.
Native files stay native. Import copies a CLI session onto a T3 thread. Export writes the thread back. Presence (t3 vs native) swaps Import/Export so both sides are not writers at once.
Codex export writes session_meta the CLI can resume. OpenCode imports text turns only, does not treat live opencode.db as a foreign lock, and does not match parent cwds into sibling codex / claude / grok folders. Stop settles Working when the turn is aborted, when there is no live session, or when interrupt fails.

UI

Import lives on the new-thread / sessions view. Export lives in the chat header. Composer send is disabled while the thread is in the native CLI.

New UI

Hover

Composer disabled after Teleport Out

Recordings

Codex

Claude

Why

Two-way teleport needs a shared engine, UI, and one adapter per CLI. This PR is that whole stack in one diff because stacked bases have to exist on pingdotgg/t3code.

UI Changes

Import lives on the new-thread / sessions view. Export lives in the chat header. Composer send is disabled while the thread is in the native CLI.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes

Relates to #207, #5146, #5741, and #6590.

Note

Add two-way teleport between app threads and native CLI sessions

• Introduces a full teleport system allowing threads to be exported to native CLI sessions (Claude, Codex, Grok, OpenCode) and imported back, with message history synchronization via new thread.history.replace and thread.teleport.set orchestration commands.
• Adds TeleportService with list/import/export session RPCs (teleport.listSessions, teleport.importSessions, teleport.exportSession) wired into the WS layer with scope-based authorization.
• Adds per-provider JSONL/directory format adapters with schema-version gating, file-lock detection, and atomic writes; a registry pattern enables runtime format registration.
• Extends the command palette and chat UI with session browsing, import flows, a TeleportOutButton in the chat header, and composer/send disabling when a thread is teleported-out.
• Adds DB migration 041 adding teleport_json to projection_threads with backfill from existing runtime telemetry.
• Risk: thread.turn.start now fails with OrchestrationCommandInvariantError if the thread's teleport presence is native, blocking turn creation on teleported-out threads.

📊 Macroscope summarized 18ed3c0. 52 files reviewed, 0 issues evaluated, 0 issues filtered, 0 comments posted

🗂️ Filtered Issues

No issues evaluated.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 8a86460d-dc34-4a24-9c87-02e715f5dd10

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Two small consistency findings in the new teleport UI. Everything else in the changed web files (command palette views, composer disabled/placeholder handling, ChatView toast) follows the existing primitives and layout conventions.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Effect service conventions review of the new TeleportService (plus its contract errors). Four convention violations found; details inline.

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

One finding: the new header control's disabled state suppresses the tooltip that explains why it is unavailable.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Two error-modeling convention issues in the new teleport code: message stored as data when it is a fixed template over existing attributes, and a helper whose only behavior is constructing that error.

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

Reviewed the new teleport service against the Effect service conventions. Service shape (Context.Service with inline interface, exported make/layer), dependency acquisition via yield*, and Effect.catchTags usage all look right now. Three remaining error-modelling issues below.

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

One finding: the new chat-header teleport button loses the themed toolbar control styling because the tooltip wrapper overwrites data-slot="button". See the inline comment for the one-attribute fix.

^{Posted via Macroscope — UI Consistency}

[t3-code]

closing because this is explicitly marked Draft. Do not merge. and documents cross-fork teleport exploration rather than merge-ready work.

[baanish]

Draft. Do not merge. Exploration of two-way teleport. Opened as one PR because GitHub cannot stack cross-fork bases on this repo.

What Changed

T3 Code can list, import, and export native CLI sessions for Codex, and Claude.
Native files stay native. Import copies a CLI session onto a T3 thread. Export writes the thread back. Presence (t3 vs native) swaps Import/Export so both sides are not writers at once.
Codex export writes session_meta the CLI can resume. OpenCode imports text turns only, does not treat live opencode.db as a foreign lock, and does not match parent cwds into sibling codex / claude / grok folders. Stop settles Working when the turn is aborted, when there is no live session, or when interrupt fails.

UI

Import lives on the new-thread / sessions view. Export lives in the chat header. Composer send is disabled while the thread is in the native CLI.

New UI

Hover

Composer disabled after Teleport Out

Recordings

Codex

Claude

Why

Two-way teleport needs a shared engine, UI, and one adapter per CLI. This PR is that whole stack in one diff because stacked bases have to exist on pingdotgg/t3code.

UI Changes

Import lives on the new-thread / sessions view. Export lives in the chat header. Composer send is disabled while the thread is in the native CLI.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes

Relates to #207, #5146, #5741, and #6590.

Note

Add two-way teleport between app threads and native CLI sessions

• Introduces a full teleport system allowing threads to be exported to native CLI sessions (Claude, Codex, Grok, OpenCode) and imported back, with message history synchronization via new thread.history.replace and thread.teleport.set orchestration commands.
• Adds TeleportService with list/import/export session RPCs (teleport.listSessions, teleport.importSessions, teleport.exportSession) wired into the WS layer with scope-based authorization.
• Adds per-provider JSONL/directory format adapters with schema-version gating, file-lock detection, and atomic writes; a registry pattern enables runtime format registration.
• Extends the command palette and chat UI with session browsing, import flows, a TeleportOutButton in the chat header, and composer/send disabling when a thread is teleported-out.
• Adds DB migration 041 adding teleport_json to projection_threads with backfill from existing runtime telemetry.
• Risk: thread.turn.start now fails with OrchestrationCommandInvariantError if the thread's teleport presence is native, blocking turn creation on teleported-out threads.

📊 Macroscope summarized 18ed3c0. 52 files reviewed, 0 issues evaluated, 0 issues filtered, 0 comments posted

🗂️ Filtered Issues

No issues evaluated.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 8a86460d-dc34-4a24-9c87-02e715f5dd10

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Two small consistency findings in the new teleport UI. Everything else in the changed web files (command palette views, composer disabled/placeholder handling, ChatView toast) follows the existing primitives and layout conventions.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Effect service conventions review of the new TeleportService (plus its contract errors). Four convention violations found; details inline.

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

One finding: the new header control's disabled state suppresses the tooltip that explains why it is unavailable.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Two error-modeling convention issues in the new teleport code: message stored as data when it is a fixed template over existing attributes, and a helper whose only behavior is constructing that error.

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

Reviewed the new teleport service against the Effect service conventions. Service shape (Context.Service with inline interface, exported make/layer), dependency acquisition via yield*, and Effect.catchTags usage all look right now. Three remaining error-modelling issues below.

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

One finding: the new chat-header teleport button loses the themed toolbar control styling because the tooltip wrapper overwrites data-slot="button". See the inline comment for the one-attribute fix.

^{Posted via Macroscope — UI Consistency}

[t3-code]

closing because this is explicitly marked Draft. Do not merge. and documents cross-fork teleport exploration rather than merge-ready work.

[baanish]

Draft. Do not merge. Exploration of two-way teleport. Opened as one PR because GitHub cannot stack cross-fork bases on this repo.

What Changed

T3 Code can list, import, and export native CLI sessions for Codex, and Claude.
Native files stay native. Import copies a CLI session onto a T3 thread. Export writes the thread back. Presence (t3 vs native) swaps Import/Export so both sides are not writers at once.
Codex export writes session_meta the CLI can resume. OpenCode imports text turns only, does not treat live opencode.db as a foreign lock, and does not match parent cwds into sibling codex / claude / grok folders. Stop settles Working when the turn is aborted, when there is no live session, or when interrupt fails.

UI

Import lives on the new-thread / sessions view. Export lives in the chat header. Composer send is disabled while the thread is in the native CLI.

New UI

Hover

Composer disabled after Teleport Out

Recordings

Codex

Claude

Why

Two-way teleport needs a shared engine, UI, and one adapter per CLI. This PR is that whole stack in one diff because stacked bases have to exist on pingdotgg/t3code.

UI Changes

Import lives on the new-thread / sessions view. Export lives in the chat header. Composer send is disabled while the thread is in the native CLI.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes

Relates to #207, #5146, #5741, and #6590.

Note

Add two-way teleport between app threads and native CLI sessions

• Introduces a full teleport system allowing threads to be exported to native CLI sessions (Claude, Codex, Grok, OpenCode) and imported back, with message history synchronization via new thread.history.replace and thread.teleport.set orchestration commands.
• Adds TeleportService with list/import/export session RPCs (teleport.listSessions, teleport.importSessions, teleport.exportSession) wired into the WS layer with scope-based authorization.
• Adds per-provider JSONL/directory format adapters with schema-version gating, file-lock detection, and atomic writes; a registry pattern enables runtime format registration.
• Extends the command palette and chat UI with session browsing, import flows, a TeleportOutButton in the chat header, and composer/send disabling when a thread is teleported-out.
• Adds DB migration 041 adding teleport_json to projection_threads with backfill from existing runtime telemetry.
• Risk: thread.turn.start now fails with OrchestrationCommandInvariantError if the thread's teleport presence is native, blocking turn creation on teleported-out threads.

📊 Macroscope summarized 18ed3c0. 52 files reviewed, 0 issues evaluated, 0 issues filtered, 0 comments posted

🗂️ Filtered Issues

No issues evaluated.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 8a86460d-dc34-4a24-9c87-02e715f5dd10

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Two small consistency findings in the new teleport UI. Everything else in the changed web files (command palette views, composer disabled/placeholder handling, ChatView toast) follows the existing primitives and layout conventions.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Effect service conventions review of the new TeleportService (plus its contract errors). Four convention violations found; details inline.

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

One finding: the new header control's disabled state suppresses the tooltip that explains why it is unavailable.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Two error-modeling convention issues in the new teleport code: message stored as data when it is a fixed template over existing attributes, and a helper whose only behavior is constructing that error.

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

Reviewed the new teleport service against the Effect service conventions. Service shape (Context.Service with inline interface, exported make/layer), dependency acquisition via yield*, and Effect.catchTags usage all look right now. Three remaining error-modelling issues below.

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

One finding: the new chat-header teleport button loses the themed toolbar control styling because the tooltip wrapper overwrites data-slot="button". See the inline comment for the one-attribute fix.

^{Posted via Macroscope — UI Consistency}

[t3-code]

closing because this is explicitly marked Draft. Do not merge. and documents cross-fork teleport exploration rather than merge-ready work.

[baanish]

Draft. Do not merge. Exploration of two-way teleport. Opened as one PR because GitHub cannot stack cross-fork bases on this repo.

What Changed

T3 Code can list, import, and export native CLI sessions for Codex, and Claude.
Native files stay native. Import copies a CLI session onto a T3 thread. Export writes the thread back. Presence (t3 vs native) swaps Import/Export so both sides are not writers at once.
Codex export writes session_meta the CLI can resume. OpenCode imports text turns only, does not treat live opencode.db as a foreign lock, and does not match parent cwds into sibling codex / claude / grok folders. Stop settles Working when the turn is aborted, when there is no live session, or when interrupt fails.

UI

Import lives on the new-thread / sessions view. Export lives in the chat header. Composer send is disabled while the thread is in the native CLI.

New UI

Hover

Composer disabled after Teleport Out

Recordings

Codex

Claude

Why

Two-way teleport needs a shared engine, UI, and one adapter per CLI. This PR is that whole stack in one diff because stacked bases have to exist on pingdotgg/t3code.

UI Changes

Import lives on the new-thread / sessions view. Export lives in the chat header. Composer send is disabled while the thread is in the native CLI.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes

Relates to #207, #5146, #5741, and #6590.

Note

Add two-way teleport between app threads and native CLI sessions

• Introduces a full teleport system allowing threads to be exported to native CLI sessions (Claude, Codex, Grok, OpenCode) and imported back, with message history synchronization via new thread.history.replace and thread.teleport.set orchestration commands.
• Adds TeleportService with list/import/export session RPCs (teleport.listSessions, teleport.importSessions, teleport.exportSession) wired into the WS layer with scope-based authorization.
• Adds per-provider JSONL/directory format adapters with schema-version gating, file-lock detection, and atomic writes; a registry pattern enables runtime format registration.
• Extends the command palette and chat UI with session browsing, import flows, a TeleportOutButton in the chat header, and composer/send disabling when a thread is teleported-out.
• Adds DB migration 041 adding teleport_json to projection_threads with backfill from existing runtime telemetry.
• Risk: thread.turn.start now fails with OrchestrationCommandInvariantError if the thread's teleport presence is native, blocking turn creation on teleported-out threads.

📊 Macroscope summarized 18ed3c0. 52 files reviewed, 0 issues evaluated, 0 issues filtered, 0 comments posted

🗂️ Filtered Issues

No issues evaluated.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 8a86460d-dc34-4a24-9c87-02e715f5dd10

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Two small consistency findings in the new teleport UI. Everything else in the changed web files (command palette views, composer disabled/placeholder handling, ChatView toast) follows the existing primitives and layout conventions.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Effect service conventions review of the new TeleportService (plus its contract errors). Four convention violations found; details inline.

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

One finding: the new header control's disabled state suppresses the tooltip that explains why it is unavailable.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Two error-modeling convention issues in the new teleport code: message stored as data when it is a fixed template over existing attributes, and a helper whose only behavior is constructing that error.

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

Reviewed the new teleport service against the Effect service conventions. Service shape (Context.Service with inline interface, exported make/layer), dependency acquisition via yield*, and Effect.catchTags usage all look right now. Three remaining error-modelling issues below.

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

One finding: the new chat-header teleport button loses the themed toolbar control styling because the tooltip wrapper overwrites data-slot="button". See the inline comment for the one-attribute fix.

^{Posted via Macroscope — UI Consistency}

[t3-code]

closing because this is explicitly marked Draft. Do not merge. and documents cross-fork teleport exploration rather than merge-ready work.