enForged is your creative writing partner. It helps you write stories with an AI that actually understands the world you've built. Great for fanfiction, original fiction, or any creative writing project.
Build a story universe:
Then write alongside an AI that knows it all. Nothing to install, no account to make, and your work stays private in your browser. You'll just need a key from an AI provider like Claude or OpenAI (or a free local one via Ollama).
Lore entries are the world-building backbone of your universe. Every chat message is sent with your lore as context so the AI always knows your world.
| FIELD | SENT TO AI? | PURPOSE |
|---|---|---|
| Type | Yes | Categorises the entry (Character, Location, etc.) |
| Name | Yes | How the AI refers to this entity |
| Core Description | Yes | Brief overview the AI reads first |
| Type-specific fields | Yes | Structured metadata (see below) |
| Tags | Yes | Additional keywords for context |
| Relationships | Yes | Bidirectional links to other lore entries, each with a label and optional notes describing the connection from both sides |
| Private Notes | No | Your private thoughts, planned twists, spoilers the AI should never see |
Canon vs Working Ideas: Canon lore is locked-in fact; the AI must never contradict it. Working Ideas are possibilities treated as plausible but not definitive. Use Working for things you're still developing.
| LORE TYPE | TYPE-SPECIFIC FIELDS |
|---|---|
| Character | Appearance, Personality, Motivation/Goals, Dialogue Style, Role in Story |
| Location | Atmosphere/Mood, Key Features, Significance, Who Frequents It |
| Faction | Goals/Agenda, Values/Ideology, Key Members, Relations to Other Factions |
| Magic/Power | How It Works, Limitations/Cost, Who Can Use It, Visual Manifestation |
| Timeline | When (in-story), What Happened, Consequences, Characters Involved |
| Rule | The Rule, Why It Exists, Consequence of Breaking |
| Writing Style | Narrative Voice, Tone, Prose Style, Pacing, Dialogue Approach |
| Other | (core description only) |
Any lore entry can be linked to any other via the Relationships section in the edit modal. Each relationship is bidirectional: you define both sides at once so neither entity needs to be edited separately.
Both labels must be filled for a relationship row to be saved. When the entry is saved, the linked entity's relationship list is updated silently, so you will see the reciprocal label appear on that entity's card without opening it. Removing a relationship row and saving will also remove the reciprocal from the other entry.
Relationship labels and notes are included in the AI context alongside the entry's other fields, so the model understands the web of connections between characters, factions, and locations.
In the Lore Vault tab, click ↓ Import Lore to cherry-pick individual lore entries from any other universe into the current one. Each universe's entries appear in a collapsible section; select as many as you want across multiple universes and click Import Selected. Imported entries receive new IDs and are fully independent; editing them will not affect the originals.
The Story So Far tab connects two things: the raw beats you write, and the polished summary the AI generates from them.
Story Beats are short factual notes about what has happened: "Rin discovered her quirk was inherited from her father", "The League attacked during exams". Add them manually in the text box, or commit an AI response from Chat using + Add to Beat.
The Summary is compiled by the AI from your beats. Click ✦ Summarise after adding beats. The summary is injected into every chat session; it's how the model knows the current state of your story without re-reading the full history.
In epic mode, beats are off. The Story So Far summary stays as a hand-edited scaffold; per-scene records live as events on the Timeline tab. See the Epic Mode section below.
Every message is sent with your full story context: lore, summary, and recent chat history. The context bar at the top of the chat panel shows what's included; click any chip to toggle it on or off for the next request.
Multi-generational stories with hundreds of lore entries break the classic "send everything every turn" model. Epic mode replaces it with an era-aware retrieval pipeline that runs entirely in your browser.
Convert classic to epic: hover any universe in the sidebar and click the ⇄ button. The convert dialog creates a non-destructive duplicate (the original classic universe stays put). Optionally click ✦ Suggest Eras with AI to have the model read your beats and propose 2-6 eras with assignments; preview, rename, reassign, then apply.
Hover over any universe in the sidebar to reveal the ⧉ duplicate button. Clicking it opens a dialog with three modes:
Open ⚙ Settings → AI Prompts to view and customise the five prompts enForged sends to the AI. Leave any field blank to use the built-in default.
| PROMPT | USED FOR |
|---|---|
| Co-Author Instructions | Behaviour rules appended to every chat, e.g. "never contradict canon", "flag invented details" |
| Summary Compiler · System Role | The AI's role definition when generating your Story So Far |
| Summary Compiler · User Instructions | Format rules for the story brief (EVENTS / STATE / THREADS structure) |
| AI Seed · Story-Shape Role | The AI's role when helping you define a new story after duplicating a universe with Lore + AI seed |
| Epic Convert · Era Suggester | Used by "Suggest Eras with AI" when converting a classic universe to epic; the AI reads your beats and proposes eras with assignments |
Each prompt has two buttons: Clear (empties the field; blank means use the built-in default on the next call) and Default (fills the field with the built-in text so you can read and tweak it). Custom prompts travel with your backup JSON when the Custom AI prompts category is ticked in the export modal.
Classic state lives in localStorage under enforged_v2_state; epic state (eras, events, scope, pinned) under enforged_epic_state. Vectors live in IndexedDB and are regenerated on demand (not backed up). Everything persists across page reloads but is browser- and device-specific.
The sidebar's Export and Import buttons open per-category modals so you choose what travels with the file:
| CATEGORY | EXPORT DEFAULT | WHAT IT COVERS |
|---|---|---|
| Universes | ✓ ticked | All universes, lore, beats, chat history, and epic timeline data (eras, events, scope, pinned) |
| API keys & tokens | ☐ opt-in | Claude / OpenAI / Drive token. Keep the file secure |
| Settings | ☐ opt-in | AI provider, model selection, font, history window, chip defaults |
| Custom AI prompts | ☐ opt-in | Any prompts you customised in Settings |
On import the defaults flip: categories present in the file default ticked so applying everything is the obvious path; untick to skip. Imported universes get fresh IDs and merge alongside existing ones; epic state remaps so eras and events keep their cross-references.
.json file; Import reads one back.Classic mode: a flat assembly of every lore entry plus the Story So Far summary plus your customisable instructions.
Epic mode: same shape, but Canon/Working sections are replaced by RELEVANT LORE and RELEVANT EVENTS containing only the items the retrieval pipeline picked for the current turn (era-filtered, cosine-ranked, packed into the token budget). The active era is named at the top. Pinned lore and Writing Style entries are always included. An extra epic-only instruction tells the AI to append a hidden 📌 EVENT: metadata block to every response, which powers the + Add to Event chat button.
What is never sent (both modes): Private notes on lore entries, individual story beats (only the compiled summary), and internal system messages from the chat history.
enForged runs entirely in your browser, but it needs an AI backend to do the actual writing. This walkthrough gets you from zero to your first co-authored sentence in a couple of minutes.
Tip: clicking any URL on this page copies it to your clipboard.
You'll need exactly one of these. Your API key (or Ollama URL) stays on your device. It's saved to localStorage and sent only to the matching provider over HTTPS.
| PROVIDER | COST | NOTES |
|---|---|---|
| Claude (recommended) | Paid | Best prose quality. |
| OpenAI | Paid | Widely available. |
| Ollama | Free | Runs locally; quality depends on the model and your hardware. |
You only need one. Follow the bullet for the provider you picked above. Skip the others.
sk-ant-). You'll need to add a small amount of credit before the key works.sk-). Billing must be set up on your account.OLLAMA_ORIGINS=* ollama serve so this page is allowed to reach it, and (2) you've already pulled the model you want to use. Then open enForged via http://localhost:8080, because Ollama blocks file:// origins even with OLLAMA_ORIGINS set.Pick your provider, paste your key, choose a model, then Save. Click Test connection to verify; a successful response shows ✓ enForged OK (or similar) in monospace text.
If the test fails, the most common causes are: a typo in the key, no billing/credit on the account, or (for Ollama) the server isn't running or CORS isn't configured. Same fields are also available later via the ⚙ Settings panel.
You're ready to write. Click below to open the new-universe dialog: give it a name and an optional premise, and you're off. The How to use enForged guide (linked from the home screen) covers everything past this point: lore, beats, chat, prompts, backups, and (for multi-arc stories) epic mode with an era-aware Timeline tab and an in-browser retrieval pipeline that keeps the AI focused as your world grows.
If your world already exists somewhere (a draft, a worldbuilding tool, even a published book), you can seed a universe from it instead of building lore by hand. Almost any source can be turned into enForged JSON via your LLM of choice:
The flow is the same regardless of input:
[paste your story text here] with your text, attach your EPUB / PDF / JSON file, or replace it with the title of a known story..json file.The same prompt is also available later from the sidebar's Import section, under ✦ Generate JSON from existing story.
Extraction is approximate. Expect to clean up names, merge near-duplicates, and adjust canon flags before writing. For very short drafts it's usually faster to enter lore manually.
Everything is stored in your browser by default, which means clearing site data wipes your work. If you want an off-device copy, open ⚙ Settings → Google Drive Backup and follow the in-panel instructions for getting an OAuth token from the OAuth Playground. Tokens expire after about an hour and need to be refreshed manually.
This is currently a thin layer over the Drive REST API and the OAuth Playground flow: usable, but rough edges remain. Local Export / Import is the more reliable backup until this stabilises.