Skip to content

fix: Follow-up logic persists after /stop trigger. #6656

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Soulter merged 1 commit into from
Mar 20, 2026
Merged

fix: Follow-up logic persists after /stop trigger. #6656

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions astrbot/core/pipeline/process_stage/follow_up.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -172,6 +172,9 @@ def try_capture_follow_up(event: AstrMessageEvent) -> FollowUpCapture | None:
if not active_sender_id or active_sender_id != sender_id:
return None

if runner_event.get_extra("agent_stop_requested"):
Comment thread
Soulter marked this conversation as resolved.
return None

ticket = runner.follow_up(message_text=_event_follow_up_text(event))
if not ticket:
return None
Expand Down
Loading