Trade-offs · 2026-10 · 1 min read

AI should be part of the editor, not another chat box

Putting AI in a side chat box is like asking it to work through glass — it can see your document, but it cannot touch it.

Illustration for: AI should be part of the editor, not another chat box

Almost every editor has added an AI chat box by now. Our view is that this is only the first step — and the easiest one.

The problem is not the position, it is the permission

A side chat box can read what you paste into it, but not the document you are editing, its backlinks, or the notes it references. It gives advice; you still do the typing. Behind the glass, it cannot really help.

Make it a first-class citizen

In Textrix, AI is a first-class citizen: it works with the context of the current document, can search across files, run multi-step tasks and call tools (MCP). It is not an add-on but a capability of the workbench itself.

Review before it writes

The more capable it is, the more it needs brakes. AI changes to your files pass through a checkpoint first — nothing lands on disk until you confirm. That is not a limitation; it is what makes letting AI touch your documents safe to do.

  • Context-aware rewriting / continuation / polishing
  • Multi-step tasks and tool calls (MCP)
  • A checkpoint before writing to disk
  • Bring your own API key, or run a local model
← All posts

Keep reading

Two more articles from the same trade-off series.

Still in development

Not yet available for download. Join the waitlist and you will be invited first when it opens.

Email-collection mode: submitting opens a pre-filled message in your mail client.