In PowerShell. The script puts shako.exe in %LOCALAPPDATA%\shako\bin, adds that folder to your PATH, and needs no admin. ssh and scp come with Windows 10 and 11.
The new VM's name: a-z, 0-9 and single hyphens, starting with a letter, at most 31 characters. It is in the VM's SSH name and in the URLs of its public ports.
--size <size>
The size: small 1cpu/2G/16G disk, mid 2cpu/4G/32G disk, large 4cpu/8G/64G disk, xl 4cpu/16G/128G disk (default small).
--cpus <cpus>
Custom vCPUs: 1 or an even number. It replaces the vCPUs of the size.
--memory <memory>
Custom memory, for example 3G or 2560M. The disk is 8 GB per GB of memory. It replaces the memory of the size.
--image <image>
Image release, e.g. 2026.10.27.1 (default: the current release).
--sleep <sleep>
When the VM sleeps. auto: when it is quiet; never: it stays on, and restarts after a reboot or a crash. With both, shako vm sleep and shako vm wake work at once (default auto).
--idle <idle>
The quiet time before the VM sleeps, for example 15m or 2h (default 15m).
--no-wait
Return before the guest's SSH is up.
--agent <agent>
An AI agent or a coding agent to put in the VM: claude, codex, opencode, pi, kiro, openclaw, hermes. Give several with commas (--agent claude,codex) or with one --agent for each.
--desktop
Browser use and computer use for the agents: a screen and a shared browser. Needs an agent and 4 GB of memory or more (size mid or bigger).
--isolated
The key in the VM acts nowhere: no shako commands and no SSH to other VMs from the VM. SSH into the VM, the internet and its URLs still work.
--tenant <tenant>
The tenant, from shako tenant ls. You need it when you have more than one tenant. In a Shako VM, the default is the tenant of the VM.
Examples
Create a VM of the default size, Small.
$shakovmcreateweb1
A VM with Claude Code and Codex, and a screen and a shared browser for them. These need size Mid or bigger.
List the crons in a VM (cron and the schedulers of its agents) and its next wake. The box asks an awake VM now. A sleeping VM does not wake: the list is the one of its last sleep.
Usage
shakovmcrons<vm>[flags]
Parameters
<vm>
The VM's name, from shako vm ls.
--tenant <tenant>
The tenant, from shako tenant ls. You need it when you have more than one tenant. In a Shako VM, the default is the tenant of the VM.
Examples
List the crons in a VM: their source, schedule and next run, and when the box wakes the VM next.
Update Shako's own tools in a VM (shako-session, shako-wake) and its shako CLI to the build of main, over ssh. The files in the VM and the running sessions stay. New sessions use the new tools.
Usage
shakovmupdate<vm>[flags]
Parameters
<vm>
The VM's name, from shako vm ls.
--tenant <tenant>
The tenant, from shako tenant ls. You need it when you have more than one tenant. In a Shako VM, the default is the tenant of the VM.
Examples
Give a VM the newest Shako tools, for example the session status in the web workspace. Your files stay.
Change sleep policy, if crons and chat messages wake the VM, if the VM is isolated, and its backups.
Usage
shakovmset<vm>[flags]
Parameters
<vm>
The VM's name, from shako vm ls.
--sleep <sleep>
When the VM sleeps. auto: when it is quiet; never: it stays on, and restarts after a reboot or a crash. With both, shako vm sleep and shako vm wake work at once.
--idle <idle>
The quiet time before the VM sleeps, for example 15m or 2h.
--wake-on-cron <wake_on_cron>
On (the default): after each sleep, the VM wakes 2 minutes before its next cron job. off: it does not. On for a sleeping VM starts at its next sleep.
--wake-on-chat <wake_on_chat>
On or off: wake the VM when a chat message comes (default on).
--isolated <isolated>
On: the key in the VM acts nowhere: no shako commands and no SSH to other VMs from the VM. SSH into the VM, the internet and its URLs still work. off: the VM acts as you again. The change is at once, with no reboot.
--backup <backup>
On (the default): each night, Shako backs up the VM if its disk changed. off: no new backups, and the old backups go 7 days after they were taken.
--after-delete <after_delete>
What happens to the VM's backups when you delete the VM. keep-7d (the default): they stay 7 days, then Shako erases them. erase: Shako erases them within a few minutes. After an erase, the storage keeps the deleted data 7 more days, then deletes it.
--tenant <tenant>
The tenant, from shako tenant ls. You need it when you have more than one tenant. In a Shako VM, the default is the tenant of the VM.
Examples
Sleep after 30 quiet minutes.
$shakovmsetweb1--sleepauto--idle30m
A VM that never sleeps, for example for a bot or a server.
Copy a VM: a new VM whose disk starts as a copy-on-write copy of the source VM's disk. It gets the size, image and agents of the source VM, and boots with new SSH host keys.
Usage
shakovmcp<source><name>[flags]
Parameters
<source>
The VM to copy, from shako vm ls.
<name>
The new VM's name: a-z, 0-9 and single hyphens, starting with a letter, at most 31 characters. It is in the VM's SSH name and in the URLs of its public ports.
--sleep <sleep>
When the VM sleeps. auto: when it is quiet; never: it stays on, and restarts after a reboot or a crash. With both, shako vm sleep and shako vm wake work at once (default: the sleep policy of the source VM).
--idle <idle>
The quiet time before the VM sleeps, for example 15m or 2h (default: the quiet time of the source VM).
--no-wait
Return before the guest's SSH is up.
--isolated
The key in the VM acts nowhere: no shako commands and no SSH to other VMs from the VM. SSH into the VM, the internet and its URLs still work. The source must be isolated: its copy is isolated also without this flag.
--tenant <tenant>
The tenant, from shako tenant ls. You need it when you have more than one tenant. In a Shako VM, the default is the tenant of the VM.
Examples
Copy a VM, for example to try a risky change on the copy.
Awake and asleep hours, RAM GB-hours and cost per VM.
Usage
shakovmusage[flags]
Parameters
--range <range>
The time: this week (from Monday), this month, or all (default).
--vm <vm>
Only the VMs with this name, deleted ones too.
--days
Also the cost of each day, on this computer's clock.
--tenant <tenant>
The tenant, from shako tenant ls. You need it when you have more than one tenant. In a Shako VM, the default is the tenant of the VM.
Examples
The hours awake and asleep of each VM with usage, and its RAM GB-hours (memory times those hours), and its cost in US dollars. One row holds all the deleted VMs with one name. The most awake GB-hours come first, then the most asleep. Then the totals, with the total cost.
$shakovmusage
The cost of the VMs named web1 this month, deleted ones too, and of each day.
A backup is a copy of a VM's disk, kept outside its box. A restore puts the disk back to a backup, and the VM restarts. With backups on, Shako backs up the current disk first, so you can undo a restore. shako vm set --backup and --after-delete are the privacy settings of a VM.
List a VM's backups, newest first: the ID, the time on this computer's clock, the kind (nightly, manual or pre-restore) and the data that it added to the store. Then the backup or restore that runs now, or the last one if it failed.
Usage
shakobackupls<vm>[flags]
Parameters
<vm>
The VM's name, from shako vm ls.
--tenant <tenant>
The tenant, from shako tenant ls. You need it when you have more than one tenant. In a Shako VM, the default is the tenant of the VM.
Examples
List a VM's backups: the ID, the time, the kind and the data that each one added. Then the backup or restore that runs now.
Put a VM's disk back to one of its backups. The VM restarts, and the files that changed after the backup go back. Shako backs up the current disk first (kind pre-restore), so you can undo. With backups off for the VM (shako vm set --backup off), it does not, and you cannot undo. Without --yes, the CLI asks first.
Usage
shakobackuprestore<vm><id>[flags]
Parameters
<vm>
The VM's name, from shako vm ls.
<id>
The backup's ID, from shako backup ls.
--yes
Do not ask first.
--no-wait
Return at once. The restore goes on, and shako backup ls shows it.
--tenant <tenant>
The tenant, from shako tenant ls. You need it when you have more than one tenant. In a Shako VM, the default is the tenant of the VM.
Examples
Put a VM's disk back to a backup, with its ID from shako backup ls. The CLI asks first, and the VM restarts.
$shakobackuprestoreweb19f3c1a2e
Restore with no question, for example in a script.
$shakobackuprestoreweb19f3c1a2e--yes
Undo a restore: restore the pre-restore backup that it made of the disk of before.
Delete every backup of a VM now. You cannot undo this. The VM stays, and with backups on, the next night backs it up again. The storage keeps the deleted data 7 more days, then deletes it. Without --yes, the CLI asks first.
Usage
shakobackuperase<vm>[flags]
Parameters
<vm>
The VM's name, from shako vm ls.
--yes
Do not ask first.
--tenant <tenant>
The tenant, from shako tenant ls. You need it when you have more than one tenant. In a Shako VM, the default is the tenant of the VM.
Examples
Erase every backup of a VM now. The CLI asks first, and the VM stays. The storage deletes the last copies within 7 days.
$shakobackuperaseweb1
Stop the backups of a VM, then erase the old ones now with no question.
Share a port at a URL, on your private network or for the internet.
Usage
shakoportshare<vm><port><access>[flags]
Parameters
<vm>
The VM's name, from shako vm ls.
<port>
The port in the VM, 1 to 65535. A program must listen on it on 0.0.0.0, not 127.0.0.1.
<access>
Public: anyone on the internet can open https://<vm>-<port>--<tenant>.<apps domain>. private: only your devices can open https://<vm>-<port>--<tenant>.net.<apps domain>.
--tenant <tenant>
The tenant, from shako tenant ls. You need it when you have more than one tenant. In a Shako VM, the default is the tenant of the VM.
Examples
Share port 3000 at https://web1-3000--maya.shakoapp.dev. Anyone can open it.
$shakoportshareweb13000public
Share an admin page at https://auction-8080--maya.net.shakoapp.dev. Only your devices can open it.
A private port opens only on your devices, with no password, at https://<vm>-<port>--<tenant>.net.shakoapp.dev. Add this computer once. Its tunnel stays on, and it carries only the traffic to Shako.
Add this computer to your private network. It installs WireGuard if it is missing, and starts a tunnel that stays on, also after a reboot. It uses sudo.
Usage
shakodeviceadd[name][flags]
Parameters
[name]
The device's name (default: this computer's host name).
--tenant <tenant>
The tenant, from shako tenant ls. You need it when you have more than one tenant. In a Shako VM, the default is the tenant of the VM.
Examples
Add this computer to your private network, with its host name as the device's name.
$shakodeviceadd
Give the device a name, then share a port that only your devices can open.
Start a session with a name in a folder and attach to it. To leave the session running, close the terminal or type ~. at the start of a line (ssh's escape).
Usage
shakosessionnew<vm><session>[flags]
Parameters
<vm>
The VM's name, from shako vm ls.
<session>
The new session's name, for example api or fix-login. No other session of the VM may have it.
--agent <agent>
The agent to run: claude, codex, opencode, pi, kiro, openclaw, hermes. The VM must have it. Default: a shell.
--dir <dir>
The folder in the VM to start in, an absolute path (default /home/shako). It must exist, unless --mkdir.
--mkdir
Make the folder first (and the folders above it).
--tenant <tenant>
The tenant, from shako tenant ls. You need it when you have more than one tenant. In a Shako VM, the default is the tenant of the VM.
Examples
Start Claude Code in a new session api, in a new folder.
List a VM's sessions: the name, the agent, and the status of the program in it (working, blocked, done or idle). A shell, or a session from before shako vm update, has no status.
Usage
shakosessionls<vm>[flags]
Parameters
<vm>
The VM's name, from shako vm ls.
--tenant <tenant>
The tenant, from shako tenant ls. You need it when you have more than one tenant. In a Shako VM, the default is the tenant of the VM.
Examples
List the sessions of a VM and the status of each agent. The web workspace shows the same sessions.
Open the VM's build page (workspace.shako.dev/build) in this computer's browser. Only a VM with an agent has T3 Code.
Usage
shakobuildopen<vm>[flags]
Parameters
<vm>
The VM's name, from shako vm ls.
--no-browser
Only print the link.
--tenant <tenant>
The tenant, from shako tenant ls. You need it when you have more than one tenant. In a Shako VM, the default is the tenant of the VM.
Examples
Open T3 Code in the VM agents, in this computer's browser. Code with its agents there.
$shakobuildopenagents
Only print the link, for example to open it on another computer.
$shakobuildopenagents--no-browser
Agent Memory
Notes of up to 2000 tokens that Shako adds to each LLM request from your VMs, for every agent. While memory is on, each request from your VMs to a model provider goes through Shako. Your login goes to the provider unchanged, and Shako does not keep it. While memory is off, the requests go straight to the provider.
Stop adding the notes: the LLM requests from your VMs go straight to the providers.
Usage
shakomemoryoff[flags]
Parameters
--tenant <tenant>
The tenant, from shako tenant ls. You need it when you have more than one tenant. In a Shako VM, the default is the tenant of the VM.
Examples
Stop adding the notes. The text stays.
$shakomemoryoff
Turn the notes off for one test, then on again.
$shakomemoryoff&&shakomemoryon
Secrets
A secret, such as a GitHub token, that your VMs use but cannot read. Each VM gets a placeholder, and Shako puts the value in place of it in the requests to the hosts of the secret. The value never goes into a VM.
Add a secret or replace it. The value comes from the standard input, or else the CLI asks for it and does not show what you type. Each VM gets the variable NAME=shako-secret-NAME, and Shako puts the value in place of shako-secret-NAME in each request to the hosts. The value never goes into a VM.
Usage
shakosecretset<secret>--host<host>[flags]
Parameters
<secret>
The secret's name, also the name of the variable in your VMs, for example GH_TOKEN: A-Z, 0-9 and _, not first a digit, at most 64 characters.
--host <host>
Required. A host that gets the value: github.com or api.github.com. Give --host for each host.
--tenant <tenant>
The tenant, from shako tenant ls. You need it when you have more than one tenant. In a Shako VM, the default is the tenant of the VM.
Examples
Give your VMs the GitHub login of this computer. Then git clone, git push and gh work with your private repositories in each VM, and no VM has the token.
Save the PDF invoice of a month: each VM's usage and cost.
Usage
shakocreditinvoice[MONTH][flags]
Parameters
[MONTH]
The month, YYYY-MM (default: this month, on this computer's clock).
-o, --output <output>
The file to write (default: shako-invoice-<name>-<month>.pdf in this folder).
--tenant <tenant>
The tenant, from shako tenant ls. You need it when you have more than one tenant. In a Shako VM, the default is the tenant of the VM.
Examples
Save the PDF invoice of this month so far, in this folder.
$shakocreditinvoice
Save the invoice of October 2026 as oct.pdf.
$shakocreditinvoice2026-10-ooct.pdf
Tenants
A tenant has its own VMs, credit and invoices. You can own many tenants and share one with other accounts: each one accepts with the link of an email. With more than one tenant, a command that acts in a tenant needs --tenant.
Invite another account to a tenant: its VMs, ports, devices and agent memory. The account gets an email, and it is a member when it opens the link. It must have logged in to Shako once. Only the owner shares.
Usage
shakotenantshare<name><email>
Parameters
<name>
The tenant's name, from shako tenant ls.
<email>
The email of the account.
Examples
Invite a colleague to a tenant. They must have logged in to Shako once, and they accept with the link of the email.
$shakotenantshareacmebob@example.com
Invite an account, then show the accounts of the tenant: it is invited until it accepts.
Stop sharing a tenant with an account, or cancel its invite. Its VMs stay in the tenant, and their keys and its devices stop working there. Only the owner unshares. A member can leave: give your own email.
Usage
shakotenantunshare<name><email>
Parameters
<name>
The tenant's name, from shako tenant ls.
<email>
The email of the account.
Examples
Stop sharing a tenant with an account, or cancel its invite. Its VMs stay in the tenant.
$shakotenantunshareacmebob@example.com
Leave a tenant that another account shares with you.