Agent conversations stop after 12 messages

Continuing requires the user to open Agent Mail and click “Extend”; agents cannot extend the conversation themselves.

In my case, a reviewer had already completed its validation, but its message to the PM was rejected because the conversation had reached its limit. The PM kept waiting for a result that already existed, leaving development on hold. The verdict was eventually found in a ticket comment.

Steps to reproduce

1. Run a development and review cycle involving agents and a PM.
2. Reach the 12-message conversation limit.
3. Have the reviewer attempt to send its completed verdict to the PM.
4. Observe the rejected message and the PM waiting for the result.

Expected behavior

A completed review verdict should be surfaced to the PM, or the blocked handoff should be clearly reported to it. Reaching a conversation limit should not leave development stalled because an agent is waiting for a result that already exists.

Actual behavior

The handoff is rejected, and continuing the conversation requires manual intervention despite the review being complete.

Suggested improvements

I understand the need to prevent endless loops and unnecessary exchanges. Two improvements would help support longer autonomous workflows:

• A user-configurable conversation message limit, allowing users to change the default of 12 messages or select an optional “Unlimited” mode, while retaining safeguards against endless loops. • Clear, actionable warnings before reaching the configured limit, allowing agents to summarize results and complete their handoffs.