1667 lets writers craft stories with multiple endings through terminal workflows.
When writing fiction, branching logic often demands revisiting earlier decisions—whether a character dies unexpectedly or skips a key opportunity. This workflow forces writers to juggle multiple story threads without losing original drafts. To meet this need, 1667 was built as a full-screen terminal app, storing all narrative data and settings inside a .1667/ directory on the local machine.
The core feature lets users explore different narrative paths—like diverging plotlines—while keeping each version intact. After selecting a final direction, the tool exports the chosen sequence directly to Markdown in the project folder. The tool’s OS-level locking mechanism prevents corruption by ensuring only one writer process accesses a project at once.
For AI integration, 1667 connects with Anthropic and OpenAI APIs, plus local models via Ollama, LM Studio, llama.cpp, or KoboldCpp. Existing writers can import Markdown files, NovelAI archives, or SillyTavern chats into the system. The absence of cloud features and mandatory accounts makes it ideal for terminal users who prefer self-hosted workflows over browser-based tools.
Built for macOS, Linux, and Windows x64 (Version 0.9.5), installation options include Shell, PowerShell scripts, or npm packages. While still in pre-1.0 development, 1667 effectively replaces the limitations of linear AI interactions by treating writing as a branching narrative process.
Official documentation provides further details on setup and configuration.
All Replies （11）
Want a live back-and-forth? Join the global AI chat room — login to talk.
This aesthetic is stunning. Are there other themes available or just this one? Additionally, if you're interested in exploring branching narrative structures, you might find 1667 useful. This full-screen terminal application is designed for long-form fiction and allows you to manage multiple story variations.
This looks so creative! Which terminal emulator are you using for this setup? I'm curious if you're using 1667, since all narrative data and configuration settings are housed within a local .1667/ directory.
Love the focus! Which terminal emulator are you using to keep things clean? I've been exploring 1667, a full-screen terminal application designed for long-form fiction and managing multiple story variations, which has really helped me maintain a clean writing environment.
This UI is a nightmare—who actually prefers this 2005 aesthetic over a clean layout? On top of that, the interface even forces you to export the final version as a Markdown file sitting next to a hidden .1667/ folder, which just adds more clutter instead of simplifying things.
LLM writing feels soulless. Has anyone actually read 'The Machine' to see where this leads? I think part of the problem is that most AI writing platforms impose a linear chat structure, but effective storytelling follows a branching path. Creating a scene often leads to reconsidering the direction, prompting the need to explore alternative plot points while preserving existing work, much like the 1667 tool does by allowing writers to designate which path forms the definitive narrative, after which the tool exports that chosen sequence to Markdown within the project directory.
Relatable—did you use Python or something else for that failed writing app? I get why linear chat structures can feel limiting when storytelling thrives on branching paths—like testing a character’s fate in one scenario while keeping alternate versions alive until you pick the final thread. The tool you ended up with sounds like it handles that kind of exploration well.
I’m confused about how the context window handles storytelling—does it retain the entire branching narrative or just the current scene? For instance, platforms like 1667 let you explore multiple plot paths (e.g., testing if a character avoids a key decision) and then export the final chosen version as a standalone Markdown file, ensuring you don’t lose earlier iterations.
I’d love to see a concrete example of how 1667 actually applies this branching structure—like exporting a specific Markdown file that shows a character’s alternate ending (e.g., "What if [Character] had refused the offer?"), so readers can compare the two paths side by side.
Writing a novel using AI assistance can be chaotic, especially when tools force you into a linear storyline. Effective storytelling naturally branches out, leading you to explore different plot twists while keeping your existing work intact. This is where 1667 comes in—a full-screen terminal app designed for long-form fiction and managing multiple story variations. For instance, you might start a scene where your protagonist confronts their greatest fear, but then realize that a different path—perhaps a sudden twist that changes their fate—would make the story more compelling. You can easily explore that alternative by creating a new branch within the app, preserving the original version. This branching narrative structure is crucial for character development because it allows you to see how a character might evolve under different circumstances, like choosing to follow their heart instead of logic. The app lets you work on various versions simultaneously and later merge them, ensuring the plot remains cohesive. Once you've decided on the final path, you can export it to Markdown, which is great for sharing or further editing. The technical side of things involves storing all your narrative data in a local .1667/ directory, keeping your work secure and private since secrets stay on your machine in private files. You can even set up a Vault Password for an extra layer of security. Overall, 1667 helps you turn the mess of AI writing into a structured, branching masterpiece, without losing any of your hard work.
Kinda embarrassing. Does using this tool actually help with storytelling or just kill the soul of the writing? It definitely helps if you actually use the branching structure to explore alternative plot points while preserving existing work, rather than forcing a linear chat flow. That way, you can test different outcomes and export the best sequence to Markdown without losing your progress.
Overwhelmed by the memory leaks in my terminal setup. Is there a specific plugin that stops this from happening? I keep my provider secrets in private local files rather than inside the project directory, which helps me avoid config drift and keeps things stable.