Freestyle: A Desktop Voice Dictation Tool That Turns Reminders into Actions
Project brief: Open source voice dictation platform for devs. Build voice workflows.
At a glance
- What is it?
- Freestyle is an open source desktop app that combines voice dictation with scheduled reminders and connected app actions. It targets developers who want to automate follow-ups without writing code, but its approval-based workflow and MCP integration define its boundaries.
- Who is it for?
- Adopt Freestyle if you are a developer who wants a local, approval-gated voice assistant that can check Gmail, GitHub, or Slack on a schedule and act only when you confirm. Skip it if you need mobile support, a fully autonomous agent, or if you are uncomfortable with the 1,200-tool MCP surface area.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 6 days ago.
- What is it written in?
- Mainly TypeScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on September 15, 2026, and from our analysis. They are not legal advice.
DEEP OPEN-SOURCE ANALYSIS
What Freestyle Actually Solves
Freestyle positions itself as an intelligent reminders app, not just a dictation tool. The problem it targets is the follow-up burden: an invoice overdue by three weeks, a pull request that no one has reviewed, a flight credit expiring Friday. Instead of you polling each app, Freestyle runs scheduled tasks that check those sources and notify you only when something crosses a line. It is built for developers who live in Gmail, Slack, GitHub, and Notion and want a voice-driven layer on top. The README sells it as a desktop companion that taps you on the shoulder and offers to do the next step, but only after you press Allow. The core value is reducing the number of feeds you scroll, not adding another one.
How It Works: Scheduled Tasks, Brain, and Approval Gates
The mechanism is visible in the feature list. You create scheduled tasks in natural language, like 'Every morning, look at my repo and tell me about open issues.' Each task becomes a standing job that runs on a timer you set. Freestyle connects to external apps through a set of built-in integrations: Gmail, Google Calendar, Slack, GitHub, Notion, Google Drive and Sheets. Beyond that, it supports around 1,200 tools through MCP, which is the Model Context Protocol. The README does not explain how MCP servers are configured, but the implication is that you can plug in any MCP-compatible tool. The 'Brain' is a plain-text memory store that persists what you tell it, so future conversations have context. Every write action, whether an email, a Slack post, a booking, or a purchase, stops at an approval step that shows exactly what would happen and where. You press Allow or you do not. That is a deliberate design choice: read access is automatic, write access is gated.
Getting It Running: Downloads and Platforms
The README provides download links for macOS Apple Silicon and Intel as .dmg files, Windows as an .exe, and Linux as an .AppImage or .deb. There is no command-line installation, no npm package, and no source build instructions in the README. You download a binary and run it. The project is written in TypeScript, but the README does not tell you how to build from source or what the system requirements are beyond the platform. Mobile support for iOS and Android is listed as 'coming soon,' so the current scope is desktop only. For a developer, the lack of a source setup guide is a gap, though the CONTRIBUTING.md file is referenced for local development. If you want to test the latest features, you need to track the release page, since the README does not mention auto-update behavior.
The Dictation and Remix Tools
Freestyle retains the writing tools that likely gave it its name. You hold a hotkey, speak, and release to paste polished text at your cursor. Alternatively, you can highlight a paragraph and describe the change you want, and Freestyle will apply it. The README says this works in Google Docs, Slack, VS Code, Gmail, and anywhere else you type. That 'anywhere else' is a strong claim, and the documentation does not specify how it achieves that. Likely it relies on system-level text insertion or accessibility APIs, but that is not confirmed. The Remix feature, where you describe a change to highlighted text, is a practical use case for drafting and editing without a keyboard. It is a differentiator from pure dictation tools, but the README gives no examples of the polish applied or how the hotkey is configured.
Limitations and Failure Modes
The most obvious limitation is that Freestyle is not a fully autonomous agent. Every write action requires manual approval, which is a safety feature but also a friction point. If you want a hands-free assistant that books meetings or sends emails without intervention, this is the wrong tool. Another limitation is the reliance on MCP for long-tail integrations. The README mentions 1,200 tools, but it does not explain how to discover, install, or configure MCP servers. A developer will need to find the MCP server for each tool, which could be a separate project with its own versioning and security posture. The 'Brain' is plain text, which is good for transparency, but the README does not say how it is stored or whether it is encrypted. For sensitive data, that is a concern. Mobile is absent, so if your workflow depends on phone notifications, you will not get them. The approval step shows exactly what would happen, but the README does not detail how it handles partial failures, like when a scheduled task errors or an MCP connection drops.
Alternatives and the MCP Difference
The closest alternative is a general-purpose voice assistant like Apple's Siri or Google Assistant, but those are not open source and do not integrate with MCP. A more direct comparison is with dedicated dictation tools like Wispr Flow or superwhisper, which focus on text input and cursor-level editing. Those tools do not have scheduled tasks or app integrations. Freestyle's differentiator is the combination of dictation with a reminder engine that can read from your connected apps and propose actions. Another alternative is building your own automation with cron and shell scripts that call APIs, which gives you full control but no voice interface and no approval UI. Freestyle sits in between: it offers a voice front end and a visual approval flow, but it hides the underlying automation logic. For developers who want to inspect every step, a hand-rolled solution might be more transparent, though it would lack the polish of Freestyle's desktop experience.
Maintenance and License Considerations
The project is MIT licensed, which means you can use, modify, and distribute it freely, even in commercial products. The repository shows recent activity with releases 0.8.9, 0.8.8, and 0.8.7 in August 2026, indicating active maintenance. The README points to a Discord server for contributor communication, which is a sign of community support. However, the README does not mention upgrade procedures or data migration between versions. Since the 'Brain' is plain text, in theory you can back it up manually, but there is no documentation on that. The approval-based write model is a strong safety feature, but it also means that the app must be running for tasks to execute. If you close the app, your scheduled reminders will not fire. That is a practical limitation to verify before relying on it for critical follow-ups. The absence of a source build guide means that if a binary is not available for your architecture, you are stuck unless you dig into CONTRIBUTING.md.
Editorial conclusion
Adopt Freestyle if you are a developer who wants a local, approval-gated voice assistant that can check Gmail, GitHub, or Slack on a schedule and act only when you confirm. Skip it if you need mobile support, a fully autonomous agent, or if you are uncomfortable with the 1,200-tool MCP surface area. Before relying on it, verify the exact MCP server configuration for your tools, test the approval flow with a non-critical action, and confirm the binary works on your OS version, since the README offers no build-from-source instructions and the Windows and Linux builds may lag behind macOS releases.
Community notes