Draft: teleport backend — import/export engine - #8
Conversation
Contracts, orchestration, and the teleport service land first. Native CLI formats register later, so list/import/export stay empty until a provider adapter is added. Co-authored-by: aanishbhirud <aanishbhirud@gmail.com>
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
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. Comment |
Keep personal project directories out of the public diff. Co-authored-by: aanishbhirud <aanishbhirud@gmail.com>
Thread transfer impact
This comment will update automatically after the next completed run. |
What Changed
The teleport engine: contracts,
thread.history.replace, presence, and the server service that lists, imports, and exports native CLI sessions.Native files stay native. Import copies a CLI session onto a T3 thread. Export writes the thread back. Presence (
t3vsnative) is persisted so both sides are not writers at once.No CLI format adapters are registered yet.
listSessionsreturns an empty list. Import/export of an unregistered provider fails closed. Adapters land in the Codex / Claude / Grok / OpenCode PRs on top of this one.Why
Two-way teleport needs one shared engine before any provider-specific format. This is that engine.
Stack
mainUI Changes
None. The picker and export button land in the next PR.
Checklist