Documentation

Everything users need for sessions, teams, models, widgets, settings, and Image Studio

The complete guide to IXIOM: parallel sessions, teams of a lead, workers and a guardian, model and provider switching, widgets, settings, and Image Studio, explained the way you use them day to day.

Bilingual: English and GermanFeature overview & FAQUpdated September 2026

Workflow guides

Choose a practical starting point for your next project. These guides explain the setup, the decisions and the limits of working with AI coding agents in IXIOM.

Search the docs
Jump straight to sessions, widgets, settings, FAQs, and more.

The workspace

Session bar, terminal, and status line in one view: your CLIs run side by side here, each session with its own backend.

Right after launch

Sessions, widgets, and history are one click away: the app boots in under a second and is ready to work immediately.

A workflow begins

Create a session, pick a backend, set a goal: this is how a typical workflow starts in IXIOM.

The workflow in motion

Results, diffs, and status updates come together in the session while the agent works.

Open and start fast

Create a session, name it, add an optional goal, and choose the backend that fits the job before you type the first prompt.

Use the right view

Switch between chat, terminal, collab, buddy, and Image Studio. Single, split, quad, and grid layouts let you shape the workspace around the task.

Work in parallel

Run several sessions at once: one researching, one building, one reviewing. Each session keeps its own backend, model, and permissions.

German and English

Both the website and the app support both languages. You can switch language from the site nav and inside the app under Look.

Workflow

Sessions, views, and layouts

The session layer is the center of IXIOM. It decides what you work with, how the workspace looks, and how much stays open in parallel.

Session start
Name, goal, backend, model choice for Claude, Codex, or Gemini, skip-permissions for supported backends, Shell or WSL startup commands, local agents, skills, and OpenClaw agent selection.
Management
Run multiple sessions, rename them, search them, pin them, mark them done, tag them, keep quick notes, restore history, and attach to already running external CLI sessions.
Views
Chat for guided AI work, Terminal for real CLI sessions, Collab for shared work, Buddy for the companion system, and Image Studio for image tasks.
Layouts
Single, Split H, Split V, Quad, and Grid. Tiled modes can be switched by shortcut and navigated by keyboard focus.
Environments

One project, one world

Environments are the layer above sessions. If you work on several projects at once, this keeps them fully apart instead of merely sorting them.

What an environment is
The top level. An environment contains only its own sessions - switching is not filtering, it is being somewhere else. Sessions from other environments appear neither in the sidebar nor in search, Ctrl+Tab, or the tiled views.
What to use them for
One project per environment. Thirty sessions from five projects in a single list stop being an overview. Groups still order things inside an environment, but they take nothing out of sight.
Creating and switching
From the environment bar along the top. Each one gets a name and an accent colour, so it is obvious at a glance which one you are working in.
Where membership lives
On the session itself, stored alongside everything else about it. Delete an environment and its sessions fall back to the default one - a running session never vanishes from every list.
Teams

Delegator, lead, workers, and guardian

A team is a process rather than a screen: one session writes the code, a second checks it, a third merges it. You say what needs building and read what came through at the end.

Delegator
The stage before the workers: one ask in, separate briefs out. The number you set is a ceiling and never a target, and coming back with a single job is a correct answer. What returns is a list you read, edit and prune, and the button says how many sessions it is about to open. Off by default, switched on per team.
Lead
A session you promote, or one started as a team lead straight from Plus. It sits on the integration branch, hands out the work, reviews what returns, merges and pushes. It needs a git repository and creates no branch of its own. Close it and its workers and guardians close with it, after asking.
Worker
One fresh session per task, each in its own git worktree on its own branch, so three workers can edit the same file without colliding. The rules for your repository go out with the briefing, the task box takes screenshots, files and dictation, and the branch name comes from a title a model reads out of the task.
Guardian
On by default. It reads the finished branch against your standards and sends back a numbered list: file, rule, fix. One to four rounds, then the branch reaches the lead anyway, marked NOT PASSED with the open findings attached. It may never edit, commit, push or merge, and there is exactly one route to the lead: through it.
Board
Five columns: Workers, Guardian, Lead, Done, and Needs you for anything that stopped. The column is derived from git and never stored, so cards cannot be dragged and a merge you did by hand moves the card anyway. A blocked card shows, per file, what your worker did to it and what landed on the base branch.
Summaries
Every role writes its own: a worker says what was asked for and what changed, a guardian what it read and what convinced it or what it objected to, a lead which branch landed and whether it is actually live. It sits on the card and at the bottom of the session that produced it.
Team setup
Seven pages: Overview, Delegator, Workers, Guardian, Integration, Deploy, and Prompts. Every team points at a profile of its own with its own standards, models, backends and way of shipping, so two projects never have to agree.
Briefings
The Prompts tab shows the exact text a worker, a lead and a report receive, rendered against a sample repository before a team even exists. Editable, with placeholders for repository, checkout, branch and task, with Reset, and with a rewrite from IXI that lands in the editor unsaved.

The whole run, slide by slide with diagrams and examples, is on the What's new page.

Models

Models, providers, and CLIs

IXIOM keeps session backends and agent providers separate on purpose. That lets you launch sessions while the IXI agent uses a different model in parallel.

