Most AI writing tools work like a black box. You highlight text, hit a button, and the AI rewrites your paragraph. Maybe it improved things. Maybe it nuked a sentence you liked. You can undo, but you lost visibility into what changed and why.
We built CoCraft to fix that. Part of the OCTO ecosystem, Apache 2.0 licensed. The core idea: AI is your writing partner, not your ghostwriter.
How the edit flow works
Select text. Tell the AI what you want in plain language, like 'make the claim less absolute' or 'add a disclosure about AI usage per journal policy.' AI generates an edit proposal, CoCraft shows a diff. Every change is highlighted. You accept or reject each one separately.
This matters more than it sounds. Revising a paper after peer review, you might get three comments touching the same section. One asks for an AI usage acknowledgment. Another flags your 'near-optimal' claim lacks empirical backing. A third points out a concurrent result computing the theoretical upper bound that you did not reference.
CoCraft lets you handle each comment, generate edit proposals, and go through diffs one change at a time. Keep what works, toss what does not.
Compilation error diagnosis
CoCraft has a diagnostic panel for compilation errors. Panel locates the error, AI proposes a fix in one step. Small feature, saves real time.
Connected to Octo
CoCraft connects into the Octo ecosystem, so collaborator discussions retain full context. Your co-author's notes about why a paragraph was phrased a certain way stay visible when the AI proposes changes.
Trade-offs we are honest about
The diff-based flow adds friction compared to just rewriting it all. For quick drafts where you do not care about granular control, it can feel slower. We think the trade-off is worth it for serious writing like papers and technical docs, but it is not the right tool for every use case.
Source code and ecosystem: OCTO on GitHub | Mano-P