Q Web Trigger — Work with Q on any website

Q can now work from the page you’re already reading. With the new Q Web Trigger Chrome extension, you can send any web page to Q, choose the right HeyQ project, and ask Q to turn that page into useful product work — without copying text, switching tabs, or opening HeyQ first.

Install it from the Chrome Web Store: Q Web Trigger

What changed

• Trigger Q from any webpage. Open the extension popup while viewing a competitor’s release notes, an industry report, a public roadmap, or any other page you want Q to act on.
• One-click current tab capture. Q Web Trigger captures the current page URL, title, page text, and optional selected text on demand — no manual copy/paste required.
• Project picker built in. Choose which HeyQ project the page belongs to before sending the job, so Q updates the right workspace context.
• Natural-language instructions. Ask Q to do real work, like “create a DEV mission to copy this,” “update our market size to $23B,” or “add this competitor to the comparison matrix.”
• Background execution. Jobs run asynchronously via QStash, so longer tasks keep going even if you close the popup.
• Past runs with deep links. The Past runs tab keeps a record of recent jobs, including full results and direct links back to the files, missions, or pages Q created or updated.
• Per-project capability controls. Decide what the extension is allowed to do per project — create, update, delete, and deep-scrape capabilities can be controlled independently.
• Existing HeyQ login. The extension reuses your HeyQ session, so there is no extra API key setup.

Why it matters

The best product context often appears outside your product workspace: competitor launches, analyst reports, changelogs, docs, forums, roadmaps, and customer-facing pages. Before Q Web Trigger, turning that context into product truth meant copying content into HeyQ, describing what you wanted, and manually reconnecting the source.

Now the workflow starts exactly where the signal appears. When you find something useful, hand the page to Q, give it an instruction, and let it update your HeyQ project in the background. This makes HeyQ faster for competitive research, market sizing, roadmap inspiration, and day-to-day product capture.

Example uses

• Turn a competitor feature page into a structured DEV mission.
• Add a new competitor or update an existing comparison matrix from the page you’re viewing.
• Capture a market report and ask Q to update your market size or positioning pages.
• Review another company’s release notes and ask Q to identify relevant roadmap ideas.
• Save the result as a new page, file update, or board item with source context attached.

Notes

• Q Web Trigger requires an active account on heyq.com.
• The extension is available on the Chrome Web Store: https://chromewebstore.google.com/detail/q-web-trigger/efiikemlehiablacaoodidbdmnlnknoe
• The extension only captures page content when you explicitly run it from the popup.

Documentation Search — Find Help Without Leaving Your Workspace

Need a quick answer about how roadmaps, mission boards, integrations, or Q work? You can now search the HeyQ docs without ever leaving the app.

What changed

• Docs search in the project navbar. While you’re inside a project, open documentation search the same way you open project search — and look up anything in the public docs without breaking your flow.
• Docs search in the workspace sidebar. Browsing your workspace? The same search is one click away from the sidebar.
• Familiar search pattern. The experience mirrors HeyQ’s existing project search, so there’s nothing new to learn.
• Keyword-first guidance. The empty state nudges you toward short keywords like “roadmap” or “github” instead of long questions, so you get useful results faster.
• Results open in a new tab. Selecting a result never disrupts your current project or workspace state — your work stays exactly where you left it.

Why it matters

Documentation only helps if you can reach it without losing your place. Until now, looking up how a feature worked meant tabbing out, hunting through the docs site, and trying to find your way back. With docs search built into both the project navbar and the workspace sidebar, the answer is always within reach — and your workspace is still right where you left it when you’re done.

How to use

1. Open documentation search from the project navbar (while inside a project) or from the workspace sidebar.
2. Type a short keyword — try “roadmap”, “mission board”, or “github”.
3. Pick the result that matches what you’re looking for. It opens in a new tab.
4. Switch back to HeyQ whenever you’re ready — your project state hasn’t moved.

Notes

• Search works on the public HeyQ docs only. Your private project content is not part of these results.
• Keyword search works best — semantic and typo-tolerant search aren’t part of this release.

Q Moves to the Navbar — A Smarter, Quieter Companion

Q is no longer buried in a sidebar tab. It’s now a dedicated companion in your navbar — watching your project quietly and surfacing the right next step at the right time.

What changed

• Q lives in the navbar. Look next to the notifications bell for the Q icon, with a badge showing how many suggestions are waiting for you.
• Click to slide out a suggestion panel. No page navigation, no context switching — just a focused list of what to do next.
• The AI sidebar is now chat-only. Opening the sidebar starts a fresh chat. The fixed “Q tab” is gone, so your chat space is yours.
• Actions are context-aware. Clicking “Ask AI” on a Q suggestion tucks the Q panel away and opens a new chat in the sidebar. Accepting a to-do keeps the Q panel open so you can continue working through suggestions.
• A subtle pulse ring on the Q icon helps new users discover onboarding suggestions.
• No more text input in Q. Q is for acting, not chatting — the AI sidebar handles conversations.

