Run Tego on a Mac or Windows PC
Tego only runs on Linux, so on a Mac you run it inside a small Linux VM made with Lima, and on Windows inside WSL2. Your agent runs there too, and one command sets each up.
Tego's Mac VM has booted on an Apple silicon Mac with Lima 2.3, but the Mac path is not fully tested yet, and nobody on the project has run the Windows setup on a real PC. This post says plainly which parts are unproven. The docs for macOS and Windows are the reference.
Why Linux?
Tego runs an AI agent under rules you write, enforced by the Linux kernel and Tego's supervisor, a process outside the agent. The kernel parts are Linux features: Landlock and seccomp at the Basic protection level, which needs no root, and BPF programs at Plus and Max, which need root. There is no macOS or Windows backend.
Tego governs processes on the kernel it runs on, so the agent has to run inside the VM too. You set up the VM yourself.
What a VM gives you on its own
A VM is already a boundary. Lima's AI agents page says it helps "to prevent agents from directly reading, writing, or executing the host files", and recommends mounting only your project folder. It rates a host mount "Lower" safety and its sync mode (Lima 2.1 or later), which reviews changes before they reach the Mac, "Higher".
WSL2 is built for working across Windows and Linux, so it shares more. Microsoft's WSL settings page lists, as defaults, your Windows drives mounted under /mnt (so C:\ is /mnt/c) and interop that lets Linux start Windows programs.
Inside either one, Tego adds a contract for the agent: the files it may write, the programs it may run, the hosts it may reach, actions held until you answer, and a record of each run. It doesn't hide the machine. The agent can read any path not in deny_read, which in WSL2 includes your Windows drives.
On a Mac: Lima
brew install lima
limactl start --name=tego https://github.com/Attention-Span-AI/Tego/releases/latest/download/tego.yaml
limactl shell tego tego doctorThese lines install Lima (2.0 or later), start an Ubuntu 24.04 VM named tego with Tego inside, and check it. That VM gives Basic, Plus with sudo, and Max after a GRUB boot line. Tego's support table says Lima's Fedora template gives all three levels with no edit; you install Tego in it with the Linux installer.
As written, the VM mounts your Mac home read-only. Tego's built-in list of secret files names paths in the VM's home, so it doesn't cover your Mac's /Users/<you>/.ssh. To share less, start the VM with --mount-none and keep projects on the VM's own disk (choose what the VM can see). On a Mac, keep the project inside Tego's VM; a folder shared from the Mac can't be used.
If the cgroup check fails, run systemd-run --user --scope bash in the VM first, then tego doctor again.
On Windows: WSL2
In PowerShell opened as administrator:
wsl --install -d Ubuntu-24.04Microsoft's install guide says this needs Windows 10 version 2004 or later (build 19041) or Windows 11. Restart if asked, open Ubuntu, then install and check Tego:
curl -fsSL https://github.com/Attention-Span-AI/Tego/releases/latest/download/install.sh | sh
tego doctor
tego testYour distribution must run as WSL 2 (wsl -l -v shows it), because a WSL 1 distribution runs no Linux kernel. The Basic level also needs systemd running: if ps -p 1 -o comm= doesn't print systemd, add [boot] and systemd=true to /etc/wsl.conf and run wsl --shutdown. We haven't tested whether that is all Basic needs.
The kernel decides your level. On WSL's 6.18 kernel you get Landlock ABI 7. On older 6.6 installs you get ABI 3, which has no TCP port rules, so Tego's supervisor alone decides each connection. Run wsl --update first.
Two WSL defaults reach past Linux. Add your Windows paths, such as /mnt/c/Users/<you>/.ssh, to the contract's deny_read, and give every contract an exec: allow list so it refuses Windows programs started through interop.
Max in WSL2
Max needs root and bpf in the kernel's boot list of security modules. Microsoft's WSL kernel lists bpf by default from 6.18.54.1, shipped in WSL 3.0.3 on 9 October 2026 (kernel releases). After wsl --update, check cat /sys/kernel/security/lsm: if it lists bpf, there's nothing to change. Nobody has run Tego on that kernel yet.
On an older kernel, sudo "$(command -v tego)" doctor prints the fix for GRUB, which WSL2 doesn't have. Put the same lsm= list in %UserProfile%\.wslconfig instead:
[wsl2]
kernelCommandLine = lsm=<the list tego doctor printed>Run wsl --shutdown, reopen the distribution and check that the list includes bpf. Don't copy an lsm= line from elsewhere: it replaces the whole list. Protection levels explains each one.
Where the agent and its tools run
Inside the VM. Install the agent, its runtimes and its tools in the Lima VM or the WSL2 distribution, and sign in there. Then follow Run Claude Code and Codex under Tego, or write a contract for any other agent.
A tool you run on the Mac itself is outside the kernel Tego governs, and so is a Windows program started through interop. If your workflow needs macOS-native tools, Tego can't cover them today.
The dashboard runs in the VM and answers only connections from the user who started it, so a port that Lima or WSL forwards may be refused. On a Mac, forward it over SSH: ssh -F ~/.lima/tego/ssh.config -N -L 8484:127.0.0.1:8484 lima-tego. Neither route has been tested; tego receipt --last always works in the terminal.
What hasn't been tested yet
- The project's VM test matrix runs Ubuntu 24.04, Debian 13, RHEL 9, Amazon Linux 2023 and Fedora. It has no WSL or macOS job.
- The support table was verified on 2026-09-21, and its WSL2 and Lima rows aren't backed by continuous tests.
- Whether systemd gives your user a delegated cgroup in WSL2.
- Opening the dashboard from a Mac or Windows browser.
If you run Tego on either system, a bug report on the repository with your tego version and tego doctor output helps the next person. To build Tego by hand in the VM instead, see Build from source.
Other options on macOS and Windows
As of 2 November 2026:
- Claude Code's sandboxed Bash tool uses Seatbelt on macOS and bubblewrap on Linux and WSL2. On native Windows, Claude Code runs commands unsandboxed, and Anthropic says to use WSL2 for the sandbox (Sandboxing).
- Codex uses Seatbelt on macOS, a native Windows sandbox in PowerShell, and its Linux sandbox in WSL2 (Codex sandbox docs).
- Docker Sandboxes run AI coding agents "in isolated environments on your machine or on Docker-managed cloud infrastructure" (Docker docs).
- A plain VM, as Lima's page describes, with no Tego inside.
Five ways to sandbox an AI agent compares them with sources, and the Tego FAQ answers the short questions.
Sources (15 links)
Checked on 2 November 2026; Tego's Lima file and WSL kernel details on 6 November.
- Lima: AI agents, templates, limactl start.
- Microsoft: Install WSL, Advanced settings configuration in WSL, WSL kernel releases.
- Go: Download and install.
- Anthropic: Sandboxing. OpenAI: Codex sandbox. Docker: Docker Sandboxes.
- Tego: ARCHITECTURE.md, sections 13 and 14, TIERS.md, INSTALL.md, test/README.md, examples/lima/tego.yaml.
Read next
Five ways to sandbox an AI agent
Sandboxes, containers, VMs and Tego, compared.
An agent deleted production in nine seconds
Strict rules refuse key steps
Codex, under rules it can't turn off
Run Codex under rules it can't switch off.