Skip to main content
The Computer is a sandboxed container the agent can actually work in. It writes the code, installs what it needs, runs a build, and serves the result at a live URL you can open. Nothing runs on your laptop and nothing is left behind on it. It is attached to a chat. Ask for something in that chat and the agent uses the machine to deliver it rather than handing you a file to run yourself.

​
What it can do

Install packages, scaffold with a framework CLI, run builds and tests, read and write files, and start a preview server that stays up at its own address. bun, node, npm, git, curl, openssl and python3 are available. Routine steps run without asking: reading and writing files, installing from the lockfile, running the project’s own scripts and local git. Anything else waits for your approval in the chat, and Add to allow list remembers that command for the project. Commands that reach the network, such as curl, wget or git push, or that read environment variables or credential files, ask every time and cannot be added to the allow list. Previews are private by default. You choose whether a project stays private, is visible to your workspace, is public, or sits behind a password.

​
One size

Every project gets the same machine: 2 GB of memory, sized for a real development server. There is nothing to pick and nothing to approve halfway through a build. If a command does run out of memory the agent tells you and retries with a smaller step. It will not ask you to pay for a bigger machine, because there is no bigger machine.

​
What it costs

Two things are metered, and only while the machine is awake. Those are the units. What they come to in practice: Starting a project costs nothing. Storing one costs nothing. The machine sleeps three minutes after the last thing that touched it, and the meter stops when it sleeps, so a project that exists but is not in use is free. A wake is billed for at least one minute of memory, which on a 2 GB machine is EUR 0.0003. Processor time is billed as measured with no minimum.

​
The off peak rate

Between 00:00 and 08:00 UTC the processor rate is a quarter lower. That is the whole of it: fixed hours, in UTC, published in advance, and the same for everybody. Memory is never discounted and never surcharged. Leaving a preview awake overnight costs exactly what leaving it awake at midday costs, because the discount applies to work you can choose to move, not to a machine sitting still. The rate on this page is the highest rate there is. Nothing is ever billed above it.

​
Nothing arrives as an invoice

Credits are prepaid inside your plan. The meter can only spend credits you already have, so there is no bill after the fact and no overage to opt out of. When the balance runs out the current session finishes and then the machine sleeps; the next start is refused until you top up. See Credits for the balance itself and everything else that draws from it.

​
Limits by plan

Hours of building is your plan’s credits divided by a modelled building hour, so it is an estimate rather than an allowance. Credits also pay for search, page reads and research, so spending them elsewhere leaves fewer Computer hours. A session is how long one run can last before the machine stops on its own. The Computer is not part of the free plan.

​
When the host is full

There is a fixed amount of memory across every project running at once, so a start can arrive when there is no room for it. When that happens the request waits rather than failing immediately. It holds a place in order and starts as soon as another project sleeps, which usually happens within the three minute idle timeout. If no room appears within twenty seconds it gives up and tells you the machine is at capacity, so a refusal is never slower than that. A project already running is never stopped to make room for somebody else’s, and that includes your own. If you are at your plan’s concurrent limit, starting another one is refused and the message names the project you need to stop first.

​
How long a preview runs

A preview keeps running for up to 30 minutes after the last time you or the agent worked on it. Pro is the same, Max is an hour and Enterprise is two hours. Working on it is what extends that. A command, a file write, a build, an edit in the editor: each one starts the clock again, so a long build is never cut off part way through. Visitors do not extend it. Someone opening your shared link keeps the machine awake, which is what stops it sleeping mid visit, but it does not push the limit back. So a preview nobody is working on stops 30 minutes after you last touched it, however much traffic it is getting. That is deliberate. The Computer is a preview of something you are building, not somewhere to host it, and a link that stays up on its own for weeks is the shape of hosting.

​
Keeping one awake anyway

If you do want a preview to stay up, Publish has a switch below who can open it. Always awake exempts the project from both the sleep timer and the session limit, and it runs until you turn it off or your credits run out. The dialog shows what that costs before you save: about EUR 0.02 an hour, and how long your current balance covers at that rate. Two things it uses up. It holds one of your plan’s running projects for as long as it is on, so on Starter you cannot start a second project while it runs. And it spends credits the whole time, because the meter does not care why the machine is awake. Previews are never indexed by search engines whether or not this is on.

​
Project memory

The agent keeps short private notes about each project, such as what it built, bugs and their real causes, and decisions you made, and reads them before it starts work in a later chat. The notes are stored in your Nemu account, not on the machine, so they survive the project being moved or the host being replaced. Computer reads only its own notes for that project. To let it also read the notes your coding agents saved on your own machines, share a Context project with it in the console under Context, Share with Computer. Sharing is read only and can be undone. See Privacy and control.

​
Getting started

Open a chat, ask for something that needs to run, and the agent creates the project on its own. There is no setup step and nothing to install.
Related: Prompting for getting more out of the agent.