ibara
Install ibara

CLAUDE CODE

Computer use for Claude Code on Omarchy.

ibara gives Claude Code computer use across the Omarchy machines you own. Claude Code keeps running where you use it; ibara gives it a spare computer’s desktop, browser and apps to work in, while you keep working on yours.

Updated

Claude Code on Linux#

Claude Code’s own computer use is a research preview on macOS in the CLI, and on macOS and Windows in the desktop app. Anthropic’s docs say it isn’t available on Linux (computer use in the CLI, the Linux desktop app, September 2026). Omarchy is Arch Linux, so ibara adds computer use through MCP. Computer use on Linux, by agent.

It also works differently. Built-in computer use drives the screen you’re sitting at. ibara gives Claude Code a computer of its own: its clicks and keystrokes land on the spare, so they never take your cursor or focus. Your agent works there. You keep working here.

Connect Claude Code#

In the ibara console, choose Connect an Agent in the fleet’s toolbar, then Copy Prompt, and paste it into Claude Code. Claude Code adds the ibara server to its own MCP settings, links the ibara skill into its skills folder and adds a short ibara note to its instructions file, then tells you which computers it can use. On a computer without the console, ibara prompt prints the same prompt.

To add the server yourself instead, register ibara as a local MCP server for all your projects:

claude mcp add --scope user ibara -- ibara mcp

Leave out --scope user to add it to the current project only. Claude Code’s MCP docs. The skill link and the note in the full prompt tell Claude Code when to reach for ibara; without them it still has the tools.

Give it a task#

Ask as usual and name the computer. Start with the practice page, which needs no login and changes nothing:

On spare-mini, open https://ibara.app/practice and check the Settings menu with the mouse and the keyboard. Take a screenshot and tell me what worked. Don’t change system settings.

Then give it the work you’d otherwise check by hand: “On spare-mini, open the staging dashboard, change the notification settings, reload, and check they stuck.” Claude Code sees the screenshots ibara returns right in the conversation, and each step comes back checked. Steps ibara recognizes as sending, spending, deleting or changing access wait for your approval, unless you’ve turned approvals off for your own computers.

Watch the spare from the ibara console, Take Control at any point, then Hand Back.

What Claude Code gets#

The same eleven tools as every agent: the fleet’s status, starting a task, reading the screen, the mouse and keyboard, the browser, commands, waiting, files, checkpoints, procedures and a checked finish. The tools.

In acceptance testing on 27 September (ibara 0.1.0-8, with that build’s prompt), Claude Code connected itself from the pasted prompt and finished its task on a test computer. Test results.

Give each Claude Code session its own computer and they work side by side.