[FEATURE] Web sessions and IDE extension are not synced — resuming creates a desynchronized local copy

Resolved 💬 3 comments Opened May 8, 2026 by Pablito-1231 Closed May 12, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

Description

When resuming a Claude Code web session (claude.ai/code) from the IDE extension
(VS Code / VS Code forks like Antigravity), the extension creates a local copy
of the session instead of maintaining a live connection to the cloud session.

This means:

  • Any progress made in the web session after resuming in the IDE is lost locally
  • Any progress made in the IDE does not reflect back in the web session
  • The two contexts diverge immediately after "resuming"

Expected behavior

Resuming a web session from the IDE extension should either:

  1. Keep both in sync in real-time (bidirectional sync), or
  2. Clearly indicate that it is a one-time copy with no ongoing sync,

so users are not misled into thinking they are continuing the same session

Actual behavior

The IDE extension presents a "Resume remote session" option that imports the web
session as a local copy. After that point, the web session and the local session
are completely independent with no synchronization.

Environment

  • IDE: Antigravity (VS Code fork)
  • Claude Code extension (latest)
  • Session started on: claude.ai/code

Impact

Users who switch between the web interface and their IDE lose context and work,
making the workflow between cloud sessions and local development unreliable.

Proposed Solution

The core problem is that the extension and the web session are two separate
runtimes with no communication channel between them. The solution is to make
the extension act as a lightweight client of the cloud session, the same way
VS Code Remote SSH works. This is essentially what GitHub Codespaces + VS Code
Remote do today, but applied to Claude sessions.

Anthropic would need two things:

First, each active cloud session should have a persistent "entry point" that
any client (web, IDE, mobile) can connect to and see the exact same state in
real time: chat messages, files Claude is editing, command output.

Second, the IDE extension should have an "attach to active session" option
instead of "copy session". When you attach, the IDE becomes a window into
Anthropic's VM, not a local copy. You type in the IDE and the message reaches
the same session. Claude responds and you see it identically in both the IDE
and the web.

The session lives in one place (the cloud), and you can look in from anywhere
without breaking anything or causing desync. If you close the IDE, the session
keeps running. If you reopen it, it's exactly where you left off.

Alternative Solutions

_No response_

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