Processing modes
Choose from three processing modes when submitting a brain dump:The streaming pipeline (SSE)
When processing in Auto or Review mode, AllKnower opens a Server-Sent Events (SSE) stream to the Portal:- Live stream: The dashboard renders the parser’s step-by-step reasoning and a stream of extracted entities (with titles and types) in real time.
- Observability: The stream prints live token counts, processing latency, and estimated OpenRouter cost.
- No timeout: The SSE pipeline uses active
: keepalivecomments to prevent browser timeouts during long inference runs, which can take up to a minute.
Bulk batch processing
If you have a backlog of text files (e.g. dozens of campaign session recaps or old worldbuilding docs), you can use the Bulk Brain Dump feature:- Queueing: Submit multiple text documents at the same time. The Portal sends them to AllKnower’s background worker, which queues them in the
brain_dump_jobstable. - Background execution: The system executes jobs sequentially. Monitor progress, pause, or cancel queued dumps from the settings page.
- Notifications: Enable push notifications in the Portal to receive alerts on your desktop or phone when a batch job completes.
Best practices for writing dumps
To improve extraction accuracy:- Mention relations explicitly: Write how things connect.
- Good: “Sir Roderick is a member of the Silver Gauntlet. He reports directly to Commander Vane.”
- Bad: “Sir Roderick works with Vane at the Silver Gauntlet.”
- Provide context for ambiguous names: If a word is a place, spell out that it is a location.
- Good: “The party traveled to Eldoria, a coastal trade town…”
- Bad: “The party traveled to Eldoria…”
- Keep core terminology consistent: Try not to refer to the same group or location by multiple names in the same dump unless you explicitly state they are aliases.