Studio: your Java projects in IntelliJ or VS Code style
Studio is the part of Osiris where you work on code. It opens a project right inside Osiris and arranges it the way the IDE you know does — like IntelliJ or like VS Code, down to the tool windows, in Osiris's design. Both environments work on the same files as your real IDE.
Studio is still in beta — it works, but it is still changing.
Pick the environment once, then your project
The first time, Studio asks how you want to work: like IntelliJ or like VS Code. After that it opens with your projects — the same window for both: search, a new project, open a folder, and the projects you worked on last. Pick one and it opens; the Osiris sidebar folds down to its icons so the code gets the room. Projects at the top (or File → Close Project) takes you back, and Switch environment there changes the arrangement.
New project: Java or Kotlin, with Maven or Gradle
New project is laid out like the window of the same name in IntelliJ: on the left you choose what to create, on the right you fill in name, location and the rest; GroupId and ArtifactId sit under Advanced settings.
- New project — Java or Kotlin, built with IntelliJ's own build system, with Maven or with Gradle (Kotlin or Groovy DSL), with or without sample code.
- Empty project — just the project, without source code.
- Maven Archetype — quickstart or webapp from the built-in catalog. Osiris creates them itself, without fetching an archetype from the network.
- Minecraft — plugins for Paper, Spigot, Bukkit, Folia, Purpur, Velocity and BungeeCord. Step by step: Minecraft plugins with Claude in Studio.
The JDK field lists the JDKs Osiris finds on your computer — in JAVA_HOME, the package folders,
the JDKs IntelliJ downloaded, SDKMAN, Gradle, Homebrew and, on Windows, the vendor folders under
%ProgramFiles% — named the way IntelliJ names them. Maven and Gradle projects get the wrapper
(mvnw, gradlew), so they build without Maven or Gradle installed; on the
first run, the wrapper downloads the version it needs. The project is set up so that IntelliJ
recognises it as a Maven or Gradle project with the chosen JDK when you open it.
In IntelliJ style
On the left the project tree with IntelliJ's own icons, in the middle the open files with syntax colours, on the right the Maven or Gradle tool window with its tasks, and on the far right a narrow bar with a small chat with Osiris. At the top, as in IntelliJ, build and the run configurations with run, debug and stop.
With the Osiris plugin for IntelliJ the rest comes in live: the open file and the cursor position, unsaved changes and errors. Whatever you run, runs in IntelliJ, with the output shown in Studio.
In VS Code style
A title bar with menus and the command center, the activity bar with Explorer, Search, Source Control, Run and Debug and Extensions, tabs with breadcrumbs, the panel with Problems, Output, Debug Console, Terminal and Ports, and the status bar with line, column, encoding and line ending. The chat with Osiris sits in the secondary side bar. The layout is VS Code's; colours, icons and controls are Osiris's — in light and dark.
What cannot exist in Osiris — a debugger, extensions, several windows — is shown greyed out, the way VS Code shows it without the matching extension. The Terminal tab opens the Osiris terminal or your system's terminal in the project folder.
The same files, in both directions
Studio keeps no copy of its own. What you save in Studio lands on disk and your IDE loads it; what the IDE saves, Studio picks up. The project tree and open files follow changes from outside. Studio remembers the environment and the open project: after a restart — and in another browser — you land where you left off.
Building without the plugin
With IntelliJ and the Osiris plugin for IntelliJ, Maven goals,
Gradle tasks and run configurations run in IntelliJ, and Studio shows the output. Without the
plugin, Osiris starts Maven and Gradle itself, in the project folder: first the wrapper in the
project, then Maven or Gradle from your PATH, and for Maven finally the copy that comes with
IntelliJ. If JAVA_HOME is not set, Osiris uses a JDK it has found. The build button then builds
up to the jar — package with Maven, build with Gradle.
Debugging without the plugin means the same run with detailed output (-X -e for
Maven, --info --stacktrace for Gradle), not a debugger. A real debugger needs
IntelliJ with the Osiris plugin; there is no Osiris extension for VS Code.
The JAR field
Bottom left in Studio, the JAR field shows the newest jar from target/ (Maven) or
build/libs (Gradle); source and javadoc jars do not count. Put it on the clipboard as
a real file and paste it into the next program, drag it straight into a folder, or delete it so
the next build puts down a fresh one. A jar you drag out leaves the build folder once it has fully
arrived; on Windows, and on Linux in Nautilus or Dolphin, pasting moves it like a cut file.
IntelliJ plugins, managed from Studio
Plugins in Studio's start window, or File → Plugins… in an open project, opens a window arranged like IntelliJ's: Marketplace and Installed with the number of updates, a search, and for every plugin install, update, switch on or off and remove. Osiris works in IntelliJ's own plugin folder, and the JetBrains Marketplace picks the version that fits your IntelliJ build. As after Install in IntelliJ, changes take effect when IntelliJ restarts.
If the hammer and the green run arrow in IntelliJ stay grey, File → Repair IntelliJ helps:
it switches the Java, Maven and Gradle plugins back on, along with what they depend on, removes a
downloaded copy of a bundled plugin that does not fit this IntelliJ, registers the
pom.xml once as a Maven project and sets a JDK if none is set. It only switches
plugins on, never off.
Claude right next to the code
Studio is part of an AI development environment with a memory: the chat next to the code draws on the rules and notes in the brain of the connected project. The built-in editor and terminal are one click away.
IntelliJ is a trademark of JetBrains s.r.o., Visual Studio Code a trademark of Microsoft Corporation. Studio is modelled on their interfaces; Osiris is an independent product and not affiliated with either of them.