Skip to content

⌘K

Explore Download Docs

flagon-io/g1t

public

Overview Code Issues Pull requests Workflows Deployments Insights

Files Commits Branches Tags Releases Compare

g1t/scripts

syntaqxThe lockfile has the telemetry service in it. Observability added services/telemetry as a workspace package (@g1t/telemetry) without it, so npm ci refused to install and Deploy 212 stopped at its first step.d21288dyesterdayHistory

..
deploy
emoji
ops
perf
build-runner.mjs
build-rust-worker.mjs
cli-release.mjs
cloudflare-setup.py
conformance-diff.mjs
deploy.mjs
deploy.sh
desktop-release.mjs
desktop-release.test.mjs
mobile-release.mjs
mobile-release.test.mjs
runner-release.mjs
runner-release.test.mjs
sandbox-image.mjs
sccache.sh
setup-custom-domains.sh
setup-deployments.sh

Where your team and its coding agents ship code.

Product

Explore
Pricing
Download
Chat
Bring your own agent
Integrations

Developers

Documentation
API reference
MCP tools
llms.txt

Company

Flagon, Inc.
Support
Security
Status

Open source

Source on g1t
MIT license
Run g1t yourself

g1t is designed, built, and backed by Flagon, Inc., a small, independent software company founded by Chase Pierce.

Checking statusStatus
Support
Policies
Privacy
Security

·

Sign in
© 2026 Flagon, Inc. All rights reserved.

..
deployThe deploy's stages ride out a dropped npm connection as CI does. Each core, edge and front job keeps npm's downloads between runs (actions/cache on ~/.npm, keyed on the lockfile), and the deploy tool's install reads them first (npm ci --prefer-offline), so a registry connection reset mid-install no longer fails a stage, as it failed the web stage of Deploy 201.yesterday
emojiMerge the workspace shell: navigation and phone shell, g1t as orchestrator, agents in roles with audience-checked reads, reactions and custom emoji, live notifications and browser push, the homepage tour (agents 0002, chat 0002)4d ago
opsMerge remote-tracking branch 'origin/claude/cool-newton-7nm8r9' into claude/cool-newton-7nm8r9yesterday
perfThe docs folder is gone, and what it held lives where people read it: how a self-hosted g1t runs and how to deploy g1t to Cloudflare are pages on docs.g1t.sh under Run g1t yourself, and speed, rate limits and operating g1t.sh are sections of CONTRIBUTING.md; code that cited a file in docs/ now points to the page or section that covers it, or says what it means itself, and applied migrations and the runner images are left as they were.3d ago
build-runner.mjsFast pages, required checks on the branch, self-hosted runners, honest incidents1w ago
build-rust-worker.mjsThe docs folder is gone, and what it held lives where people read it: how a self-hosted g1t runs and how to deploy g1t to Cloudflare are pages on docs.g1t.sh under Run g1t yourself, and speed, rate limits and operating g1t.sh are sections of CONTRIBUTING.md; code that cited a file in docs/ now points to the page or section that covers it, or says what it means itself, and applied migrations and the runner images are left as they were.3d ago
cli-release.mjsThe g1t CLI 0.1.0 is downloadable: g1t.sh/downloads/cli/latest/, five platforms with SHA256SUMS6d ago
cloudflare-setup.pyDeploy scripts live in the repository1w ago
conformance-diff.mjsMerge remote-tracking branch 'origin/claude/cool-newton-7nm8r9'yesterday
deploy.mjsThe artifacts service is services/artifacts, the Worker g1t-artifacts, bound as ARTIFACTS by the API, the site and the agents; its live rooms move to it with a Durable Object transfer from g1t-docs-service, and its database, bucket, indexes and queue keep their names. The git store's binding and settings are GITSTORE, its ops scripts gitstore-*, and workflow run artifacts keep their compatible API under run_artifacts modules. The deploy tool puts a Worker that has never deployed before the Workers in its stage that bind to it, and the deploy guide gives the cutover runbook.3d ago
deploy.shThe docs folder is gone, and what it held lives where people read it: how a self-hosted g1t runs and how to deploy g1t to Cloudflare are pages on docs.g1t.sh under Run g1t yourself, and speed, rate limits and operating g1t.sh are sections of CONTRIBUTING.md; code that cited a file in docs/ now points to the page or section that covers it, or says what it means itself, and applied migrations and the runner images are left as they were.3d ago
desktop-release.mjsA desktop release lists every platform it built. Each build job notes what it collected in a file named for its machine, and the Windows build on Linux runs on the same kind of machine as the Linux build, so its notes replaced the Linux job's when the publish job merged them: 0.2.0's files all uploaded, but its manifest named Windows alone. The notes are named for the platforms they hold now.yesterday
desktop-release.test.mjsA desktop release lists every platform it built. Each build job notes what it collected in a file named for its machine, and the Windows build on Linux runs on the same kind of machine as the Linux build, so its notes replaced the Linux job's when the publish job merged them: 0.2.0's files all uploaded, but its manifest named Windows alone. The notes are named for the platforms they hold now.yesterday
mobile-release.mjsThe phone app with your own g1t, on g1t.sh/download until Google Play, and Node 24 (#5)2d ago
mobile-release.test.mjsThe phone app with your own g1t, on g1t.sh/download until Google Play, and Node 24 (#5)2d ago
runner-release.mjsMerge 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.yesterday
runner-release.test.mjsMerge 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.yesterday
sandbox-image.mjsMerge 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.yesterday
sccache.shThe docs folder is gone, and what it held lives where people read it: how a self-hosted g1t runs and how to deploy g1t to Cloudflare are pages on docs.g1t.sh under Run g1t yourself, and speed, rate limits and operating g1t.sh are sections of CONTRIBUTING.md; code that cited a file in docs/ now points to the page or section that covers it, or says what it means itself, and applied migrations and the runner images are left as they were.3d ago
setup-custom-domains.shAgents and memory, checks and conflicts, profiles, slug renames, custom domains1w ago
setup-deployments.shThe docs folder is gone, and what it held lives where people read it: how a self-hosted g1t runs and how to deploy g1t to Cloudflare are pages on docs.g1t.sh under Run g1t yourself, and speed, rate limits and operating g1t.sh are sections of CONTRIBUTING.md; code that cited a file in docs/ now points to the page or section that covers it, or says what it means itself, and applied migrations and the runner images are left as they were.3d ago