Config files

All OpenCues behaviour is defined by plain files, read from the project first and your home folder second. Edits apply within about 2 seconds of saving, with no restart.

Where files are read from

PathScope
$OPENCUES_HOMEwhen set, the sole source; both folders below are ignored
<project>/.cuesthis project; wins on name conflicts
~/.cuesuser-level, everywhere else; the settings file is read from here only

A project can commit its own .cues/ folder to version control, so a repository carries its vocabulary and everyone who clones it gets the same cues. A missing folder is skipped, not an error.

What is in the folder

~/.cues/ OPENCUES.md settings AUDITORS.md auditor master file IDENTITY.md personal fields, if you add any cues/ one folder per cue blanks/ one folder per blank, scripts beside their blank auditors/ one folder per auditor

opencues install <host> seeds this with a working set: the spelling, formality and calendar cues, and blank folders including volume, brightness, weather, dictionary, stocks and notes. Seeded files are ordinary files, editable and deletable. A CUES.md master file is yours to add; nothing ships one.

Edits apply within ~2 seconds

Files are re-read while a host runs.

A saved change is picked up by the next keystroke, roughly 2 seconds later. No restart, no reload command. Iterating on a cue file is edit, save, type a word, look.

Shared cue files

A team shares a vocabulary by committing the project's .cues/ folder: everyone who clones the repository gets the same cues, and an edit arrives with the next pull.

Cue files written from a chat session

A Claude Code skill and an OpenCode plugin can write .cues/CUES.md from an ongoing conversation, turning the session's recurring vocabulary into cue sources. The output is a normal cue file: editable, deletable.