Computer sessions

Your agent can open a throwaway cloud computer to run a script, convert a file or work a website that has no API — here is what it can and cannot do with it, and how to stop it.

Most of what your agent does happens through Kaizendex's own tools: reading your entries, searching the web, fetching a page, saving a link. Some jobs need a real computer — turning a spreadsheet into a chart, converting a file format, running a script over a dataset, or clicking through a website that offers no other way in. For those, your agent can open a computer session: a small, throwaway Linux machine in the cloud that exists only for that task.

What your agent can do with one

Run commands — one at a time, each with a time limit (up to 5 minutes).
Use an isolated browser — open an allowed website, read its interactive elements, click a control, fill a field, and save a screenshot as an attachment. This needs the deployment's browser setup; it never uses your personal Chrome session. Pages are treated as information, not instructions for the agent.
Send files in and fetch files out. A fetched file is saved as one of your attachments, exactly like a file you upload yourself, so it stays with you after the machine is gone. Files up to 5 MB each.
Reach the internet only where it said it would. When the agent opens a session it names the exact websites the machine may talk to; everything else is blocked. A session opened with no sites has no internet at all.

What it cannot do

See or change your Kaizendex data. The machine has no access to your account or the database. If the agent wants to save a result — a number, a page, a file — it fetches the file out and saves it with its ordinary tools, the same audited path every edit takes.
Live long. A session lasts at most 30 minutes (usually 10) and then switches itself off. You can have 2 running at once and 120 minutes of computer time per day.
Keep secrets. Nothing from your account is copied onto the machine.

Everything is written down

Every session records why it was opened (the agent states its purpose in one line), when it started and expires, which websites it was allowed to reach, every command it ran with the result, every file that went in or out, and the resource usage the provider reports. Dollar cost is currently unavailable; these usage readings are not charged against your AI credits. Unavailable cost does not mean the cloud provider runs the machine for free. Computer actions in chat show a computer session panel. Choose Show activity to inspect the commands and results, Show details for the full recorded result, and Show more activity for older pages. Saved files open by filename in the image viewer or full file reader. Refresh checks the latest state; active sessions also refresh in the background. These controls are the same on desktop and phone.

Take control of the browser

Choose Take control in a live computer's panel. The current operation finishes before your browser controls appear. Website address and Go open an allowed site. Refresh page targets lists the page's interactive controls by name; choose Click or Enter text beside a field. Replace field text replaces its value and clears the temporary input. Save screenshot creates a file you can open in the usual viewer. Return control lets the agent continue. These options are the same on web, desktop and phone.

Takeover needs a fresh browser-only computer. Computers that allowed shell commands or file writes explain why takeover is unavailable. If an operation cannot be confirmed, stop that computer and ask the agent to open a fresh one. A control request does not grant input until the server confirms that it is safe.

Human controls may say they are not enabled while a deployment is being updated. You can still stop the computer. Typed text and navigation addresses are omitted from the action history; browser pages shown during human control are temporary views unless you choose to save a screenshot.

If the machine disappears

Cloud machines can vanish mid-task. When that happens your agent is told plainly: the session is marked lost, the files it already fetched are kept, and it opens a fresh session to finish the unfinished part — it will not tell you the job is done when it is not.

How to stop it

Choose Stop computer in its chat panel, or say "stop the computer" (or "stop that session") in chat. The panel updates immediately; if the stop request fails, the previous controls return with an explanation. Ending the conversation does not stop a session by itself, but every session stops on its own when its time is up.