Tab Sorter

It sends one Choice question per open tab against the user's editable group criteria in a single parallel call, so the whole window resolves at once with structured answers and no parsing. Tabs that match nothing land in a fixed fallback bucket, and the pre-grouping tab order is restored when you ungroup.

Yes. The optional LLM engine accepts any OpenAI-compatible /v1/chat/completions endpoint, has the model invent its own group names in the language of the tabs, and parses strict JSON with a lenient fallback into an explicit Ungrouped bucket. The README presents it as exploration, with the Jev rules engine as the daily default.

In the options page you paste a typesafe.ai key and edit the group rules as label | description per line, where the last line is the fixed fallback bucket for tabs that match nothing. Both engines have a Test connection button that runs a real 3-tab classification before you commit to them.

The recorded rules run grouped a whole window in 456 ms end to end, nominally about a second, with one Choice question per tab asked in parallel and zero completion tokens, since Jev prices output at $0 and you only pay input. The LLM engine takes 10 to 30 seconds depending on the model and burns 500-plus output tokens per run under standard chat pricing.

It sees #index [tab title] host per tab and returns strict JSON as a groups array of label, description and member indexes, with labels in the language of your tabs. The parser strips code fences and any index the model skips lands in an explicit Ungrouped group, so nothing is silently dropped, and the last LLM-generated groups are auto-saved so one click adopts them as your permanent rules. The log viewer keeps the last 200 runs with engine, duration, token usage and groups.

Clone the repo and load the folder unpacked at chrome://extensions with Developer mode on, or grab tab-sorter-v1.1.0.zip from Releases; the built manifest, service worker and options page are in the repo root. Right-click the toolbar icon to pick either engine or ungroup, and note that groups you built by hand are never touched. Tab titles and domains go only to the endpoint you configured and only when you click, keys live in chrome.storage.local, and it is MIT licensed.

Five files drive it: manifest.json for the MV3 tabs, tabGroups, storage and contextMenus permissions, grouper.js as the shared core for both engines plus logging and the grouping pipeline, background.js as the service worker handling the toolbar click and right-click menu, options.html and options.js for settings, connection tests and the log viewer, and icons. Each of the last 200 runs logs engine, duration, prompt/completion/total token usage and the resulting groups, and every API failure records the HTTP status and the response body.