Why it matters

The old layout had two chat tabs that looked the same but behaved completely differently. One was a proactive suggestion engine, the other a true conversational assistant. New users reasonably expected both to work the same way — and were confused when they didn’t.

By giving Q its own home in the navbar, we’re making its role clear: Q is a smart companion that watches what’s happening in your project and surfaces focused, actionable next steps. The AI sidebar is where you go to chat, think, and explore. Two tools, two clear jobs.

How to use

1. Look for the new Q icon in your navbar, next to notifications.
2. When you see a badge, click to see what Q suggests next.
3. Accept a to-do to act on a suggestion, or hit “Ask AI” to dive deeper in a chat.
4. Need to start a conversation? Just open the sidebar — it opens fresh, ready to go.

Notes

• Q remains suggestion-only by design. If you want a back-and-forth, the AI sidebar is one click away.
• Suggestions refresh as your project evolves — including when tickets move to done, whether you moved them or AI did.

Decision Log — Page Template & Area-based AI Routing

Capture the decisions that shape your product — and make them useful to every AI tool in your workflow.

What changed

• You can now create a Decision Log page from the page template picker and add structured decision entries with a required one-liner and simple metadata (Area, Status, Decided By, Decided At).
• Decisions display in a list/board view with search and filters so you can find the choice you need in seconds.
• Area-based routing: active decisions are summarized and grouped by area (Product, Technical, GTM, Business and any custom areas you add). AI tools and exports receive only the relevant decisions for a given area, keeping prompts focused and reducing noise.
• “Copy for AI” produces a deterministic, area-grouped markdown summary of active decisions so you can paste aligned context into any tool.
• “Draft with AI” pre-fills your AI chat with a draft based on decision context so you can review and edit before sending — a small toast confirms the draft is ready.
• Active decisions are the only ones included in AI summaries and exports; Proposed and Superseded items are excluded to avoid confusion.

Why it matters

Decisions are the “why” behind what you build. Making them first-class, structured objects means your AI tools and collaborators can consistently see the intent behind features — reducing scope drift, contradictions, and repeated re-explaining across AI sessions.

By grouping decision summaries by area, HeyQ keeps each AI integration focused: marketing tools see GTM decisions, developer-facing tools see Product and Technical decisions, and so on.

How to use

1. Add a Decision Log page from the template picker.
2. Create a new decision and write a short one-liner in the recommended format (e.g., “[We] [verb] [choice] [reason]”).
3. Tag the decision with an Area and set its Status (Active/Proposed/Superseded).
4. Use the toolbar to search, filter, Copy for AI, or Draft with AI.
5. Export or let integrated AI tools read the active, area-grouped summaries when they need context.

Notes

• You can manage areas (add, rename, reorder) and create custom areas to match your workflow.
• Decisions are intended to be small, durable summaries of choices; linking decisions to tickets or building approval workflows are planned for future updates.
• Minor UI reliability and accessibility fixes accompanied this release for a smoother editing and drafting experience.

This release ships the Decision Log as a foundational, AI-friendly place to record the decisions that keep your product coherent as you build fast.

Public Roadmap — Share Your Direction & Collect Feature Requests

Your product has a direction. Now you can show it.

A roadmap your users can actually see

HeyQ now includes a full product roadmap page. Internally, you curate items across five stages — Requested, Under Review, Planned, In Progress, and Shipped — with categories, ETAs, and rich descriptions. When you’re ready, flip on public visibility and share a clean, readable roadmap with anyone.

Your public roadmap lives at its own URL and can be embedded directly on your website or docs with a single line of code.

Let your product do the talking

Each roadmap item can carry a short description, an ETA, and a category badge. Visitors can click any card to read the full details. Shipped items link directly to the relevant changelog entry — so users can trace what was promised to what was actually delivered.

Collect feature requests from users

Enable the feature request form on your public roadmap and visitors can submit ideas in seconds. Requests land in your inbox as “Requested” items, ready for you to review. Q can help triage them — searching for duplicate missions, suggesting whether something fits your current scope, and creating a new mission if it’s worth pursuing.

Upvotes that actually mean something

When voting is enabled, visitors can upvote items they care about. Vote counts are visible on both the public and internal views, so you always know what your users want most — without any manual effort.

Stays in sync with your missions

Link any roadmap item to one or more missions on your board. When those missions move — to In Progress, or Done — the roadmap item updates automatically. Planned becomes In Progress. In Progress becomes Shipped. Your roadmap reflects reality, not a wishlist frozen in time.

Q knows your roadmap

The AI sidebar has full awareness of your roadmap. Ask Q to add an item, update a status, or suggest what to put on the roadmap based on your completed missions. Your product direction is now part of your product truth.

---

Public roadmap visibility can be toggled independently of your project. Feature request submission and voting can each be enabled or disabled separately.