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.
| Path | Scope |
|---|---|
| $OPENCUES_HOME | when set, the sole source; both folders below are ignored |
| <project>/.cues | this project; wins on name conflicts |
| ~/.cues | user-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.
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.
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.
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.
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.