Session backends
Claude Code, Codex, Gemini, Shell, Linux through WSL, and OpenClaw. Each backend exposes its own setup flow and quick model options.
Agent providers
Anthropic, OpenAI, Gemini, and Custom. Supported providers offer API-key entry and OAuth login, while Custom also supports your own base URL.
Visible model choices
Claude with Sonnet, Opus 4.6, Opus 1M, Opus 4.7, and Haiku. Codex with GPT-5.4, GPT-5.4 Mini, GPT-5.3 Codex, and Spark. Gemini with Auto, Flash, Flash Lite, and Pro.
Smart Helpers
In addition to the main model, IXIOM lets you choose a separate helper model for things like session naming and Image Studio prompt refinement.
Tooling

Agent, presets, and marketplace

Alongside the sessions themselves, IXIOM includes a second layer for reusable roles, quick commands, and publishable agents.

Agent workspace

Agent Chat opens as a right-side workspace with a memory browser, cron dashboard, health monitor, scripts manager, and search/debug view.

Presets and commands

Session presets, custom chat commands, and Shell or WSL startup profiles make repeatable setups fast to launch and easy to keep consistent.

Marketplace

Browse agents, filter by type, price, or tags, and publish your own listings with descriptions, tags, and a pricing model.

Custom providers

Add providers with your own base URL and API keys and use them in sessions exactly like any built-in backend.

Dashboard

Widgets and the fullscreen dashboard

The widget system is not decoration. It is the fast side layer for status, media, productivity, social features, and compact control.

Focus

Agent Chat, Notes, and Sessions keep conversations, scratch work, and active workstreams close at hand.

Insight

Claude Usage, Codex Usage, Productivity, Activity, Dream Log, Proactive, and Coordinator surface limits, progress, and background status.

Media

Media Player, Spotify, and YouTube cover generated audio plus embedded music and video inside the same workspace.

Social and game layer

Collab, Friends, and Buddy bring shared work, presence, challenges, and the companion system together in one place.

Agent ChatNotesLevel & XPBuddyClaude UsageCodex UsageProductivityActivityMedia PlayerCollabSessionsSpotifyYouTubeFriendsDream LogProactiveCoordinator
Shared work

Collab, Friends, and Buddy

IXIOM mixes live collaboration with social tooling and its own companion system. These parts work together, but they still stay clearly separated.

Collab

Host or join by code, choose guest permissions, share tasks in the board, and keep voice chat running with either VAD or push-to-talk.

Friends

Search users, manage requests, track presence, invite people into collab, and launch buddy duels from the widget itself.

Buddy

Buddy covers sanctuary, collection, equipment, battle, and upgrades, including feed, revive, monster encounters, XP, and Flux progression.

Studio

Image Studio

Image Studio brings IXIOM’s visible image features into one focused workflow. One half is built for generation, the other for clean background removal.

Image generation

Write a prompt, optionally attach a reference image, choose a style, and set the aspect ratio.

IXIOM refines the prompt before the actual image render starts.

Results stay inside the same view, can be copied, and can be passed straight into background removal.

Background removal

Upload an image and choose the right remove-background engine for the run.

Archive and output folders stay reachable from the same workflow.

Auto-save and auto-remove-after-generation can be controlled from settings.

BriaBiRefNetRemBG1:116:99:164:55:43:22:3
Control

Settings from Account through Features

Settings cover the full visible product surface, from profile controls to language, Image Studio, voice, and the advanced feature toggles.

Account

Profile, display name, plan status, and logout.

Terminal

Fonts, cursor, CLI backend, session mode, CLI paths, and startup presets.

Look

Avatars, language, wallpaper, UI scale, brightness, accent color, chat font, and themes.

Agent

Providers, API keys, OAuth, model selection, Smart Helpers, and persona.

Image Studio

Gemini key, fal.ai key, folders, default engine, BiRefNet model, and resolution.

Voice

Whisper or browser STT, ElevenLabs TTS, language, speed, and usage counters.

Features

Sound, buddy notifications, autoDream, Proactive Agent, Coordinator, and Telegram Gateway.

About

App info, changelog, and general orientation.

Keyboard

Work faster with keyboard shortcuts

IXIOM is clearly built with keyboard-first usage in mind. The main paths through sessions, panels, search, and layouts are directly reachable by shortcut.

Ctrl+T
New session
Ctrl+P
Command palette
Ctrl+B
Toggle sidebar
Ctrl+J
Toggle widget panel
Ctrl+Shift+J
Open fullscreen dashboard
Ctrl+Shift+T
Cycle main view
Ctrl+Shift+A
Toggle Agent Chat
Ctrl+Shift+C
Toggle Collab panel
Ctrl+Shift+F
Terminal search
Ctrl+Shift+1-5
Change layouts
FAQ

Frequently asked questions

If you just need the short answer for one part of the product, this is the fastest way to get it.

Do I need to use the same backend for every session?

No. Each new session can start with its own backend, and IXIOM keeps multiple live sessions open at the same time.

What is the difference between chat and terminal?

Chat is built for guided AI work with attachments, tool cards, and choice bars. Terminal shows the real CLI session with terminal input and terminal output.

Can I use my own models or endpoints?

Yes. The Agent area supports a custom provider with your own base URL and model name, and the built-in providers support API keys or OAuth where available.

What does Image Studio cover?

Image Studio bundles image generation, prompt refinement, reference images, aspect ratios, and background removal, including archive and output-folder handling.

Are Collab and Buddy separate systems?

Yes. Collab is for shared sessions, tasks, and voice. Buddy is the companion layer with collection, battles, upgrades, and friend duels.

Which providers and CLIs does IXIOM support?

Claude Code, OpenAI Codex, Google Gemini, Moonshot Kimi, xAI Grok, plus Shell, WSL Linux, OpenClaw, and custom providers with your own base URL and API keys.