Skip to content

Where people and agents ship software together. The open-source git platform for the whole job: issues, agents, checks and deploys to the edge.

g1t.sh
30 linesCodeBlameRaw

Pick any line to see why it is the way it is: the commit, the pull request and issue it came from, and what the agent was thinking.

Merge the runner sandbox: g1t-runner sandbox up makes a person's own computer a self-hosted runner that nothing a job runs can get out of. Linux jobs run in a Linux VM of the runner's own (a WSL 2 distribution with no host mounts, interop or Docker socket on Windows; vfkit on macOS; Sysbox, or QEMU and KVM, on Linux), each in a fresh container under Sysbox inside it; on Windows 11 Pro and up, Windows jobs each run in a Windows Sandbox discarded after the job. Runners report their isolation, and the Runners page shows it.1# The g1t sandbox's WSL settings (deploy/sandbox/Dockerfile). Everything
2# that reaches Windows from inside a WSL distribution is turned off here:
3# Windows drives are not mounted, Windows programs cannot be started from
4# Linux, and Windows' PATH is not added. `g1t-runner sandbox guest run`
5# checks that this file is exactly this before it starts, and refuses to
6# start if it is not (crates/runner/src/selfhosted/launcher/guest.rs).
7[automount]
8enabled = false
9mountFsTab = false
10
11[interop]
12enabled = false
13appendWindowsPath = false
14
15[boot]
16systemd = false
17
Merge main into rm-agents: mirroring removal, open signups, free-tier limits, the g1t CLI and runner fixes, with the agent removal kept. The CLI's table of operations is regenerated from the API without the agent, customize and AI credit operations; no CLI command used them.18# Every call the launcher makes names root itself (`wsl -u root`). Anything
19# else that opens the distribution, a `wsl -d g1t-sandbox` with no user or
20# Explorer at \\wsl.localhost\g1t-sandbox, gets this account instead: no
21# password, no shell, no home, and none of root's files (the Dockerfile).
Merge the runner sandbox: g1t-runner sandbox up makes a person's own computer a self-hosted runner that nothing a job runs can get out of. Linux jobs run in a Linux VM of the runner's own (a WSL 2 distribution with no host mounts, interop or Docker socket on Windows; vfkit on macOS; Sysbox, or QEMU and KVM, on Linux), each in a fresh container under Sysbox inside it; on Windows 11 Pro and up, Windows jobs each run in a Windows Sandbox discarded after the job. Runners report their isolation, and the Runners page shows it.22[user]
Merge main into rm-agents: mirroring removal, open signups, free-tier limits, the g1t CLI and runner fixes, with the agent removal kept. The CLI's table of operations is regenerated from the API without the agent, customize and AI credit operations; no CLI command used them.23default = sandbox
Merge the runner sandbox: g1t-runner sandbox up makes a person's own computer a self-hosted runner that nothing a job runs can get out of. Linux jobs run in a Linux VM of the runner's own (a WSL 2 distribution with no host mounts, interop or Docker socket on Windows; vfkit on macOS; Sysbox, or QEMU and KVM, on Linux), each in a fresh container under Sysbox inside it; on Windows 11 Pro and up, Windows jobs each run in a Windows Sandbox discarded after the job. Runners report their isolation, and the Runners page shows it.24
25# WSL's resolv.conf is a link into /mnt/wsl, which the sandbox unmounts:
26# the supervisor writes its own from what WSL offers at start.
27[network]
28hostname = g1t-sandbox
29generateHosts = true
30generateResolvConf = false

This file's history is long; its oldest lines are credited to the oldest commit read.