Skip to content

Osiris is still in development — the official launch is coming soon. Try the preview free

Osiris
Account Try free
Editor · Terminal

A terminal with Claude and a built-in text editor

Two tools you reach for all the time while coding with Claude are built into Osiris: a text editor that leaves your files the way they were, and a terminal that starts your own shell in the project folder — and, when you type osiris, a session with Claude. Both run locally on Windows, macOS and Linux.

The text editor

The editor opens as Editor in the Osiris sidebar or in a window of its own. Osiris becomes the default app for text files such as .txt, .md, .yml, .json, .ini, .properties, .toml and .xml, so a double-click opens the file straight in an editor window.

config.yml — Osiris
The Osiris editor: config.yml open, three matches for “Shop” highlighted

Encoding and line endings stay as they were

When the editor reads a file, it remembers how the file is built — encoding, byte order mark, line ending — and writes exactly that back. A CRLF file stays CRLF, a file with a BOM keeps it. UTF-8, UTF-16 and Windows-1252 are recognised, so an old .ini or .properties file does not lose its umlauts on saving. Mixed line endings are unified to the most frequent one, and Osiris tells you before it does. Files that are not text are refused instead of being damaged.

The terminal

The built-in terminal opens from the sidebar or with Ctrl+`. Every tab is your usual shell, started in the folder of the connected project: zsh on macOS, the shell set for your account on Linux (usually bash), PowerShell on Windows. Switch to another view and the terminal is hidden; the shells keep running.

Terminal — Osiris
The built-in terminal in Osiris: git log and git status in the webshop project

Claude in the terminal: the Osiris session

Type osiris — or osiris code — in the built-in terminal, and a session starts in the folder you are in: in the style of Claude Code, with the name and design of Osiris. At the top it shows the Osiris mascot, the version, the model and the folder. The work is done by Claude in the background, with your own login and with your Ultrabrain and Memory behind it.

The command exists only in the terminal built into Osiris, not in your system's PATH. On macOS and Linux, claude there is still Claude Code itself. On Windows, where the built-in terminal runs in line mode, claude opens the Osiris session as well; Claude Code's own full-screen interface needs the system's terminal there — how to set it up is described in installing Claude Code on Windows. If you prefer a window to a prompt, the chat in Osiris does the same work with diffs and permission cards: a GUI for Claude Code.

What works where

On macOS and Linux the terminal is complete: colours, full-screen programs and resizing work. On Windows it is more limited for now: PowerShell runs in line mode — commands work, but there is no tab completion, Ctrl+C does not stop a running command, and full-screen programs such as vim or Claude Code belong in the system's terminal.

Part of the whole

Editor and terminal sit next to Studio, the project view in IntelliJ or VS Code style, and next to the chat with Claude, which draws on the rules and notes in the brain.