Repository navigation
feat(lastcode): safeguard persistent threads - #178
Merged
Merged
Conversation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Persistent recovery threads can currently be archived or deleted without noticing that checkpoint automation still targets them.
This adds one environment-level persistent-thread designation, exposes it in web and desktop context menus, marks the thread with an italic title and message-square-lock icon across web, desktop, and mobile lists, and blocks archive/delete in both the UI and server until persistence is transferred or disabled. The checkpoint dashboard now detects missing or unprotected configured IDs and can atomically repair its supervisor configuration with
--repair-persistent-thread.Validation:
dbbdf0e2127696327bcb240e1daf714d342ac368Implemented with GPT-5.6 Sol through the Codex harness.