If you're up for learning Emacs, it has several packages for integrating with Ollama, such as ellama. It has worked satisfactory for me.

Mikupad is incredible:

https://github.com/lmg-anon/mikupad

I think my favorite feature is the 'logprobs' mouseover, aka showing the propability of each token that's generated. It's like a built-in thesaurus, a great way to dial in sampling, and you can regenerate from that point.

Once you learn how instruct formatting works (and how it auto inserts tags), it's easy to maintain some basic formatting yourself and question it about the story.

It's also fast. It can handle 128K context without being too laggy.

I'd recommend the llama.cpp server or TabbyAPI as backends (depending on the model and your setup), though you can use whatever you wish.

I'd recommend exui as well, but seeing how exllamav2 is being depreciated, probably not the best idea to use anymore... But another strong recommendation is kobold.cpp (which can use external APIs if you want).

I'm not sure if this is what you're looking for, but for AI generated novels, we have Plot Bunni. That's specifically made to draft, generate an outline and chapters and then the story. Organize ideas... It has a lot of rough edges though. I had some very limited success with it, and it's not an editor. But it's there and caters to storywriting.

I recently started with Zed. It works with ollama.

Too early for me to give more of an assessment than "it works".

In an ideal work what exactly would you want an AI integrated text editor to do? Depending on what you need to have happen in your workflow you can automate copy pasting and automatic output logging with python scripts and your engines api.

Editing and audiing stories isnt that much different from auditing codebases. It all boils down to the understanding and correct use of language to convey abstraction. I bet tweaking some agebic personalities and goals in vscode+roo could get you somewhere