VS Code extension for Caffeine, the language that compiles service expectations to reliability artifacts.
- Install the extension from the VS Marketplace or Open VSX
- Install the Caffeine binary via Homebrew:
brew install caffeine-lang/tap/caffeine - Open a
.caffeinefile - That's it. The extension finds the binary and spins up the language server automatically.
If you installed Caffeine somewhere nonstandard, point the extension at it via the caffeine.serverPath setting.
- Syntax highlighting
- LSP integration (diagnostics, completions, go-to-definition, etc.)
- Format on save (enabled by default)
- Smart indentation, bracket matching, code folding
| Setting | Description | Default |
|---|---|---|
caffeine.serverPath |
Path to the caffeine binary. Leave empty to auto-detect from CVM, Homebrew, or PATH. |
"" |
caffeine.trace.server |
Trace LSP communication between VS Code and the language server. Useful for debugging. | "off" |
The trace.server setting accepts "off", "messages", or "verbose". If something looks off with the language server, flip it to "verbose" and check the output panel.
| Command | Description |
|---|---|
Caffeine: Restart Language Server |
Restart the language server without reloading the whole editor |
You need the Caffeine binary installed. The extension looks for it in this order:
- Custom path from
caffeine.serverPath(if set) - CVM --
~/.cvm/current/caffeine - Homebrew --
/opt/homebrew/bin/caffeine(Apple Silicon) or/usr/local/bin/caffeine(Intel) - System
PATH
Requires VS Code 1.75+.
- Language server not starting? Check that
caffeine lspruns from your terminal. If it does, the extension should pick it up. If not, setcaffeine.serverPathexplicitly. - Weird LSP behavior? Set
caffeine.trace.serverto"verbose"and check the Caffeine output channel in VS Code's Output panel. - Still stuck? Open an issue.
MIT