Introduction
Orihai is a Windows application for long interactive fiction. Everything you write stays in a file on your own disk.
The pages#
- Installing Orihai
- What it needs, where on your disk your stories are kept, and how to back them up or move them to another machine.
- Models and keys
- Orihai AI, your own key, or a model on your own machine, and every field of a model profile. Start here, because nothing else works until a model is set.
- Guiding the story
- Asking for another take, changing what you sent, rewinding, and where to put a correction so you stop making it twice.
- Writing a scenario
- How to build one that plays well: the opening scene first, a world sheet worth its cost, and what to fix after ten turns.
- Scenarios
- The world, its cast and its opening scenes: world sheet, style directives, lore and places.
- Characters
- Every field on a cast member and on the persona you play.
- Playing a story
- Writing turns, asking for another take, and what the second model is doing while you read.
Three ways to run it#
The first needs nothing set up. The other two need no account and send nothing to an Orihai server.
- Orihai AI, our own managed models. Make an account at account.orihai.com, sign in, and write: no key to find, no provider to choose, no card. Free while it is being tested, with a monthly allowance. It is the one arrangement in which an Orihai server processes anything, and the privacy policy says what it sees.
- Your own key. Anthropic, OpenAI, OpenRouter, or any OpenAI-compatible endpoint. The application talks to your provider directly, and the bill is the provider's.
- A model on your own machine. Ollama, LM Studio, llama.cpp, anything that answers on the OpenAI-compatible shape. Nothing leaves the computer and there is no key to bring.
You are not choosing once. A model profile is a saved setting, a scenario can name its own, and a story keeps the one it started with, so a story written on a local model and a story written on Orihai AI can sit side by side in the same library.
What is on your disk#
Everything you write. One SQLite file, in your own user data folder, alongside a folder of any images that were generated.
It is an ordinary database file. You can open it in any SQLite browser, and a backup is a file copy. There is no synchronisation, no telemetry and no crash reporter, so the file is not mirrored anywhere unless you copy it yourself.