Add open source tool: Plainsay
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 67/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- macos, typescript
- Domain
- content
Research direction
Read the existing tool entries and the contribution format in the repository, then find the entry point or data file where tools are listed. Add Plainsay with its name, website, category, MIT client license, and macOS requirements; check that the listing matches the surrounding entries and that its links work.
Written by the indexing model from the issue text.
Description
Name: Plainsay
Repository: https://github.com/conrader/plainsay
Website: https://plainsay.app/
Category: Dictation / speech-to-text
Proprietary alternatives: Wispr Flow, Superwhisper
License: MIT for the Mac client
Release: https://github.com/conrader/plainsay/releases/tag/v0.2.38
Requirements: macOS 14+ and Apple silicon; download a speech model for Local mode.
Description:
Plainsay is a native Mac menu-bar app for live dictation into text fields. Hold a key, speak, and release to paste the transcript, with a clipboard fallback. It does not import existing audio files.
Features:
- Free Local transcription using Whisper or Parakeet, with no account.
- Offline recognition after model download.
- Optional Polishing and voice editing with a configured provider.
With Local transcription and Polishing off or using a local endpoint, dictation audio and transcript text stay on the Mac. Hosted Polishing sends text to the chosen provider. Optional paid Plainsay Cloud transcription uploads audio; the hosted service is separate from the MIT client.
I'm Konrad, the developer. This suggestion was drafted with AI assistance.
- Dominant language
- TypeScript
- Stars
- 1.3k
- Forks
- 195
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from junaid33/opensource.builders
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
junaid33/opensource.builders#597 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
junaid33/opensource.builders#596 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
junaid33/opensource.builders#594 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
junaid33/opensource.builders#593 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
junaid33/opensource.builders#591 ·
All issues in junaid33/opensource.builders
Similar issues
-
Chip source filter and denial markers miss Storage rows when a Storage activity source is pickedOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
omdsh-dev/DSH-better-sidebar#1141 ·
Maintainers usually reply within 2 days
-
desktop linux photos
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Cleanup SetupPossibly taken @AlexanderKaran claimed this today. Opendocumentation enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
e18e/framework-tracker#769 ·
Maintainers usually reply within 1 day
-
bug v2
Difficulty 1/5 Under an hour Newbie friendliness 88/100
modelcontextprotocol/servers#5483 ·
Maintainers usually reply within 1 day