Skip to content

Context lost when switching devices #46

Closed

Description

@mikeburgh

Firstly, great product, really appreciate the simplicity.

One thing I noticed when switching between local and remote, the context is lost.. I think this happens as it's effectively creating a new session and providing a summary to claude when switching between devices.

I wonder if it would be an option to use the claude --continue feature... eg terminate the session and then start the new one with --continue so it picks up the one just terminated.. that from some quick testing seems to maintain claude's context, rather than a summry.

Activity

  1. ex3ndr commented on Aug 25, 2025

    @ex3ndr
    Contributor

    Hello not sure what you are meaning but we are, in fact, continue session and not starting a new one. Claude code sometimes produces broken sessions so we check them before (really trivial check) continue and if it is broken we start from scratch. Can you tell more information about your setup? OS, version of happy, version of claude? NodeJS version?

  2. mikeburgh commented on Aug 25, 2025

    @mikeburgh
    ContributorAuthor

    Ahh, sorry should have checked the code.. my bad!

    I am using 0.7.2 of the cli, and latest claude, Node 22, and macos.

    It was weird, as I have used /resume a bunch.. and it normally is fine picking up where it left off, but in this case it basically went back and re went through a whole bunch of things already covered.. Will keep an eye on it.. but obviously it's Claude's issue since you are using --continue.

    I will update to 0.9.0 and re open this if I notice it again, and will try and gather some more detailed information if it happens.

  3. ex3ndr commented on Aug 25, 2025

    @ex3ndr
    Contributor

    Debugging and helping with this would be very very helpful, it is an important bug but we dont know what in claude causes session files to disappear or move.

    Any input would help! Lets keep this issue open until we find a problem.

  4. reopened this on Aug 25, 2025
  5. added a commit that references this issue on Jan 19, 2026
    3f36398
  6. added a commit that references this issue on Feb 18, 2026
    79ff188
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions