Write without a model

You can use 1667 to organize prose that you write yourself. You do not need to set up a model provider.

The manual workflow includes these tasks:

• Import a Markdown draft.
• Edit story parts.
• Keep alternative takes.
• Select one story line.
• Add chapters and Facts.
• Use the tree and map views.
• Export the selected story line.

Start with a Markdown draft

Write your draft in a Markdown file. Use a # heading for the story title. Use ## headings for chapters. Separate story parts with blank lines.

On macOS or Linux, import the file with these commands:

1667 init
1667 import draft.md
1667

On Windows, use these commands in PowerShell:

1667.exe init
1667.exe import draft.md
1667.exe

1667 creates a new story. The source file stays unchanged.

Write and edit takes

Press w on a story part to write a sibling take. A sibling take is another version of the same story part.

Press e to edit the focused story part. A normal save keeps the earlier text as another take. The editor also has an action to update the current take.

A direction is optional in the editor. Put it above the first --- line. To write only prose, put --- on the first line and write the prose below it.

Use these keys to move and choose text:

The selected take at each point forms the story line. Other takes remain in the tree. You can select them again at any time.

Organize the story

Chapters, Facts, tags, and maps do not require a provider. You can write chapter titles, chapter summaries, and Facts yourself.

Export the selected story line

On macOS or Linux, run this command in the project:

1667 export

On Windows, run this command in PowerShell:

1667.exe export

1667 writes a Markdown file to the project root. The file contains the selected story line. It does not contain unselected takes.

Run the command again after you select different takes. 1667 writes the story line that is selected at that time.

Know which actions use a provider

The following actions request model output:

• Continue a story with Space.
• Send a direction from the composer with Enter or i.
• Request a Retake with r or R.
• Rewrite selected prose from the command palette.
• Create a story name with autoname story.
• Generate a chapter summary.
• Send a question in Aside.

If you do not use these actions, the workflow in this guide stays manual. Editing, take selection, chapters, Facts, maps, import, and export remain available.

Find your files

1667 stores each project in the .1667/ directory at the project root. An exported Markdown file is next to that directory.

Use a Vault Password if you want to seal the project files at rest. See Story storage.

Related documents

• Story storage
• Technical terms
• Facts, context, and model providers