ibara
Install ibara

GLOSSARY

Glossary.

The words you’ll see in ibara and these docs, in plain terms.

Updated

Agent identity
How ibara names an agent: agent@computer, the agent and the computer it connects from, such as claude@your-laptop for Claude Code or codex@your-laptop for Codex. Used in permissions and in the record of who did what.
Always Allow
An answer to an approval that lets that agent take that kind of step on that computer without asking again. Undo it in the computer’s Access tab.
Approval
A person’s yes to one step an agent wants to take, such as sending, spending or deleting. It covers that exact step only. You can turn approvals off for your own computers’ agents; how.
Check
Something a task must prove before it finishes, like “the submenu opens with Enter”. Each check comes back passed or failed.
Computer use
An agent using a computer the way a person does: it sees the screen and works the mouse and keyboard in the browser and apps. ibara gives your agents computer use on Omarchy computers you own.
Console
ibara’s window in Omarchy, opened by right-clicking the ibara mark in the bar, where you see and use every computer you’ve added.
Cua
The open-source computer-use engine ibara is built on. It performs every click and keystroke, in apps and in web pages. Built on Cua.
Fleet wall
The page ibara’s console opens on in Omarchy: every computer you’ve added as a card, with a recent picture of its screen, its state and who’s using it.
Grant
A permission a computer gives a person or agent. There are five: Watch, Files, Take Control, Agent Tasks and Administer, each Allowed, Ask First or Denied. No grant means no access.
Hand back
Ending your control of a computer so it’s available again. It never restarts an old agent session.
Invite code
A single-use code, such as 4H7K-92QX, made with Share This Computer. A friend’s computer that uses it is added at once with the level you chose (Watch, Use with Approval or Take Control) until it runs out or you revoke it. It never grants Administer.
Lease
Control of a desktop, held by one person or agent at a time. An agent’s session sends a heartbeat every 30 seconds while it’s connected; its lease ends after five minutes without one, or 30 seconds after it disconnects.
MCP tools
The tools ibara gives your agent, such as computer_begin and computer_act. Full list.
Pairing
Adding a computer once, from Add Computer in the console. Your own computers on your tailnet are added with Add, or all the ready ones at once with Add Your 2 Computers (with your own count), with no code. Someone else’s computer shows the same six-digit code on both screens, and a person there has five minutes to accept; a computer with no screen accepts with ibara join.
Pause
Pause Agents, in the console, stops all agent input on a computer immediately. A person’s pause lasts until someone chooses Resume. After a restart, a computer resumes by itself once it’s healthy, unless its Resume agents after a restart setting is off.
Registered machine
A spare computer someone has added to the public list, reviewed before it appears.
Spare
The computer your agent works on. It runs Omarchy, your apps, the ibara service and Cua, but no model.
Tailnet
Your private Tailscale network. ibara connects computers over it and opens nothing to the public internet.
Take control
Taking over a computer from whoever is driving it. The agent’s input stops before yours begins.
Task
One piece of agent work on one computer, from computer_begin to computer_finish.
Tested hardware
Machines ibara is developed and tested on, with published specs and results. Tested hardware.
Watch
Seeing a computer’s screen without taking control. The agent keeps working.