ibara
Install ibara

CODEX

Computer use for Codex on Omarchy.

ibara gives Codex computer use across the Omarchy machines you own. Codex 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

Codex on Linux#

OpenAI’s Computer Use for Codex runs in the ChatGPT desktop app on macOS and Windows. OpenAI’s Linux preview doesn’t include it yet (Computer Use, the Linux app, September 2026). On Omarchy, ibara gives Codex computer use through MCP. Computer use on Linux, by agent.

It also works differently. Codex’s Computer Use drives the computer you’re sitting at. ibara gives Codex 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 Codex#

In the ibara console, choose Connect an Agent in the fleet’s toolbar, then Copy Prompt, and paste it into Codex. Codex 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:

codex mcp add ibara -- ibara mcp

Codex saves it as [mcp_servers.ibara] in ~/.codex/config.toml, which the Codex CLI, the IDE extension and the ChatGPT desktop app share. Codex’s MCP docs. The skill link and the note in the full prompt tell Codex 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 app you just changed, try the new signup form with a bad email and a good one, and tell me what each shows.” 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 Codex 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), Codex connected itself from the pasted prompt and finished its task on a test computer. Test results.

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