Skip to content

Track batch progress per comment, not per batch#12

Open
Sfgangloff wants to merge 1 commit into
paraschopra:mainfrom
Sfgangloff:fix/per-comment-batch-tracking
Open

Track batch progress per comment, not per batch#12
Sfgangloff wants to merge 1 commit into
paraschopra:mainfrom
Sfgangloff:fix/per-comment-batch-tracking

Conversation

@Sfgangloff

Copy link
Copy Markdown

Fixes #10.

The bug

A batch can hold several comments. The page treated the whole batch as done as soon as the agent answered any one of them: the processing state cleared and the remaining comments disappeared from the panel, so they looked handled when they weren't.

The fix

The page now checks each comment id against history. The batch only clears once every comment has been answered. While some are still open it shows N/M done and marks each comment "awaiting" or "addressed", so nothing in a batch gets silently dropped. SKILL.md now tells the agent to answer every comment in a batch.

Changed: lib/feedback.js, lib/feedback.css, SKILL.md.

Testing

Booted the real feedback.js in jsdom with a seeded 3-comment batch and fed it different history.json states:

  • 1 of 3 answered → banner stays, shows 1/3 done, 2 awaiting + 1 addressed (before the fix the banner wrongly cleared — verified against the current main).
  • 3 of 3 answered → banner clears.
  • 0 of 3 answered → 3 awaiting, no false progress.
  • single-comment batch answered → still clears (no regression).

All checks pass. Happy to share the harness.

A submitted batch can hold several comments. The page treated a batch as
"done" as soon as the agent answered any one of its comments: the processing
state cleared and the remaining comments disappeared from the panel, so they
looked handled when they weren't.

Now the page checks each comment id against history. The batch only clears
once every comment has been answered. While some are still open it shows
"N/M done" and marks each comment "awaiting" or "addressed", so nothing in a
batch gets silently dropped. SKILL.md now tells the agent to answer every
comment in a batch.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Only one comment in a batch gets handled; the rest silently disappear

1 participant