Can we rebuild Osso?
Build a Chrome extension like Osso — a Osso alternative you own.
If you want to cut through web fluff, you can build your own Osso as a custom Chrome extension. Instead of relying on a niche AI provider or rigid settings, building a DIY alternative lets you hook directly into your preferred LLM to strike out filler sentences and highlight key details in real time.
The listing record
| Name | Osso |
| Store rating | 5 / 5 · 1 ratings |
| Users | 5 |
| Store listing | Chrome Web Store ↗ |
| Analyzed | 10 November 2026 |
What Osso does
Most of what you read online is filler. Osso strikes it out as you read and leaves what you came for. • The life story fades; the recipe stays. • "We value your trust" fades; "prices go up 20% on Monday" stays. • Forty paragraphs of terms fade; "renews automatically, no refunds" stays. Nothing is hidden or rewritten. The filler stays on the page, greyed and struck through. Hold Shift and it all comes back. You can also tell Osso what to always keep (prices, deadlines, allergens) or what to highlight (red flags, candidate names). How it works: Osso asks Jev, an AI model by TypeSafe, one question about each sentence: is this what the reader came for? You need your own TypeSafe API key (typesafe.ai), which is paid: about $0.001 a page. Osso itself is free and open source.
What the store says
★ 5 from 1 ratings · 5 users
Pulled live from the Chrome Web Store listing at analysis time.
Can PlugThis rebuild Osso?
“A content script and an LLM prompt turn messy pages into signal over noise.”
The extension extracts visible page text, breaks it into segments, and sends it to an LLM to classify what is essential versus fluff. A content script simply styles non-essential text with strike-through and grey styling, while listening for a Shift keypress to toggle visibility. You can easily build this using your own OpenAI, Anthropic, or custom API key.
What you'd plug into
Analyzes page sentences and flags fluff versus essential content
Why build your own Osso alternative
- Use any LLM provider like OpenAI, Gemini, or Claude instead of being locked to TypeSafe
- Customize exact prompt instructions and categories of text to keep or highlight
- Ensure total privacy by never sending page content to unvetted third-party services
- Add custom hotkeys and styling rules to match your preferred reading setup
What it costs vs what you'd save
The original: The extension itself is free and open source, but requires a paid third-party API key costing around $0.001 per page.
Your version: While the original tool is free, building your own lets you swap the backend to cheaper, faster, or locally hosted models without extra markups.
The starter prompt
Build a Chrome extension that removes fluff from articles by greying out and striking through filler sentences. When triggered on a webpage, a content script should segment paragraph text, send it to an LLM API to evaluate whether each sentence is essential signal or unnecessary filler, and apply a strikethrough class to filler nodes. Include a global hotkey (like holding Shift) to temporarily reveal the unedited text, and an options popup where I can set my API key and custom text rules.Build it with PlugThis →
Features you could add that Osso doesn't have
Because you own the code, these are a follow-up prompt away — tap one to add it to the prompt above.
- Custom Category Highlighting — Define custom tags like 'pricing', 'allergens', or 'cancellation policies' to highlight them in distinct colors.
- Domain Allowlist — Automatically run the filtering only on designated long-form recipe, terms-of-service, or blog domains.
Questions about rebuilding Osso
How does sentence striking work technically?
A content script parses the text blocks on the page, splits them into logical sentences, sends them in a single batch to an LLM, and wraps rejected sentences in a custom span styled with strikethrough and lower opacity.
Do I have to use TypeSafe's Jev model?
No. When building your own version, you can wire it to OpenAI's gpt-4o-mini, Anthropic's Claude 3.5 Haiku, or any other fast, cost-effective language model.
Will this break interactive web pages?
Targeting inner text nodes inside typical article wrappers rather than destructive DOM replacing ensures buttons, forms, and scripts remain intact.
How to build it yourself
- 1Open PlugThis and start a new build
Head to PlugThis and start a new Chrome extension. You're describing a Osso alternative you'll own outright — no store subscription.
- 2Paste the starter prompt
Paste the starter prompt above. PlugThis expands it into a full Manifest V3 extension — popup, content scripts, and service worker included.
- 3Connect your own keys
Wire in OpenAI or Anthropic API using your own account — the build uses your credentials, so there's no per-seat fee.
- 4Review, tweak, and load it
Review the generated code, ask for tweaks in plain English, then download and load the unpacked extension in Chrome to try it.
- 5Publish it (optional)
When you're happy, publish your Osso alternative to the Chrome Web Store — or just keep it as a private tool for yourself.
Build your own Osso alternative
Describe it in plain English. PlugThis generates the full Manifest V3 Chrome extension in about two minutes.
Build it with PlugThis →More teardowns
We run the same teardown on any Chrome extension — what it does, whether a self-built alternative holds up, and the prompt to make one. Tear down another extension, or see the extensions we've actually rebuilt and filmed — real build times, real prompts, real recordings.
Sources & verification
- All facts pulled live from the Chrome Web Store listing ↗.
- The verdict is drafted by the PlugThis teardown engine — an opinion about buildability, not affiliation with Osso.
- Written by PlugThis, which builds Chrome extensions from plain-English prompts.
Published and last updated 10 November 2026. Figures reflect the Chrome Web Store listing on that date and may have changed since.