Here's what I found while triaging this issue:

This looks like a code-review/agent button-state bug, but the public report does not include enough detail to tell which disabled condition is wrong. The button can be intentionally disabled when there are no non-outdated comments, no eligible terminal, AI is disabled without a CLI agent, or AI credits are unavailable.

I have a few follow-up questions before I can narrow this down:

Could you attach a screenshot or short screen recording showing the disabled Send to Agent button and its tooltip?
What are the minimal steps that make the button become disabled when you expect it to be enabled?

Reply in-thread with those details and the triage workflow will automatically re-evaluate the issue and update the diagnosis, labels, and next steps.

Maintainer details

I concluded that the report indicates the code-review Send to Agent button can be disabled incorrectly, but the public issue lacks reproduction details beyond the title and Linear link..

Triage summary

The issue appears to be a bug in the code-review flow where the Send to Agent button is disabled when the user expects it to be enabled. The public report only contains the Linear link/title, so this needs reporter details before maintainers can identify which disabled-state branch is wrong.

Evidence from code inspection

app/src/code_review/comment_list_view.rs computes the Send to Agent enabled state from ReviewDestination, whether there are non-outdated comments, and AI credit availability. CLI-agent destinations bypass AI-credit checks.
app/src/workspace/view/right_panel.rs computes ReviewDestination by looking for an available terminal in the selected repo. When AI is disabled, only active CLI-agent terminals are considered available; otherwise idle Warp terminals can be destinations.
app/src/code_review/code_review_view.rs gathers non-outdated review comments and emits SubmitReviewComments, which the right panel routes to either a CLI agent/rich input or Warp Agent review.
Existing APP-3892 specs describe several intended disabled states: no non-outdated comments, AI disabled with no CLI agent, no AI credits, all terminals busy, or no matching repo terminal. The current report does not say which of these states was present or why it was incorrect.

Duplicate search

I enumerated 3,194 open non-PR issues via the GitHub API, excluding #9761, and checked recently closed issues from the last seven days. No exact duplicate for Send Comment to Agent Disabled Incorrectly or Send to Agent disabled was found. The nearest open matches (#9606, #9051, #9028) cover related code-review/agent feature requests, not this disabled-button symptom.

Question reasoning

Could you attach a screenshot or short screen recording showing the disabled Send to Agent button and its tooltip? — This is a visual UI-state issue, and the tooltip should reveal which disabled-state branch the app selected.
What are the minimal steps that make the button become disabled when you expect it to be enabled? — The current report has no reproduction path, and the expected enabled state depends on comments, selected repo, terminal availability, AI state, and CLI-agent state.

This is my automated analysis and may be incorrect. A maintainer will verify the details.

Send Comment to Agent Disabled Incorrectly #9761

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions