TL;DR: Ink Dev Digest v1.5.0
A flip-through summary of Ink v1.5.0, the unified Cogito feedback pipeline, and why the release matters for local-first writing.
Ink had a compact but important release week between 16 and 23 June 2026. The two main releases, v1.4.0 and v1.5.0, do not add a long list of visible buttons. Instead, they push the project in a more useful direction: Ink is becoming a more reliable local-first writing environment, not just a clean markdown editor. If you are new to the project, start with the original Ink introduction for the basic local-first idea.
The headline is v1.5.0: Cogito feedback and document analysis now share a more coherent local workflow. That sounds like internal plumbing, but it changes the feel of the product. AI feedback should be available when it helps, quiet when it does not, and resilient enough that it does not interrupt the writing session.
What Changed
| Area | v1.4.0 | v1.5.0 |
|---|---|---|
| Main focus | Developer tooling and mobile polish | Unified AI feedback and stability |
| Headline feature | Automated demo capture | Unified Cogito feedback pipeline |
| User-facing polish | Mobile textarea auto-zoom fixes | More reliable local feedback flow |
| Maintenance | Dependency updates | README update |
| Notable pull request | codex/add-demo-video-capture |
feat/cogito-and-linter |
v1.4.0: Making the Project Easier to Show
v1.4.0 introduced an automated Ink demo capture workflow. That might sound like a maintainer convenience, and it is, but it also matters for users.
Ink is a visual writing tool. A release page or README can describe the workflow, but a short demo shows whether the editor feels calm, fast, and direct. Automating that capture means the project can keep its demos closer to the real application, instead of relying on stale screenshots or hand-recorded videos.
This release window also included useful housekeeping. The mobile textarea zoom fixes addressed the kind of small irritation that can make a writing app feel untrustworthy on a phone. If tapping the editor causes the browser to zoom in at the wrong moment, the writing flow breaks. Fixing that is not glamorous, but it is exactly the kind of polish a writing environment needs. It continues the work from v1.3.1, where Ink moved from a writing companion toward a fuller writing environment.
Dependabot also updated build and test dependencies, including esbuild, form-data, and istanbul-lib-processinfo. None of those changes are the story by themselves, but they keep the project healthier and reduce the maintenance drag around future releases.
v1.5.0: Cogito and the Linter Come Together
The bigger step is v1.5.0, which unifies Cogito feedback with document analysis.
Cogito is Ink’s local AI writing companion. Its job is not to write over you. It reads the current writing context and asks questions that help you sharpen the next thought. The Document Linter, meanwhile, looks at the structure of the draft: headings, paragraphs, formatting, and other signals that affect readability. That philosophy started with the Cogito release: AI as a reflective prompt, not an automatic co-author.
Before this release, those two features were conceptually related but technically separate. v1.5.0 brings them into a more unified feedback pipeline. For the user, the benefit is simple: AI-assisted reflection and document-level analysis should feel like parts of one writing loop.
This is the direction I want Ink to move in. The app should help you notice weak spots in a draft, ask better questions, and keep control of the text in your hands. It should not become another autocomplete machine.
Why This Matters
Architectural releases can be easy to undersell. A cleaner shared pipeline does not photograph as well as a new toolbar, but it affects everything that comes next. When Cogito and the Linter share a more resilient foundation, future writing features become easier to build and easier to reason about.
It also reinforces Ink’s product philosophy: local-first AI should support the writer’s attention rather than replace it. The best version of Ink is not a tool that writes for you. It is an environment that helps you stay close to your own thinking.
Open viscioletti.com/ink, choose a local folder, and write a short markdown note. No account, no cloud workspace, and no install step. If the workflow clicks, you can follow the source, releases, and issues on GitHub.
If Ink feels useful, starring the repository helps other people find it:
The Shape of Ink Now
After these releases, Ink has a clearer identity:
- A local-first markdown editor that keeps your files under your control.
- A single-file web app that remains easy to download, inspect, and run.
- A writing companion that asks questions instead of generating generic prose.
- A document analysis layer that helps tighten structure and readability.
- A project workflow that is easier to test, demo, and maintain.
That combination is starting to feel like more than a small editor. It is becoming a writing workspace with a point of view.
The fastest way to understand the direction is to try it with a real draft: open Ink now, point it at a local folder, and see whether the writing loop feels lighter than your current setup.