VS Code support for Forge.
- Run Forge files with robust process management (Racket discovery, version checks, graceful stop).
- LSP essentials: go to definition, hover, and document symbols.
- Intelligent code completion: 60+ Forge keywords and 9 smart snippets for common patterns.
- Syntax highlighting and language configuration for
.frg.
- Install Racket and Forge:
raco pkg install forge - Install the extension from the
- Open a
.frgfile and runForge: Run(or click the Run button).
Smart, non-intrusive completions for Forge. Trigger with Ctrl+Space (Windows/Linux) or Cmd+Space (Mac), or let it appear naturally as you type.
Features:
- 60+ Keywords: All Forge keywords (
sig,pred,fun,run,check,all,some,always, etc.) - 9 Smart Snippets: Common code patterns with tab-stop placeholders:
sig (snippet)→ Full signature declaration templatepred (snippet)→ Predicate with parametersrun (snippet)→ Run command with scopetest expect (snippet)→ Complete test block- Quantifiers:
all (snippet),some (snippet) - And more...
- Context-aware: Skips completions inside comments and strings
- Helpful documentation: Each item includes description and usage info
Forge: RunForge: StopForge: Continue Forge RunForge: Enable LoggingForge: Disable LoggingForge: Forge Docs
The extension includes a chat participant that lets students ask questions about Forge directly in VS Code's Copilot Chat. It comes bundled with the complete Forge v5 documentation, so answers are grounded in the official reference material — not generic LLM guesses.
- VS Code 1.93+
- GitHub Copilot (or another VS Code language-model provider) installed and signed in.
Open the Chat panel (Ctrl+Shift+I / Cmd+Shift+I) and type @forge followed by your question:
@forge How do I declare a sig with fields?
@forge What does "lone" mean?
@forge Why am I getting a "contract violation" error?
| Command | Description |
|---|---|
@forge /docs <topic> |
Look up the official Forge documentation for a specific topic (sigs, quantifiers, temporal operators, etc.) |
@forge /explain |
Explain Forge code or concepts — automatically includes the active .frg file as context |
- Bundled docs — The full Forge v5 documentation is shipped inside the extension as structured data (see
client/src/forge-docs.ts). No network fetch needed at query time. - Keyword search — When a question comes in, the extension scores every documentation section against the query using keyword and title matching, then selects the most relevant sections.
- LLM augmentation — The relevant doc sections, plus the user's current
.frgfile (if open), are sent as context to the language model alongside a Forge-specific system prompt. - Pedagogical guardrails — The system prompt instructs the model to guide students toward understanding rather than providing homework solutions outright.
- Open your
.frgfile. - Open Chat and type:
@forge /explain - The assistant reads your file and walks through the model, explaining each sig, predicate, and constraint.
- Follow up with:
@forge Why is my run returning UNSAT? - The assistant uses the relevant "Running" and "Bounds" documentation to help you debug.
| Setting | Type | Default | Description |
|---|---|---|---|
forge.racketPath |
string | "" |
Path to Racket executable. Leave empty to auto-detect. |
forge.minVersion |
string | "3.3.0" |
Minimum Forge version required. |
forgeLanguageServer.maxNumberOfProblems |
number | 100 |
Max diagnostics produced by the server. |
forgeLanguageServer.trace.server |
string | "messages" |
LSP trace verbosity. |