A travel brief often mixes the trip itself with meeting context, preferences, and unresolved decisions. A short summary can help the person review it before requesting proposed form changes.

That is a useful place for Chrome’s Summarizer API: a bounded reading aid beside an existing text field.

In Trip Workbench , the public demo I built and maintain, the original brief already feeds a separate Gemini feature that proposes trip fields for review. The local summary has a different purpose. It helps the person read the brief; it does not update the trip, replace the source text, or decide which details the cloud model receives.

This walkthrough builds on commit 4b3f370 . The demo has the basic API call.…