Editor Setup for .oxoflow Files#
Workflow files (.oxoflow) are plain TOML — oxo-flow's
declarative workflow format. Most editors do not recognize the .oxoflow
extension yet, so configure one small file-type association and you get full
TOML support: syntax highlighting, bracket matching, folding, and formatting.
VS Code#
Workspace (zero setup, ships with the repo)#
The oxo-flow repository and every
oxo-flow-community workflow repository
ships a committed .vscode/settings.json:
Open the repository folder in VS Code and .oxoflow files highlight as TOML
immediately — nothing to install.
User-level (all folders, all projects)#
To apply the association everywhere, open the command palette
(Cmd/Ctrl+Shift+P) → Preferences: Open User Settings (JSON) and add the
same files.associations block. Alternatively: Settings → search
files.associations → Add Item with key *.oxoflow and value toml.
Other editors#
Zed#
Add to ~/.config/zed/settings.json:
Helix#
Add "oxoflow" to the toml language's file-types in ~/.config/helix/languages.toml:
Neovim#
JetBrains IDEs (IntelliJ / RustRover / PyCharm)#
Settings → Editor → File Types, select TOML, and add the
*.oxoflow pattern in the File name patterns list.
Sublime Text#
Open an .oxoflow file → View → Syntax → Open all with current
extension as... → TOML.
Emacs#
Optional: schema-backed validation and completion#
For key-name validation and completion while editing, dump the JSON Schema reference and associate it in VS Code with the Even Better TOML extension's settings:
Note: oxo-flow schema exports a subset of the full format — the complete
reference lives in the
Workflow Format documentation.