Use Prismio in IntelliJ
Install the Prismio plugin for JetBrains IDEs, start a project, and write, navigate, run and check code from the editor.
Last verified
On this page7 sections
Writing Prismio in a plain text editor means switching to a terminal to see whether it compiles. The Prismio plugin for JetBrains IDEs shows the compiler's errors as you type, completes, navigates and renames with the compiler's own knowledge, fills the run menu from your project, and creates new projects for you.
The plugin does not bundle a compiler. It uses the prismio you installed, so install the toolchain first.
Install the plugin
- Open Settings | Plugins | Marketplace.
- Search for Prismio and click Install.
- Restart the IDE if it asks.
It needs a JetBrains IDE from 2026.2 on, and works in IntelliJ IDEA and CLion, where it has been tested. It also passes JetBrains' compatibility check against WebStorm and RustRover 2026.2, but has not been used in them by hand. IDEs older than 2026.2 cannot install it.
Choose a compiler
The plugin finds prismio on your PATH by itself. If it cannot, or you want a different one, open Settings | Languages & Frameworks | Prismio, browse to the compiler, or press Auto-Detect. When Auto-Detect finds nothing, it says where it looked.
Everything that needs to understand the language comes from the toolchain's language server, prismio lsp, which the plugin starts with that compiler (see Set up your editor): errors, hover, completion, parameter and type hints, Go to Declaration, Find Usages, rename, the structure view, Go to Symbol, the import quick fix and Reformat Code. The plugin keeps no copy of the language, so a newer or older compiler shows its own functions, methods and errors, and there is nothing else to configure. The setting Use the Prismio language server, just below the compiler path, turns the server off; with it off the plugin keeps highlighting, folding, typing and running, and shows no compiler errors or completion.
Start a project
File | New | Project | Prismio asks for a name and a location. It has two more options:
- Compiler, filled in with the one the plugin found and the version shown under it: a green tick and
prismio 0.1.0, or the reason it cannot be used. Create stays unavailable until the field holds a working compiler. - Create Git repository, as in other languages. It appears only when the IDE has its Git plugin.
The dialog looks a little different in each IDE, but has the same options. In IntelliJ IDEA it shows Name, Location, the Git checkbox and Compiler. In CLion and the other IDEs, which show a Location field with no separate name, the plugin adds a Name field below it that follows the last folder of the location, so changing either one changes the other.
You get the same files prismio init writes:
my-project/
├── .gitignore
├── build.ums
└── src/
└── main.psmTo add a manifest to a folder that already has code, use New | UMS Manifest. It creates build.ums in that folder, named after the folder.
Run and build
The run menu is built from your build.ums: a Run entry for each executable target, plus Build, Test and every command the manifest declares. Green run buttons also appear beside fn main and beside each target and command in the manifest.
Run Current File runs a file that has a main. If the file is the entry of a target, it runs as that target.
Errors in the output are links: click src/main.psm:12:5 to jump to that line. Output colors, such as a program's std.term styling, show in the IDE console when your toolchain supports them.
Writing and navigating
The compiler checks your code as you type, including changes you have not saved, and marks problems in the file. On a missing name, Alt+Enter offers to add the import for it. A file that belongs to a larger program is checked as part of that program. If an error in another file stops the check before it reaches yours, one note says so.
- Ctrl+Q (or hover) shows a declaration's signature and its comment; Cmd+P inside a call lists the overloads and bolds the parameter you are on; the editor shows the type of a
letand the name of each parameter at a call. - Cmd+B or Cmd+click goes to a declaration. For a name from the standard library it opens the library's source (a read-only copy the language server writes out of the compiled module), and from an
import std.ioline it opens that module. - Alt+F7 lists usages, Shift+F6 renames a declaration and every use of it, and the structure view and Cmd+Alt+O (Go to Symbol) list what a file and a project declare.
- Reformat Code (Cmd+Alt+L) runs
prismio fmt, so it formats the way the command line and VS Code do.
A function with a syntax error in it is not analysed: until the line is finished, hover, hints and completion in the rest of that function are missing.
Documentation comments
Write documentation above a declaration with /// lines or a /** ... */ block, and Ctrl+Q shows it for the name:
/**
* The next id after `current`.
*/
fn nextId(current: Int) -> Int {
return current + 1
}The compiler itself treats these as ordinary comments; only the editor reads them as documentation. The plugin turns on the IDE's Render documentation comments setting the first time it runs, so these comments show rendered instead of as source. That setting is global, so it applies to every language, and you can turn it off under Settings | Editor | General | Appearance; the plugin will not turn it back on.
Formatting treats /** */ like /* */, and keeps a comment's leading stars lined up. An if that has an else is formatted over several lines, one branch to a block, with } else { kept together; an if with no else is left as you wrote it.
Not available yet
- Only IntelliJ IDEA and CLion have been used by hand. WebStorm, RustRover and the rest of the 2026.2 IDEs pass the compatibility check but are not confirmed.
- Where an IDE shows no Name field of its own (CLion and others), the New Project dialog lists Name below Location, not above it.
- Colours of names come from the lexer, not the compiler's semantic tokens, so a name can change colour a moment after the first answer.
- A function with a syntax error is dropped from the analysis as a whole (see above); it is a known limit of the compiler's parser, listed in its known issues.
- Only a manifest named
build.umsis recognised.
For how the plugin works and how to contribute to it, see the developer documentation.