For teams
Product
Inside Glueprint
Product tour The full workflow, in 16 narrated chapters Workspaces Sessions, code, and terminals together Editor & IDE Edit, preview, and debug beside your agents Tasks & boards Plan the work and hand it to agents Channels People and agents in one conversation Assistants Memory, routines, and ongoing work Git & review Review changes, branches, and GitHub Orchestration Split one job across many agents
Get started
Desktop app Download for macOS, Windows, or Linux Mobile app Your agents on iOS and Android Always-on hosts Set up a VPS or Mac mini with the CLI Supported agents Find the agents you already use
Explore the four steps of AI adoption
Security Docs Pricing FAQ Download free Sign in
Documentation
Changelog
D-1804Editor & IDE

Language features

Diagnostics, hover, completion, go-to-definition, rename, and formatting via LSP.

Available on
Available onDesktop
Reviewed
September 28, 2026
On this page

Glueprint runs Language Server Protocol (LSP) servers in the background and wires their results into Monaco. When you open a folder, the engine scans for the language servers it knows about and starts the ones that are installed.

Setup and per-server status live in Settings > Language servers. This page covers what you can do once an LSP is running.

Diagnostics

Errors, warnings, info, and hints from the LSP show up:

  • Inline in the editor with red / yellow / blue squiggles under the offending range.
  • In the gutter with severity icons.
  • In the minimap as colored marks.
  • In the Problems panel (the Problems button in the IDE’s footer) as a flat list across every open file.

Click any squiggle, gutter mark, or problems entry to jump to the source location.

Hover

Hover over a symbol to see its type signature, doc comment, and any extra info the language server exposes. The hover card supports markdown.

Completion

As you type, completion suggestions appear from the language server. Use arrow keys + Enter / Tab to accept. The list includes whatever the server provides — variable names, methods, snippets, imports, etc.

  • Go to Definition — right-click + Go to Definition, or hold Cmd/Ctrl and click.
  • Go to Declaration, Go to Type Definition, Go to Implementation — right-click menu when the LSP supports them.
  • Find All References — right-click + Find All References. Results land in the references panel.
  • Go to Symbol in File — Cmd/Ctrl+Shift+O in the editor, or the Outline panel.

Rename

Rename a symbol with F2 (or right-click + Rename Symbol). Glueprint uses the LSP’s rename support to update every reference across the project in one edit.

Code actions

The lightbulb that shows up next to certain lines is the LSP’s code actions — quick fixes for diagnostics, refactors, organize-imports, and so on. Click the lightbulb or use the keyboard shortcut your platform binds for code actions.

Formatting

Right-click + Format Document, or right-click + Format Selection, runs the LSP’s formatter on the buffer. Enable Format on Save in Editor preferences to run the formatter automatically every time you save.

Supported languages

Auto-discovery currently covers Rust, TypeScript, JavaScript, Python, Go, PHP, C#, and Java. C# language features require csharp-ls; see Language servers for setup. F# and Kotlin get syntax highlighting from the editor, not language features. The server has to be installed on the host — Glueprint doesn’t ship language servers; it talks to ones already on your PATH or in the standard install locations. Java is the one exception: with a JDK installed, Glueprint can download jdtls for you from Settings > Language servers. Go to definition on a JDK or dependency class opens its source (attached or decompiled) in a read-only Library source tab.