Research review / adoption

AWS Quick Keeps Flows Running After the Browser Closes

AWS's November 20 update adds persistent flows and separately configured agent teams. The practical evaluation question is whether resumed work retains its evidence, identity and approval state.

By Sandeep Belgavi · Published 2026-11-21

AWS announced updates to Quick flows and agent collaboration on November 20, 2026. The release describes longer-running work that continues after the browser closes, with results and requests awaiting input available through Mission Control.

Persistent work and agent collaboration arrive together

AWS describes conversational flow creation and modification, deterministic steps and orchestration across specialized agents. Each agent retains separately configured instructions, knowledge and context. The announcement also says connectors respect existing permissions and Quick asks before write actions. These are stated product behaviors, not independently tested guarantees.

A resumed task still needs an evidence record

Engineering interpretation: background execution creates a reason to inspect task identity and intermediate evidence when returning to the result. An output that looks finished should still distinguish complete evidence from a missing input or pending decision.

Separately configured agents also create a useful review question: which evidence was available to each contributor? Combining their prose would not by itself answer whether one contributor lacked a necessary file.

A proposed handoff with one unavailable input

Original exercise, not executed: prepare three synthetic trace files. Have one agent summarize error counts and another extract latency ranges, then use a deterministic step to check their outputs against a declared JSON schema before combination.

Intentionally omit one file from the second agent's allowed inputs. The combined result should disclose the missing evidence instead of implying full coverage. Record the input set alongside each contribution so the omission is independently visible.

In an eventual persistence check, close and reopen the browser midway and compare task identifiers, intermediate outputs and approval state. Keep awaiting input distinct from complete. This is an evaluation design, not a tested Quick implementation or a claim about unobserved failure behavior.

Sources accessed November 21, 2026. Views are my own and do not represent any employer, past or present.

Sources and evidence

Check persistence together with contribution evidence and approval state, so resumed work does not hide missing inputs or pending decisions.