Product model

TabBoy is for developers, researchers, founders, students, and anyone else whose Chrome sessions get out of hand. It sorts them out locally, without sending tab data to a hosted product.

Promise

Turn a chaotic browser session into a clear set of local suggestions, then let the user decide what to apply.

The V1 product line is deliberately strict: no required account, backend, AI, telemetry, sync, or hosted FlowCrate service.

How it works

1. Scan the current Chrome session locally.
2. Evaluate validated rules against the local snapshot.
3. Show reviewable suggestions.
4. Apply only the actions the user approves.
5. Persist successful changes after browser actions complete.

Product concepts

• Scan: A local snapshot of Chrome windows, tabs, and tab groups.
• Suggestion: A reviewable action such as group, move, close duplicates, or save for later.
• Saved group: A focused tab set created before closing tabs from a save-for-later flow.
• Collection: A full-browser snapshot for later restore or backup.
• Backup import: A validated JSON import with a review step before storage writes.

Roadmap horizon

• V1: Local Chrome release with no account, backend, AI, telemetry, or sync.
• Later: Better rule authoring, after the V1 safety model is proven.
• Portability: Firefox, Edge, Chromium validation, and community rule presets.

V1 success criteria

• Scan and explain overloaded Chrome sessions locally.
• Suggest safe groups, duplicate cleanup, and save-for-later actions.
• Confirm destructive actions before closing or deleting browser state.
• Save, restore, export, and import local data.
• Provide dry-run and preview affordances for browser-changing actions.
• Pass the manual Chrome checklist in docs/manual-test-plan.md.

For project direction, read ROADMAP.md and CHANGELOG.md.