Refresh the chat screenshot, and the prose the UI change invalidated - #523
Merged
Merged
Conversation
Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
kagent-dev/kagent#2847 renamed the chat's checkpoint to "Snapshot", gave it a generated name, and moved Fork, Rename and Delete onto the snapshot's mark. The refreshed capture in this PR shows that card; the prose still described the old Checkpoint/Fork/Remove strip, and the alt text promised a tool call that the taller card pushed out of frame. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Signed-off-by: Rachael Graham <rachael.graham@solo.io>
Author
Docs preview
Both are uploaded Worker versions and serve no production traffic. |
The chat labels a checkpoint "Snapshot", which collides with the Agent Substrate object of that name: a snapshot is the state an Actor suspends to, and a checkpoint pins one. The section now states the mapping and keeps the concept named checkpoint throughout, so a reader who looks the UI label up in the glossary does not land on the wrong object. Delete now says what it releases, matching suspend-and-resume.md, rather than paraphrasing the button's tooltip. Records in chat.spec.ts why the tool call left the frame, since fullPage does not recover it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Signed-off-by: Rachael Graham <rachael.graham@solo.io>
Rachael-Graham
approved these changes
Sep 23, 2026
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
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.
Refreshes the mock-backed chat screenshots and fixes the prose they broke.
What changed in the UI
kagent-dev/kagent#2847 (Sept 17) renamed the chat's checkpoint to Snapshot, gave it a generated name, and moved Fork, Rename and Delete onto the snapshot's mark. The old
Checkpoint / Fork / Removestrip is gone.The baseline this replaces was captured Sept 15, so it predates that change. #522 refreshed only the Substrate pair, which is why this went unnoticed for eight days.
Prose fixed in
observability/launch-ui.mdCheckpointandFork. There are now three, and they sit on the snapshot's mark.The terminology collision
The UI's "Snapshot" is not the glossary's
Snapshot. In Agent Substrate a snapshot is the state an Actor suspends to; a checkpoint pins one. The UI now applies the word snapshot to the pin. The section states that mapping explicitly and keeps the concept named checkpoint throughout, so looking the UI label up in the glossary does not land on the wrong object. Delete is described as releasing the pin, matchingsubstrate-runtime/suspend-and-resume.md, rather than paraphrasing the button tooltip.Other pages that mention checkpoints were checked and are unaffected — they describe the gRPC API and the runtime, where the name has not changed.
Notes for the reviewer
<agentInstanceId>-<headTaskId>, which reads as a raw UUID. Making it friendlier means naming it in the mock fixture, which lives in the kagent repo.fullPagedoes not reach it. Recorded inchat.spec.ts, not attempted here.create-pull-requestforce-pushes this branch, so the next workflow run would discard the two prose commits.Generated by the Refresh kagent UI screenshots workflow; prose commits added by hand.