Skip to content

Chrome Triage Directions

How to run Chrome tab triage — pipeline overview, agent role (validate Sonnet's groups), available actions

When to use

user wants to triage, organize, or close Chrome tabs

Slash command: /wb-chrome-triage

Linked workflow: browser/chrome-triage

  • context/chrome_activity
  • context/chrome_cluster
  • context/chrome_content
  • context/chrome_infer
  • context/triage_item_detail

Directions

Start via mcp__work-buddy__wb_run("chrome-triage").

The system runs a 4-tier pipeline automatically: 1. Collect -- currently-open tabs + engagement scores 2. Extract & Cluster -- page content -> embeddings -> Louvain clusters 3. Haiku Summarize -- structured per-tab summaries (~$0.001/tab, cached) 4. Sonnet Intent Group -- cross-tab intent inference with context

Your job: receive Sonnet's structured intent groups, validate them (resolve flagged ambiguities using your richer context), present to the user, collect decisions, and execute.

For each intent group, the user chooses: - close -- tabs served their purpose - group -- organize related tabs together - create task -- turn into a new task (then close) - record -- attach to an existing task (then close) - leave -- still actively useful

Present groups by suggested action. Be efficient -- don't explain the pipeline.