HOW IT WORKS

How ibara works.

ibara gives your agents computer use across the Omarchy machines you own. Three things work together: the computer you use, the spare your agent works on, and the agent itself. ibara connects them, decides who may do what, and shows you what’s happening.

Updated 29 September 2026

The pieces#

Your computer runs the ibara plugin in the Omarchy shell. It shows every computer you’ve connected and lets you watch, take control, hand back and move files. You can also wake, restart, sleep or lock any computer from it. Wake works when the computer turned on wake-on-network before it slept, or when another computer on its network can send the signal. When you open the console, While you were away shows one line of news per computer, and every message and approval appears in the bottom-right corner, over the page.
The spare runs the ibara service and Cua, which carries out every click and keystroke, in apps and in web pages. It runs your apps. It doesn’t run a model.
Your agent keeps running where it already does. ibara gives it a small set of tools to use the spare.
Your tailnet connects them. ibara opens no public internet listener.

Every computer runs the same ibara, so any of them can watch the others or be the one your agent works on.

Pairing#

You add each computer once, and no code is typed. Right-click the ibara mark in the bar to open the console, then choose Add Computer. It lists the computers on your tailnet. Add your own one at a time with Add, or every one that’s ready at once with Add Your 2 Computers (the button shows your own count). Someone else’s computer shows the same six-digit code on both screens, and a person there checks it and accepts. A computer with no screen accepts with ibara join. A request waits five minutes.

Your own computers get all five permissions, Administer included. Someone else’s computer gets Watch and Files; anything more is granted on purpose. A friend can also add yours with an invite code from Share This Computer. Access and data.

A task, step by step#

You ask your agent, naming the computer: “On spare-mini, check the settings menu…”
It checks what it may use with computer_status.
It starts a task with computer_begin, listing the checks it must pass. The spare gives it control, if nobody else is driving.
It looks and acts with computer_observe and computer_act. Cua moves the agent’s own named cursor, which shows its clicks, typing and key presses. You can watch the whole time.
It finishes with computer_finish: each check comes back passed or failed, what the task opened is cleaned up, and control is released.
You get the result in your agent: the report, screenshots and any files it delivered.

One driver at a time#

Only one person or agent can drive a desktop at once. Watching never takes control. When you take over, the agent’s input stops before yours starts; when you hand back, the spare becomes available again and no old agent session silently resumes. An agent loses control when its session sends no heartbeat for five minutes, or 30 seconds after it disconnects. A restart ends any agent’s control; the spare then resumes by itself once it’s healthy, unless a person paused it or its Resume agents after a restart setting is off.

What goes where#

Stays on the spare: the apps, browser profile and files your agent uses, and short-lived task replays.
To your computer: pictures of the screen while you watch, and a live video stream while you take control. With Live Video (Preview) on, the fleet wall and the Screen tab play live video instead of pictures.
To your agent: what it observes, and screenshots when it asks for them. Your agent may send these to its model provider.
To ibara: nothing. There’s no ibara cloud service and no telemetry.