Anything, anywhere, all as agent

Unix made the file the one abstraction for every resource. Kleinia makes the agent the basic unit of the system: applications, services, login sessions and system components all exist as agents, with one kind of identity, one way to describe what they can do, and one way to call them.

Managed from launch

Every program becomes a managed agent with its own identity and resource quota the moment it starts, without any change to the program. All agents appear together under /agent:

ls /agent/local

One address space

Every agent has an agent:// address. On this machine or another device, agents can discover and call one another:

agent://local/app/libreoffice
agent://local/system/network
agent://phone/device/camera
agent://server/app/build

Draft

In 0.1 addresses resolve locally only; calls to other devices arrive in a later release.

Collaboration by default

Applications never adapted for AI can still be called by other agents, through generic interfaces the system generates. How far a program becomes an agent depends on its interfaces:

Level	What the system does	What you get
Joins the system	Projects it as a managed agent	Identity, resource tier, usage accounting
Shares its abilities	Generates tools from MIME types, command-line help, D-Bus and MCP	Other agents can find and call it
Understands tasks	Adds a general agent on top of those tools	Traditional apps take natural-language tasks
Fully native	The app ships its own manifest	All of its abilities are exposed

Tool calls between agents use MCP, and any MCP client can reach the system’s agents through the system’s MCP server. See Run your agents.

Look and call

ls /agent/local                     # every agent on this machine
agentctl schema <agent> <skill>     # what a skill takes and returns
agentctl call <agent> <skill> '{…}' # call it

See the CLI reference.