More control while Ampere works
Queue, edit, and reorder follow-up messages, see task progress, and move through clarification, stopping, and finishing states with less guesswork.
What's new
This release gives you more control over an active Ampere session without interrupting useful work. Queued follow-ups are easier to manage, task progress is easier to read, and the composer now distinguishes clearly between work that can still be stopped and a response that is already being saved.
Plan the next step while Ampere is still working
Queued follow-ups now live in a compact, collapsible sidecar above the composer. You can edit an ordinary queued message in the existing composer, reorder eligible messages with a mouse, touch, or keyboard, and remove, retry, or clear messages when their state allows it. The visible order remains the order Ampere will use.
Queue actions acknowledge immediately, then reconcile with the saved queue. Refreshes and other open tabs recover the current order rather than leaving an optimistic change stranded. Ampere-managed and older queued messages remain visible with only the controls that are safe for them.
Follow progress without reading internal bookkeeping
During supported active turns, Ampere can show a compact task-progress control with the completed count, the current task, and an expandable status list. The transcript stays focused on the work and final answer while still giving you a useful view of what is moving.
Give required input without losing the work
When Ampere truly cannot continue without a missing fact, it can pause in a clear question card that survives refresh and resumes the same work after you answer. Supplied facts, optional questions, and details you have allowed Ampere to infer should not become blocking checkpoints.
Know whether Ampere is stopping or finishing
Stop now stays tied to the exact active response and shows Stopping response while cancellation is being confirmed. Once a completed response is being saved, Stop is replaced by a disabled Finishing response state instead of implying that the work can still be cancelled. You can keep typing and queue the next message while finishing completes.
Active session state also converges more cleanly across reloads, reconnects, and route re-entry, reducing avoidable interrupted-looking states while preserving truthful recovery when continuation is not safe.
Why it matters
You should not have to wait for a long marketing job to finish before shaping what comes next. You also should not have to guess whether Ampere needs your input, is still cancellable, or is simply saving a completed response. These changes make the next action clearer while keeping the durable session, queue order, and completed work aligned behind the interface.
You still decide the direction, answer genuinely required questions, and review the result. Ampere carries the execution and gives you clearer controls around that work.
How to use it
Start a request in Ampere, then enter another instruction while the response is active. Expand the queued-follow-up sidecar to edit, reorder, retry, or remove eligible messages. Expand task progress when it appears to see the current work, answer any required-input card in place, and keep drafting or queueing the next step if the composer shows Finishing response.
Where to find it
The queued-follow-up sidecar, task progress, clarification cards, and stopping or finishing states all appear inside Ampere sessions.