Continuity / Resume v2
Resume from current Git, activity and process state instead of stale saved notes.
Guides follow the current project source. Check the release notes for your installed version.
Factual state wins
RepoTunnel's resume snapshot prioritizes current Git/process/activity evidence and treats Project Memory as semantic context rather than unquestioned live state.
Use after interruption
After an MCP reconnect, app restart or chat interruption, inspect the resume snapshot first and continue from the persisted live state rather than restarting already-completed work.
Recover facts before intentions
Resume v2 considers live Git status, recent activity, managed processes and bounded project context. Saved Project Memory captures useful user decisions, not an authoritative claim that an older task is still open.
After a reconnect or interrupted session, inspect the live resume snapshot first. Compare its recent completed operations with current working-tree state before deciding whether any mutation needs repeating.
What recovery does not do
RepoTunnel cannot detect every way an external chat generation can end, and it should not claim to restart arbitrary conversations invisibly. Its continuation features depend on explicitly supported runtime and client integration.
It is safer to report unresolved/ambiguous work than to claim completion from an old memory or duplicate a side-effectful command.
Use the app’s Project continuity panel
In Projects, inspect the selected workspace’s Current state, active or last-completed work and next step. Add or edit human context when goals or decisions change; factual progress continues updating from activity.
Use History for saved file state and the optional extension only for eligible exact-chat delivery.