Skip to content

Chrome Triage

Triage currently-open Chrome tabs through the unified source pipeline: collect tabs, attach cached Haiku summaries + tag signals, embedding-fused cluster (Louvain over embedding+tag+window-gated proximity), Sonnet-refine cluster boundaries + propose a per-cluster action (close all tabs / group in Chrome / route to tasks / etc.), and spawn a group umbrella thread + group sub-threads with the tabs as ContextItems. The user reviews and approves via the dashboard column grid + per-column action chip.

Workflow name: chrome-triage

Execution: main

Override not allowed

Steps

# ID Name Type Depends on
1 run-pipeline Run Chrome triage source pipeline code

Step instructions

run-pipeline

Auto-run. Call work_buddy.pipelines.run_source_pipeline(source='chrome_triage', engagement_window='24h', include_summaries=True). The pipeline runs collect → annotate → precluster → refine → spawn end-to-end and returns the umbrella thread id + child group thread ids + per-cluster action proposals. The umbrella becomes visible on the dashboard's Threads tab; the user reviews + drag-drops tabs between groups + picks per-group actions via the column-header action chip; approving the umbrella runs each child's chosen action through the standard FSM dispatch path (calls chrome_tab_close / chrome_tab_group / chrome_route_to_tasks / etc.).