An extension you relied on was abandoned.
Useful signal: the tool name, what you used it for, what broke, and what replacement attempts failed.
// workflow request lab
Tell us what browser workflow broke.
EXFILTR Lab is the intake layer for broken, abandoned, bloated, or missing browser workflows. We investigate requests, group similar signals, and may rebuild high-demand utilities when the scope is narrow enough to do well.
// Request intake
A recovery pipeline for browser utilities.
Tell us what stopped working, got too heavy, disappeared, or never existed in the simple form you needed. This is not custom development on demand. It is a public signal intake layer for deciding what EXFILTR should investigate next.
A browser tool became too heavy.
Useful signal: the original simple workflow, which features made it worse, and what permissions or account requirements now feel excessive.
A workflow broke after MV3 or platform changes.
Useful signal: browser, extension, failure mode, and whether other users are asking for the same replacement.
A simple utility disappeared.
Useful signal: the one job it did, how often you used it, and why modern replacements do too much or miss the point.
No modern replacement exists.
Useful signal: links to Reddit threads, Chrome Web Store reviews, public issue threads, or posts where people describe the same gap.
The best requests are small and concrete.
EXFILTR favors browser-native utilities with clear workflows, minimal permissions, local-first behavior where practical, and low maintenance burden.
// How requests move
What happens after you submit.
- The request is reviewed for browser-native fit.
- Similar requests and legacy-tool signals are grouped.
- The workflow is scored for demand, pain, permission risk, build simplicity, distribution, and maintenance burden.
- High-signal requests can enter the opportunity queue.
- Selected ideas may become public EXFILTR utilities after review, QA, and launch approval.
// Submit safely
Describe the workflow, not private data.
Do not send passwords, private account data, customer records, API keys, recovery phrases, personal documents, or anything sensitive.
Send only the workflow problem, links to public evidence if available, and why current alternatives fail.
// Form status
Request form coming later.
A structured request form may be added after the intake fields, privacy copy, spam protection, and rate limits are ready. For now, email keeps the workflow simple and avoids collecting unnecessary data.
Priority or private utility builds may be considered later, but there is no pricing, guaranteed delivery, or custom development offer on this page.
// Status cards
Current public status.
No EXFILTR product is marked live on this page. Install buttons appear only after public availability is verified.
TabRest
Browser working-memory recovery and backup/export work. The internal prototype exists for local review, restore-flow QA, and session-loss anxiety reduction.
Refine
Browser-native readability workflow infrastructure. V1 scope is activeTab-first and user-triggered, but no public extension is launched.
Future utilities
PasteClean, ManualSuspend, LinkSweep, and other concepts remain validation or watchlist candidates until demand, permission scope, and maintenance burden are clear.
// Public roadmap language
Status labels use plain meanings.
A product is not treated as available until the release state says it is available.
Evidence gathering.
A workflow, category, or complaint cluster is being studied. No product commitment exists.
Interesting signal.
There is enough signal to track, but not enough to scope or build.
V1 defined.
The problem, permission posture, boundaries, and first workflow are clear enough to review.
Internal only.
A reviewable internal version exists. It is not a public launch or installable claim.
QA and trust gate.
Permissions, privacy, performance, copy, and failure modes are being checked.
Release-sensitive gate.
Human approval is required before launch, Chrome Web Store submission, or public publishing.
Externally verified.
The product is public only after availability, policy copy, privacy posture, and links are verified.
Stopped intentionally.
The concept failed a trust, maintenance, retention, monetization, or platform-risk gate.
// Research
Browser workflow notes
EXFILTR studies abandoned extensions, migration waves, MV2/MV3 casualties, redesign backlash, pricing backlash, and trust collapse. Public summaries stay factual and source-aware.
// Restraint
Rejected ideas are visible.
Some ideas have demand but fail EXFILTR's trust, maintenance, permissions, monetization, or browser-native filters.
// Trust
Permissions are documented before launch.
The permission registry explains what products need, what they do not touch, and how local-first behavior works.
// Product rules
Scope stays narrow.
Extensions should solve one browser workflow clearly before they grow into anything larger.