Public Roadmap
What's coming in Whisperit
Backlog
2Under consideration
French UI localization
Make the Whisperit interface available in French for end users.
Export Word: When exporting, some texts appears 2x
As a user, when I export my Whisperit document to a Word document, the text in numbered list items is duplicated. Additionally, the numbering format is broken.
In Progress
2Actively being built
Unresponsive Chat Thread & Performance Slowdown Inquiry
Customer Jérôme reports that a specific chat thread (URL: https://whisperit.ai/protected/assistant/0261e881-3974-4e96-a5a7-cdcc0020798e) has been unresponsive for several days. The customer initiated a new chat due to the length and unresponsiveness of the original thread. Jérôme also notes that the system experiences significant slowdowns with dense chats and requests information on upcoming technical improvements in this regard. The customer asks if Whisperit can refresh the page on their side.
Google Drive Integration
To connect Whisperit's legal research tool directly to a customer's Google Drive. This will allow users to conduct deep, contextualized research across their own secure data by selecting specific folders or files within their Drive to serve as a private knowledge base for the AI's legal research and analysis features. (Customer based request)
Done
6Recently shipped
Assistant: Mention "@" takes 20 seconds to retrieve data
As a user, I cannot use the “mention” as it takes more than 20 seconds to retrieve the data
Split a large PDF into small pdfs
As a user, I want to split a PDF into multiple documents so that I can better work with those files. It will allow me to better contextualize each file and also work with them using AI. Currently, I either use Adobe or iLovePDF that allows to either split or group pdfs (yet I’m a bit concerned about the security even thought it’s in Italy). I’d like to split it between specific pages. That’d be extremely useful.
Lost Audio - Recording & Diarization Missing; Sort by Date Not Working
User ID _ fe0cbd7d-9f50-4b1a-abc7-d71f0d250efe Customer reports that a recently recorded conference, approximately two hours in duration, is not appearing in 'My Vault'. The recording's diarization is also missing. Customer has confirmed that nothing is visible in 'My Vault' after checking. Additionally, the customer states that the 'sort by creation date' functionality is not working.
assistant issues
**Assistant Ignoring Case Documents:** When using the assistant within a case to summarize or draft responses, it requests information (e.g., case description, dispute object, legal points, exchanged documents) that is already present in the attached case documents. This indicates the assistant is not effectively utilizing the provided case context.
Audio transcription fails for long recordings
User Story: As a user, I want long audio recordings to transcribe successfully, so that lengthy recordings can be processed without errors. Acceptance Criteria: Audio recordings longer than 30 minutes can be submitted for transcription. Large supported audio files do not fail with a server error during upload or processing. Transcription completes successfully for audio files that previously failed because of their size. Shorter audio recordings continue to transcribe successfully. Test: Upload a supported short audio recording and confirm transcription completes successfully. Upload a supported long audio recording over 30 minutes and start transcription. Confirm the upload is accepted and processing starts without an error. Confirm transcription completes and returns the expected transcript. Repeat with another large recording to verify the issue is resolved consistently. Technical note: The failure appears to affect the live dictation path only, not the import or meeting transcription paths. The live dictation flow sends audio inline to /api/voice/transcribe and does not switch to blob upload for larger files. Recordings over the request body limit can fail while parsing multipart form data, which leads to server errors for larger audio inputs.
Featurebase: sanitize page titles in v3 to avoid leaking names/IDs in dashboard recent views
Problem In the Featurebase dashboard, under recent page visits, page titles show raw route segments (including dynamic names/IDs) because v3 dashboard pages don't set document.title. Featurebase's SDK falls back to the URL path, which is how names/titles end up surfaced in the Featurebase admin view. Pointed out by Laura in #dev (Slack thread 2026-04-24): "Featurebase reads the page title we give to our pages, but we are actually not giving titles to pages on v3." Goal In Featurebase dashboard → recent page visits, each entry should display something like Whisperit · {sanitized title} — never a raw user name, doc name, client name, or other PII. Fix in a single file (messenger component) — do NOT add metadata.title to all 30 v3 route files. Ankan's constraint. Metadata on individual pages already looks fine; only the Featurebase-visible title needs to change. Proposed approach In dashboard/app/.../featurebase-messenger.tsx: Use usePathname() to get the current route. Sanitize it: strip UUIDs, numeric IDs, and any dynamic segments that could contain PII. Set document.title = \Whisperit · ${sanitized}`on every route change (viauseEffectonpathname`). Re-trigger Featurebase's changeLocale/identify (or equivalent) so the SDK picks up the new title on SPA navigations. Example sanitizer: const sanitized = pathname .replace(/\/[0-9a-f-]{36}/gi, '') // strip UUIDs .replace(/\/\d+/g, '') // strip numeric IDs .split('/').filter(Boolean) .map(seg => seg.charAt(0).toUpperCase() + seg.slice(1)) .join(' · ') || 'Dashboard'; document.title = `Whisperit · ${sanitized}`; Security / privacy requirements No PII in titles: no client names, document names, user names, emails, IDs. Whitelist of allowed route segments if possible; everything else becomes a generic label. Verify in Featurebase dashboard (recent page visits) after deploy that titles are clean. Acceptance criteria [X] Single-file change (messenger component only) [ ] Featurebase dashboard recent page visits show Whisperit · {sanitized-route} format [ ] No UUIDs, numeric IDs, or user-provided strings visible in any Featurebase-surfaced title [ ] Titles update correctly on client-side navigation (not just hard reloads) [ ] QA: manually inspect 5+ routes (incl. dynamic ones like /documents/[id], /clients/[id]) in Featurebase admin Context Slack thread: https://whisperit.slack.com/archives/C07BDM0LY14/p1777034773852469 Related: earlier Featurebase HMAC work (/api/featurebase/hash route) — keep existing auth flow intact.