Skip to content

Prevent Pi from rejecting accepted prompts - #4015

Closed
evaera wants to merge 1 commit into
getpaseo:mainfrom
evaera:feature/pi-message-queueing
Closed

evaera wants to merge 1 commit into
getpaseo:mainfrom
evaera:feature/pi-message-queueing

Conversation

@evaera

@evaera evaera commented Aug 29, 2026

Copy link
Copy Markdown

Paseo already decides whether input should interrupt, steer, or wait in the Queue track. That behavior is unchanged.

Once Paseo sends a prompt, Pi requires an explicit streaming behavior if it still considers the session busy. Without one, an accepted prompt can fail with “Agent is already processing.”

This sends Paseo’s steering path as steer and ordinary accepted prompts as followUp, while leaving client-side queueing and interruption behavior intact.

@evaera
evaera force-pushed the feature/pi-message-queueing branch from 218c6ee to 1f3fb52 Compare August 29, 2026 00:32
@boudra

boudra commented Sep 8, 2026

Copy link
Copy Markdown
Collaborator

Closing for now: this needs a before/after reproduction against real Pi showing an accepted prompt rejected while busy and then handled correctly, with the Pi version recorded. Please reopen with that evidence.

@boudra boudra closed this Sep 8, 2026
@boudra

boudra commented Sep 9, 2026

Copy link
Copy Markdown
Collaborator

Please disregard the earlier invitation to reopen with evidence. This PR remains closed unless I explicitly follow up. You don't need to resubmit this PR or provide further QA evidence.

Please read the updated PR policy. For now, I'm automatically closing feature PRs so I can focus more time on bug fixes and core improvements. Focused bug-fix PRs with a clear reproduction and QA are still welcome. The previous guide already asked contributors to submit only if they were comfortable with closure, and explained that unsolicited PRs could be closed without a detailed review.

For feature ideas, please start in GitHub Discussions and share your workflow: what you're trying to do, how you do it today, and where Paseo gets in the way. If there's already a discussion about it, join in and share your use case. I'll periodically review discussions for highly requested workflows and use that feedback to shape the roadmap.

I'll periodically look through closed PRs and choose which contributions to take forward, whether solicited or unsolicited. I may reopen a PR, including one closed by mistake, or use it as a reference for my own implementation, with attribution either way.

There are hundreds of PRs alongside ongoing development. I can't commit to reviewing every submission, providing individual feedback or giving timelines.

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.

2 participants