TL;DR release note

Ink is becoming a writing environment, not just an editor.

v1.5.0 makes Cogito feedback and document analysis feel like one local-first writing loop.

Read full article Open Ink
The headline

The release connects AI reflection with document-level structure checks.

That sounds like plumbing. In practice, it makes feedback feel calmer, more coherent, and less interruptive.

What changed

Two releases, one direction.

v1.4.0Easier to show

Automated demo capture, mobile textarea zoom fixes, and dependency maintenance.

v1.5.0Easier to trust

A unified Cogito feedback pipeline connects AI reflection and document analysis.

The feedback loop

Cogito now has a cleaner path through the draft.

1

One feedback pipeline for reflective AI prompts and document analysis.

1
Read the draftInk keeps the current writing context local.
2
Inspect the structureThe linter checks headings, paragraphs, and readability signals.
3
Ask better questionsCogito nudges the next thought without taking over the text.
Product philosophy

Local-first AI should support the writer's attention rather than replace it.

The best version of Ink is not another autocomplete machine. It helps you notice weak spots while keeping control of the text in your hands.

Why it matters

Architecture is the feature beneath future features.

ReliabilityLess interruption

Feedback should be available when useful and quiet when it is not.

ClarityOne writing loop

Cogito and the linter now point toward the same editorial workflow.

MomentumEasier to extend

A shared pipeline makes future writing features easier to build and reason about.

Final takeaway

Ink is getting a sharper point of view.

Local files, a small browser app, reflective AI, and document analysis are starting to feel like a writing workspace with intent.

Try Ink Read the full digest