GreyCat

Provides real-time syntax highlighting for GreyCat source code by delegating tokenization and semantic analysis to a local Language Server Protocol (LSP) server. The extension acts as an LSP client that communicates with the GreyCat language server (`greycat/lang`) to classify tokens and apply VSCode theme colors. Syntax highlighting is distinguished from semantic highlighting in the architecture, suggesting separate analysis pipelines for lexical vs. semantic-level token classification.

Delivers intelligent code completion suggestions by sending the current cursor position and file context to the GreyCat LSP server, which analyzes the syntax tree and symbol table to generate contextually relevant completions. Triggered via `Ctrl+Space` (or `Ctrl+Alt+Space` on macOS with workaround), the extension marshals completion requests with full project context, enabling suggestions that understand variable scope, type information, and available APIs. Completion quality depends on successful project loading within the VSCode workspace.

Automatically discovers and loads GreyCat projects within the VSCode workspace, establishing the project context required for all language features (completion, highlighting, diagnostics). The extension communicates project structure and configuration to the LSP server during initialization, enabling the server to build a complete symbol table and type graph. Project loading errors are surfaced to users with diagnostic messages, and the extension provides troubleshooting guidance for common issues (e.g., missing project files, incorrect workspace structure).

Captures compilation and semantic errors from the GreyCat LSP server and displays them in VSCode's Problems panel with file location, line number, and error message. Diagnostics are updated in real-time as the user edits code, providing immediate feedback on syntax errors, type mismatches, and other issues. The extension distinguishes between extension-level errors (e.g., project loading failures) and upstream LSP server errors, with guidance on where to report issues.

Registers GreyCat Binary file type (.gcb) with VSCode, enabling the editor to recognize compiled GreyCat artifacts and associate them with the GreyCat extension. This allows users to browse and inspect .gcb files within the editor, though full editing or decompilation capabilities are not documented. The extension may provide syntax highlighting or metadata display for binary files, depending on LSP server support.

Provides code snippets and templates for common GreyCat patterns (e.g., graph queries, ML pipeline definitions, real-time data processing workflows). Snippets are triggered via code completion or snippet commands and expand with placeholder variables that users can tab through to customize. The extension may include snippets for GreyCat's domain-specific language (DSL) constructs, reducing boilerplate and accelerating development.

Manages the startup, shutdown, and error recovery of the GreyCat LSP server within the VSCode extension lifecycle. The extension automatically starts the LSP server when VSCode opens a GreyCat project, monitors server health, and attempts recovery if the server crashes or becomes unresponsive. Server communication errors are logged and may be surfaced to users with troubleshooting guidance. The extension handles server initialization parameters and configuration, ensuring the server has access to project files and dependencies.

Exposes keyboard shortcuts for language features (e.g., code completion via `Ctrl+Space`) and provides guidance for resolving conflicts with system or VSCode shortcuts. The extension documents known conflicts (e.g., macOS 'Select the previous input source' blocking `Ctrl+Space`) and offers workarounds. Users can rebind shortcuts via VSCode's keybindings editor, though the extension does not provide a custom UI for shortcut configuration.

Automates extension packaging and distribution through GitLab CI, building the extension on every push to the master branch and publishing to the Microsoft VSCode Marketplace. The CI pipeline handles versioning, testing, and artifact generation, ensuring consistent and reliable extension releases. This approach decouples extension development from manual packaging, reducing human error and enabling rapid iteration.