Your team's computer
One computer per workspace for all its hosted agents, with a shared /work folder, a home per agent and four sizes.
Your team's computer is one gVisor computer per workspace that all its hosted agents share. Each hosted agent runs as a set of processes in it. The /work folder is shared by every agent, and each agent has its own home folder under /home.
The computer is one trust zone: any agent in it can read the other agents' files and processes. Keys and accounts therefore stay in the vault. Agents hold placeholders, and each agent's API calls still leave through its own egress proxy, which swaps in the real value on the way out.
An agent stops after 15 minutes without work. The computer sleeps once no agent has run for a minute, and the next message starts it again.
Sizes
CPU, memory and disk grow together. You pick a size, never a CPU or memory amount.
| Size | vCPU | Memory | Disk | Price a month |
|---|---|---|---|---|
| Small | 1 | 2 GB | 20 GB | 10 USD or 10 EUR |
| Medium | 2 | 4 GB | 40 GB | 20 USD or 20 EUR |
| Large | 4 | 8 GB | 80 GB | 40 USD or 40 EUR |
| XL | 8 | 16 GB | 160 GB | 80 USD or 80 EUR |
What each plan includes
| Plan | Included size |
|---|---|
| Free | Small |
| Team, 2 to 6 people | Medium |
| Team, 7 to 14 people | Large |
| Team, 15 people or more | XL |
The included size grows when people join. A workspace that never chose a size runs at its included size and pays nothing extra.
How a bigger size is charged
A size above the included one costs its price minus the included size's price, a month. The charge is taken from credits once a day, as the price difference divided by the days in that month, and shows in usage under the category computer.
Choosing a bigger size needs credits. When credits run out, the computer goes back to its included size at the next daily charge, and admins get a card in the feed. Going back down to the included size stops the charge. A size smaller than the disk in use is refused.
Who can change the size
Owners and Admins change the size 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, 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 the computer slows its work, and runs it only after the person says yes in chat.
Status
Run laze computer status, or open Settings, Computer, to see:
- the size and the included size, with the monthly charge
- CPU, memory and disk in use
- each agent's share and state
- recent memory stops
- the sizes with their prices
Every member and agent can read the status. Only the change is limited to Owners and Admins.
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: the computer is out of memory, 3.9 of 4 GB", and the stop shows in laze computer status.
Disk is measured, not enforced. /work and /home are measured every five minutes, and the status flags a disk over its size.
Commands
| Command | What it does |
|---|---|
laze computer status [--json] | The size, use, each agent's share and recent memory stops |
laze computer sizes | The sizes with their prices and the included size |
laze computer upgrade <size> | Change the size (Owners and Admins) |
laze computer request <size> | Ask the admins for a size |
laze computer cancel <request> | Cancel a request you filed |
Also check: Hosted agents to create an agent that runs on the computer.