Current release status
FluentOverlay's public docs still describe a desktop-first product surface today: live menu reading, bundled and community packs, Pro knowledge tabs, saved views, custom shortcuts, Pack Editor workflows, and export paths are the real product surface people can use now.
Shipped milestones
- v1.0 - Overlay foundation, live menu reading, fuzzy search, bundled shortcut packs, and the local-first desktop workflow core.
- v1.1 - Pack Editor, PDF and Markdown export, favourites, click-to-run depth, theme and trigger control, and broader knowledge-tab growth in Pro.
Current work
- v1.2 remains focused on stability and extension-surface work: multi-monitor polish, warm-path performance, saved-view refinement, tab-management polish, six UI locales, and cleanup across app and website surfaces.
- MCP structure authoring is already the shipped integration layer today. Broader query, execute, and context surfaces remain later steps.
Next version planned
This docs update records a planned expansion in how FluentOverlay may understand browser work. It does not change the currently documented desktop functionality in the setup, packs, or marketplace guides.
- The first planned layer is website and web-app awareness, so FluentOverlay can recognize the browser surface already in focus before it tries to attach richer help.
- The next layer adds focused-page and workspace awareness only where the signal is trustworthy enough to be genuinely useful for the exact page, document set, or working context.
- AI workflow builder, pack generation, selective cloud-connected help, and broader MCP query or execute surfaces still depend on this browser-awareness layer proving itself first.
Future / exploring
- AI natural-language search stays in the future bucket until browser-awareness and pack-grounded relevance are dependable enough to make those "how do I do X?" queries genuinely useful.
- Deeper focused-page and workspace awareness only expands after the broader browser layer proves dependable in real use.
- Passive learning, practice-style coaching, team distribution, mobile or voice experiments, and deeper automation ideas remain exploratory until they strengthen the core overlay instead of distracting from it.
How to read future-facing notes here
- Launch, install, and shipped-behavior guides should continue to describe what people can use today.
- Future-facing notes belong in the changelog or roadmap sections, where planned work can stay explicit without rewriting the core docs as if it already exists.
- If this direction becomes product-real later, the task-first setup and usage guides can expand from there.
Back to getting started
