Claude Code GUI: a desktop workflow with IXIOM

What you need before the first session

Install IXIOM for your operating system and architecture, then sign in to start the three-day trial. The download page lists the version available for each platform. A Windows release can be newer than the macOS or Linux build, so check the version beside your download.

Set up Claude Code using Anthropic's current installation and sign-in instructions. IXIOM needs to be able to launch that CLI. If you already use Claude Code in a terminal, confirm that the same installation and account work before bringing the session into IXIOM.

Start a Claude Code session

A useful first task is deliberately small: ask the agent to explain one part of a repository before letting it change files. This makes it easier to check that the session has the right project and that your CLI setup is working.

1. Choose a project environment

   Keep unrelated projects in separate environments. Give the session a descriptive name, such as Website: navigation, so you can recognize it in the sidebar later.

2. Create a session and select Claude Code

   Select the Claude Code backend and an available model. Model choices depend on the installed CLI, provider access and IXIOM version; use the choices shown by your installation.

3. Attach the repository and describe the outcome

   Use the repository integration to give the session its working context. State what should change, what should stay intact and which checks matter for the result.

4. Review the first result

   Check the proposed files and run the project's relevant checks. A completed agent response is the point to inspect the work, not proof that the feature works.

Use AI chat, terminals and split views

AI sessions present the conversation, attachments and tool results in chat. For direct terminal commands, open a Shell or WSL session. Available views depend on the backend; an AI chat does not universally switch into a terminal for that same agent session.

Split and tiled layouts keep several sessions visible. For example, leave a documentation session beside a coding session. The layout alone does not connect their conversations. For Claude and Codex, you can deliberately start a shared chat as an additional workflow.

Under Settings > Appearance, adjust the workspace design, Classic or Glassy look, fonts, chat, terminal, backgrounds and scaling. Use the options available in your installed version.

Use Codex and other backends alongside Claude

Choose the backend per session. Alongside Claude and Codex, IXIOM supports Antigravity, Kimi, Grok, Hermes and configured ACP agents such as OpenCode or Copilot. Availability depends on the installation and provider access. Older Gemini CLI sessions map to Antigravity; older OpenClaw sessions map to Claude. Gemini API capabilities, such as image features, are separate.

When several agents edit the same repository, use their assigned Git worktrees and branches. Define who owns which files and who checks the integrated result. The parallel-agent guide explains those handoffs in more detail.

Bring Claude and Codex into one shared chat

Choose Start collaboration or send a clear request such as “Bring Codex in”. Mentions, questions or quoted text alone do not activate the second agent. Address your next message to Claude, Codex or Together; with Together, the existing lead agent coordinates.

Both agents appear with their own sender identity in the timeline. They can hand off tasks, questions and answers. Generated images stay visible, and original file paths can be passed to the other agent. An agent’s available tools depend on its access and configuration.

With a repository attached, the partner gets its own worktree and branch. The lead coordinates integration and checks the combined result. End collaboration stops the partner and further handoffs. After restarting the app, collaboration stays off until you deliberately activate it again.

When the session does not start

First check whether the CLI starts outside IXIOM. Resolve provider sign-in errors, exhausted usage allowances or a missing executable at that layer. In IXIOM, check the backend, its CLI path under Appearance settings and the connected accounts. ACP agents have additional setup steps in the agent controls.

If the agent describes the wrong files, inspect the attached repository and the session's working directory before continuing. If a feature described in the docs is absent, compare your installed version with the platform version on the download page.

What the IXIOM subscription covers

IXIOM costs 19.99 EUR per month and offers a three-day trial without a credit card. It provides the desktop workspace and its features. It does not include a Claude, Codex or other provider subscription, and it does not remove the provider's usage limits.

Bring the provider access appropriate to the CLI you use. API usage may be billed by that provider. Hosted Image Studio credits are a separate offering. The pricing page explains the IXIOM trial and subscription.