Development preview: this article describes interactions in the October 23 development version. Availability in a downloaded build depends on the version you have installed. This development version does not open conversations saved in older formats; their files remain on disk.
Imagine a fictional catalog whose cache keeps showing an old price after a refresh fails. You ask Yenpo to trace how a value enters and leaves the cache. While the answer is being prepared, another question occurs to you. The next action depends on whether that question belongs after the answer or changes what the current investigation should cover.
Queue the next question
Choose “Queue” to save “Which tests cover a failed refresh?” while the current task continues. “Queue query” accepts it for a later round. You can keep reading instead of remembering the question until the answer arrives.
After a successful answer, pending questions can start automatically. Consecutive questions with compatible settings may share a round while remaining separate messages; different model configurations require separate rounds. Queue is the default sending mode and can be changed in settings.
Steer the current task
Suppose you notice that the stale price appears only after a network failure. Choose “Steer” and send “Focus on the failed refresh path; check whether the old entry remains available.” This supplements the task already in progress.
Steering waits for an ongoing model request or tool operation to finish before joining the next processing step. It does not immediately interrupt either. If the task has already finished, the input becomes queued. Steering retains the current task’s configuration and permissions; switching to a different fixed Git comparison needs a queued question.
Manage and resume pending questions
The pending list lets you edit question text, change order, remove a question, or switch its sending mode before processing begins. “Steer all” brings queued questions into the active task when they are suitable for it.
Accepted questions are saved. Stopping, failure, or reopening the app pauses pending work; review the list and choose “Continue sending” to resume. A changed provider configuration can also require attention.
An automatically started queue round does not inherit earlier permission to edit files. When you explicitly continue, you can authorize editing for that round. See privacy and control for the permission boundary.
Choose a follow-up suggestion
After an answer, an empty composer may show a suggested next question, such as “What should the caller receive when refreshing the cache fails?” It is optional: ignore it and write your own question if another uncertainty matters more.
The suggestion uses an additional request to the configured model and may be unavailable. When visible, Tab or Enter accepts and sends it; these keys do not merely copy it into a draft. Suggestions do not overwrite your text or send themselves.
Return to the source for the next step
Open the answer’s references and inspect the failure branch, the cache entry, and its caller. Separate what the source proves from what still needs a test. Your next question should name that remaining uncertainty: “Does this test assert the old price, or only that no exception occurs?”
See asking better questions for choosing context, and the reading workflow update for the surrounding reading tools.