Manifest

Assess

Tools

The company/product mentioned as having launched and later deprecated its LLM router.

Why it's here

Placed in Assess: 3 article(s) of evidence from 1 source(s), led by framework updates, with 0 in the last 30 days. Confidence 37%.

9Hacker News·8/31/2026framework_update
Google Removes MV2 Extensions from Chrome Web Store
Google has removed Manifest V2 extensions from the Chrome Web Store, including uBlock Origin. The move is part of the broader transition to Manifest V3, which changes extension capabilities and has drawn criticism from users and developers concerned about reduced ad-blocking functionality.
7Hacker News·8/8/2026framework_update
Microsoft Edge will phase out older ad blockers
Microsoft Edge is ending support for Manifest V2 extensions, which will disable older ad blockers such as uBlock Origin. Microsoft says the transition to Manifest V3 will roll out gradually to consumer users through 2026, with enterprise deprecation following in early 2027.
4Hacker News·7/31/2026product_launch
Manifest deprecates its LLM router
Manifest says it has deprecated and shut down its LLM router after four months of use, arguing that routing adds complexity and unpredictability while savings are limited. The company says a single, battle-tested model is often more effective, with caching and consistent model choice offering better results for many workflows.

Your vote is a weighted signal that nudges the radar — never a direct override.

TrialAssessConfidence25%

Business▼ Cooling
For BD, Manifest is no longer something to sell as an emerging trend; it should be positioned as a conditional choice that depends heavily on the Chrome extension context. In customer conversations, the focus should be on operational impact and migration readiness rather than promises of rapid expansion.
Developers▼ Cooling
Manifest still matters because Chrome is tightening the extension ecosystem, but with MV2 removed from the Chrome Web Store, developers should treat this as a signal to finish or adjust migration to Manifest sooner. Work will shift more toward compatibility checks and reducing reliance on legacy extension behavior.
Product▼ Cooling
PMs should treat Manifest as something that needs closer evaluation of scope and rollout risk, rather than a default direction. Product plans need to account for user impact from Chrome extension changes, especially if there is still dependence on MV2.
Testers / QA▼ Cooling
For Manifest, testing will be less exploratory and more about validating specific compatibility paths, especially where Chrome extension changes matter. QA should prioritize regression around legacy scenarios and brittle points now that MV2 is no longer distributed through the Web Store.

as of 9/8/2026

Educated guesses from the trend — you decide.