fix(steps): preserve timestamps across app restart#74
Merged
johannesjo merged 3 commits intomainfrom Apr 16, 2026
Merged
Conversation
applyTimestamps used `i >= prevCount` with prevCount defaulting to 0, so on the first read after a relaunch every existing entry satisfied the condition and got stamped with the same "now", destroying distinct timestamps from earlier sessions. Treat a missing processedCount map entry as a first observation: seed the counter to the current length and only fill in entries that are missing a timestamp. Subsequent reads keep the existing overwrite-on-new-entry behavior so AI-written timestamps on fresh appends are still replaced with the host clock. https://claude.ai/code/session_016TiVEfjjCB6qw5ZTTC13BE
Clicking the suggested next action immediately wrote the text + CR to the agent via sendPrompt, giving no chance to edit and making accidental clicks irreversible. The commit that introduced it (0660b9b) even described the intended behavior as pre-fill. Route the click through setPrefillPrompt + a focus trigger on the prompt input so the text lands in the textarea and the user can refine and send. https://claude.ai/code/session_016TiVEfjjCB6qw5ZTTC13BE
The createEffect that reported the steps panel's natural height only re-ran when latestStep or isInteracting changed, so width changes that caused the `next` line to wrap left the reported height stale. Observe the latest card with a ResizeObserver and turn latestCardRef into a signal so the observer reattaches when the card element changes. https://claude.ai/code/session_016TiVEfjjCB6qw5ZTTC13BE
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
applyTimestamps used
i >= prevCountwith prevCount defaulting to 0, so onthe first read after a relaunch every existing entry satisfied the condition
and got stamped with the same "now", destroying distinct timestamps from
earlier sessions.
Treat a missing processedCount map entry as a first observation: seed the
counter to the current length and only fill in entries that are missing a
timestamp. Subsequent reads keep the existing overwrite-on-new-entry
behavior so AI-written timestamps on fresh appends are still replaced with
the host clock.
https://claude.ai/code/session_016TiVEfjjCB6qw5ZTTC13BE