Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[MODEL] Excessive chat status lines and gating of an agreed edit during a long review session

Open
  • Is something wrong?
#104,809 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
tooling

Research direction

Start by tracing how relayed review records are handled during long review sessions and where editor suggestions and chat replies are emitted. The report names no files or tests, so first locate those entry points and reproduce the intermittent behavior with a relayed accept or resolve record. Done means an agreed edit is posted without waiting on unrelated accepts, replies are limited to one per thread, and routine records produce no chat status.

Written by the indexing model from the issue text.

Description

area:cowork area:model bug platform:linux
Type of Behavior Issue

Other unexpected behavior

What You Asked Claude to Do

I was reviewing a long document in an editor with comment threads, and a second session relayed review records into this one. I wanted each agreed change posted as an editor suggestion, with little chat traffic.

What Claude Actually Did
  • It posted a chat status line for nearly every relayed accept or resolve record.
  • It stacked several replies on one review thread.
  • It held back an agreed text move until unrelated suggestions were accepted, so the suggestion I expected was not there when I looked.

My message: "not seeing the suggestion you should be putting … why is there so much chatter here? save tokens. put comments instead".

Expected Behavior

Claude should post the agreed edit right away, give one short reply per thread, and send no chat status for routine relayed records.

Permission Mode

Not recorded.

Can You Reproduce This?

Sometimes (intermittent)

Steps to Reproduce
  1. Run a long session that receives relayed review records from another session.
  2. Agree on an edit, and watch whether Claude posts it right away or gates it on unrelated accepts while narrating each record in chat.
Claude Model

Opus 5.5 (claude-opus-5-5), Claude Code 2.1.303, Linux x64

Impact

Low - Minor inconvenience

Dominant language
TypeScript
Stars
154k
Forks
26.1k
Avg merge
1d 14h
Merged PRs (30d)
4

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • No Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from anthropics/claude-code

All issues in anthropics/claude-code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.