Build Cotypist
KINDAreplaces $6/mosaves $72/yrback to the verdict
Before step 1
you will need
- macOS with Xcode and a Swift toolchain
- Accessibility and Input Monitoring permissions granted manually
- a small local model via llama.cpp or MLX, or a personal n-gram corpus built from your own text
- Apple Silicon strongly preferred for latency
Delivery order
Scaffold the smallest runnable application and document its commands.
done whenThe project starts from a documented command in a clean checkout.
Implement the primary data model and core workflow.
done whenThe main object can be created, read and changed end to end.
Add validation, safe failure states, and persistence.
done whenBad input is refused with a readable message and nothing is left corrupted.
Cover the critical path with automated tests.
done whenThe highest-risk behavior fails the suite when it breaks.
Exercise a clean install from the README and fix every missing step.
done whenA fresh clone reaches the first successful workflow using only the README.
That is the whole plan for Cotypist. What it deliberately does not cover is below · check the gaps before you call it a replacement.
- Coverage: your build will work in native text fields and fail or misbehave in Electron apps, browsers, and terminals
- Latency polish: suggestions that arrive after you already typed the words are worse than nothing
- Safety rails: skipping password fields, secure input mode, and sensitive apps takes deliberate work
- Personalization that actually improves over months of your writing rather than a one-off corpus dump
- Signed, notarized, auto-updating distribution and the permission onboarding that makes it survive OS updates
Need the files? The project pack on the verdict page hands your agent the whole brief · more productivity utilities.