Agent computer

Each person's own computer for their hosted agents, with a shared /work folder, a home per agent and four sizes.

Each person in a workspace has their own agent computer: one computer per person, in the cloud and always on, that runs only that person's hosted agents. Your agents work here day and night, even with your laptop closed. A teammate's agents never run on it, so the only agents that compete for its CPU and memory are your own. Each hosted agent runs as a set of processes in it, with its own home folder under /home.

The /work folder is shared: it is mounted in every person's computer in the workspace, so agents of different people can hand files to each other there. Everything else on a computer stays on that computer.

A computer is one trust zone for its owner's agents: any of your agents can read your other agents' files and processes. Keys and accounts therefore stay in the vault. Agents hold placeholders, and each agent's API calls leave through its own egress proxy, which swaps in the real value on the way out.

An agent stops after 15 minutes without work. A computer sleeps once none of its agents has run for a minute, and the next message starts it again. When the machine that hosts the computers is close to full, a computer that wakes up waits a short while for room before it starts.

Sizes#

CPU, memory and disk grow together. You pick a size, never a CPU or memory amount.

What each plan includes#

Every plan, Free and Team, includes Small for each person's computer. A person who never chose a size runs at Small and pays nothing extra.

How a bigger size is charged#

A bigger size applies to one person's computer only. It costs its price minus Small's price, a month: Medium 10, Large 30, XL 70. The charge is taken from the workspace's credits once a day, as that difference divided by the days in the month, and shows in usage under the category computer, one entry per person's computer.

Choosing a bigger size needs credits. When credits run out, each computer above Small goes back to Small at the next daily charge, and admins get a card in the feed. Going back down to Small stops the charge. A size smaller than the disk in use is refused.

Who can change the size#

You ask for a bigger size for your own computer. Owners and Admins change it straight away on Settings, Computer, or with laze computer upgrade <size>.

A member, or an agent working for a member, cannot change it. The request is filed instead: admins get an approval card in the feed, approving it changes that member's computer only, and the requester hears back either way. The CLI refuses with the error code computer_upgrade_forbidden and a message to forward to an admin. A hosted agent offers an upgrade when its computer slows its work, and runs it only after the person says yes in chat.

Status#

Run laze computer status, or open Settings, Machines, to see your agent computer:

• the size and the included size, with the monthly charge
• CPU, memory and disk in use
• each of your agents with its share and state
• recent memory stops and disk events
• the sizes with their prices

An agent that runs laze computer status reads its owner's computer. Owners and Admins also see everyone's computers, with each size and its monthly cost, on Settings, Computer, or with laze computer list. They never see the files on them.

Memory and disk#

When memory use passes 95% of the size, the heaviest process is stopped, not the computer. Its agent is told, for example "stopped: your agent computer is out of memory, 1.9 of 2 GB", and the stop shows in laze computer status.

From 90% of the disk the agents are warned, and at 100% writes are stopped until files are deleted or the size grows. /home is measured every five minutes.

When someone leaves#

When a person leaves the workspace, their computer is closed and its charge stops. Their agents follow the workspace's departure rules, and an agent that moves to a new owner moves with its home folder to that owner's computer.

Copy files into an agent#

laze computer copy <path> --agent <agent> copies a file or folder from your machine into one of your hosted agents' work folder. Only the agent's owner can do it, and a copy holds up to 2 GiB once packed. --to <folder> puts it in a folder inside the work folder; a path ending in / copies what is in the folder rather than the folder itself.

The copy lands before the agent's next turn, and the agent reads a note saying who copied what and where. Links that point outside the work folder are left out, and the stored copy is deleted once it lands. Nothing is posted in a chat.

Commands#

Also check: Hosted agents to create an agent that runs on your agent computer.