Repository navigation
Confirm the first-version annotation experience #3
Description
Activity
- added a parent issue
on Sep 9, 2026 Resolution
Confirmed with CasperEngl through live discussion in the originating Delta session:
- Annotate whole messages or specific passages in user messages, assistant messages, code blocks, and expanded tool output/diffs within chat. Whole-message comments are the fallback where selection is impractical.
- Highlight the selected passage and display its comment near the source. Show pending comments above the general composer as another view of the same annotations.
- Edit/remove pending comments and jump to their sources. Submit all pending comments plus optional general context together as one turn; annotation-only submission works. Saving comments never sends them to the agent.
- Preserve pending annotations across reloads and devices.
- In the next chronological agent answer, show a compact context card containing the selected excerpt and user comment, then the agent response below the card, not inside it. Do not insert agent answers into old messages. The user's screenshot established this layout; forward navigation links are not a settled requirement.
- Clicking an existing annotation card expands its discussion and supports a follow-up on the same annotation. Follow-ups remain pending until submission.
- Allow annotation of already-visible streaming content, preserving the selected excerpt without interrupting the active turn. Submission must fit existing T3 behavior for sending during a turn.
- Submitted comments remain fixed records of what the agent received; corrections use follow-ups.
- Show Source changed or Source unavailable rather than claiming the comment is no longer useful. Preserve original excerpts; never silently attach to replacement content.
- Pending annotations may be edited, deleted, or explicitly reselected. Reselecting updates the saved excerpt and restores current-source status.
- Submitted annotations support follow-up corrections, hiding at the source, and creating a new annotation on current content; historical submissions and agent responses remain. Rewinds discard annotation submissions with their discarded turns; exact edge cases need investigation.
- Plan eventual web, desktop, and mobile support, with separate implementation tasks for each client and shared infrastructure where appropriate.
- No automatic relocation or resolve/reopen workflow in the first version. Standalone file previews outside chat are excluded.
This records approved product choices, not approval of the earlier speculative storage schema or provider protocol.
Question
What product behavior and boundaries have CasperEngl and the agent agreed on in the originating planning conversation?