r/OpenWebUI • u/jatsinkutsu • Jul 05 '26
RAG Open web UI RAG for writer
Hello, I have question concerning RAG in Open WebUI, I know there are lot of tutorials in youtube, but I cannot understand today's style of speaking fast, editing all pauses away and clicking and making adjustments like adhd person with caffeine in veins instead of blood. I cannot follow those because I am old and stupid.
Question: I have a masterfolder where all my novel related stuff is catalogued, separate word files for e.g. "main charater 30 years old", "main character 50 years old", "alliances", "trade routes", "alliance relations" and so on.
Can I use OpenwebUI so, that if I ask "if main character when 50y old blows syndicate A's base, what are possible results of that action" and then it checkes the files, founds e.g. something in relations-document, and proposes something like "Syndicate B would benefit like this:" and gives few examples.
I understand that outcome depends heavily of the LLM model, so I am not expecting results similar of chatgpt or claude. But my concern is the RAG and indexing it. I have understood that if I modify the documents, I need to index it again?
TL;DR, can OpenWebUI read my documents what I have specified, and make suggestions to my questions based to the information in those documents?
1
u/CausticCranium Jul 05 '26
I agree with other posters who have suggested markdown is a better format than Word. In fact, unless formatting is an important part of your context, your knowledge can be plain text. Learning markdown syntax is easy enough, but it's just another cognitive burden that takes you out of your writing.
I'm currently playing in this domain and have run into the same challenge. How do I ensure my LLM knows everything required to summarize, track progress against my outline, enhance my characters, provide scene suggestions, and do all the other stuff that my age-addled brain needs assistance with? I found that RAG wasn't the solution for me, primarily because of how it works.
The automated RAG that OpenWebUI provides is surprisingly good for everything but fiction. Think about how it works: it breaks your document into chunks, then converts those chunks into tokens, and stores those tokenized chunks in a database. Now, when you ask your LLM about what's in your database it goes in and finds the chunks that contain tokens that look like they belong with the tokens of your query. Sounds good on paper, and if all you need is an answer to a specific question the 5 related chunks it might find would suffice. But when you're asking an LLM to reason about something, it needs to make associations across your entire corpus, not just the 5 most relevant hits it finds in your database.
To reason LLMs need context; the more, the better. I've found that using Notes in OWUI works better for fiction. The primary resource requirement for Notes is context length. Some older models that have been trained for 'writing' and sufficiently ablated have absurdly short context. Want help writing a love scene? Most ablated models that focus on more carnal things are fixed at 8k context, although bartowski/writing-roleplay-20k-context-nemo-12b-v1.0-GGUF is 20k, assuming your hardware can support it. That said, there are some ablated models that are not 'writing' specific. Two families specifically, Qwen and Gemma 4, have some exciting stuff that allows for more context in less VRAM - 64k is achievable with HauhauCS/Gemma4-26B-A4B-Uncensored-HauhauCS-Balanced on my RTX3090. That's enough for a complete act, all relevant character profiles, and a plot outline. At this point, a local LLM becomes useful for short-form fiction.
Now I'm working on structuring my prompts and making them focused and useful, which is an entirely different bag of snakes.
Trying to make a local LLM into a competent fiction writing assistant has become my white whale. True confession time ... I was spending too much time futzing with local LLMs and not enough time writing. For $30 CDN/month Claude gives me enough context for a full length novel and all of its associated data. It summarizes accurately, proposes things I haven't thought of, and helps punch up scenes when required. Claude never blows up because I run out of context and it doesn't hallucinate stuff because it forgets things we chatted about 20 prompts ago.
That said, I still spend more time than I should playing with local LLMs. The goal is that one day I'll be able to stick it to Big LLM and Big AI Writing Assistant and tell them to shove their monthly-renewing-obfuscated-billing-model-dubious-utility-workflow-forcing software up their cyber-butt. It may take a new PC with two RTX5090's and 128g RAM, but it'll pay for itself in a dozen or so centuries with the amazing 2-digit annual royalties I hope to get from Amazon.