Sessions

The Sessions page at app.codeteleport.com lists every session you have pushed to the cloud. From here you can inspect session details, copy pull commands, and delete sessions you no longer need.

Session cards

Each session is displayed as a card with the following information:

Field	Description
Project name	The project directory the session was started in (e.g. `billing-api`)
Summary	A short description of what the session covered, extracted from the conversation
Source machine	The device name the session was pushed from
Date	When the session was last pushed
Size	Bundle size of the uploaded archive
Messages	Total number of messages in the conversation
Model	The AI model used during the session (e.g. `claude-sonnet-4-20250514` for Claude Code, or the corresponding Codex model)

Sessions can originate from any supported AI coding agent — Claude Code, Codex, or Antigravity — and each bundle records which agent produced it (agentId in the bundle metadata). The pull command restores a session for its original agent, so a Codex or Antigravity session is rebuilt for the right agent automatically.

Copy session ID

Each card has a Copy ID button that copies the full session UUID to your clipboard. This is the same ID you pass to codeteleport pull --session-id, or to your agent’s resume command (claude --resume <id>, codex resume <id>, or agy --conversation <id>).

Click the terminal icon on a session card to reveal a popover with the exact CLI command to pull that session onto your current machine:

codeteleport pull --session-id <full-uuid>

Copy and paste it into your terminal to download and install the session. The same codeteleport pull command works regardless of which agent produced the session: the bundle is self-describing, so pull restores the session for whichever agent created it (derived from the bundle’s own recorded agent, not your local config) and prints the correct resume command for that agent (claude --resume <id>, codex resume <id>, or agy --conversation <id>). See codeteleport pull for details on what happens during a pull.

Delete a session

Click the delete button on a session card to remove it from the cloud. A confirmation dialog will appear before anything is deleted.

Empty state

If you have not pushed any sessions yet, the page displays an empty state with a prompt to push your first session using the CLI:

codeteleport push

See codeteleport push for a walkthrough of the push flow.

codeteleport push — upload a session from the CLI
Sessions (concept) — what a session is, what gets bundled, and how sessions are identified