Skip to content
⌘K
Explore
Download
Docs
Sign in
Sign up
flagon-io
/
g1t
public
Star
0
Overview
Code
Issues
5
Pull requests
1
Agents
Workflows
Deployments
Insights
Files
Commits
Branches
Tags
Releases
Compare
6e2393bceee5c879cafe2c63a38daeb9ab89810e
g1t
/
apps
Claude
agent
and
Claude
agent
The phone app is given out on g1t.sh/download until it is in Google Play, and g1t is built on Node 24.
6e2393b
1d ago
History
api
desktop
docs
mobile
status
sudo
web
api
Every agent can have its own computer. A session that needs one wakes it: a home of its own on g1t cloud, one per agent and never shared, where it runs commands, reads and writes files and keeps what it made, with each session working in its own folder under a shared home; after ten idle minutes it sleeps, its home kept as a snapshot and restored when it wakes, and Reset wipes the home while memory and artifacts stay. Its shell and files are abilities with the usual choices, Alone, Alone when asked, Ask first or Never, offered only inside sessions and never to a chat reply; every command shows on the session with its output, and the agent's new Computer tab shows the state, the disk used of the five gigabytes included, the recent commands, and Wake, Put to sleep and Reset. Machine time counts only while it is awake, on the sandbox lines of the ledger that name the agent and who asked, held to the same spend caps as the session; the disk itself costs nothing in this version. The runner gained a long-lived supervisor that answers the computer's requests inside the container, and the runner service a computer per agent that keeps its snapshot in the agent homes bucket when one is attached, and says so when none is. The REST API and the agent tool can read a computer, wake it, put it to sleep and reset it. The agents, abilities, sessions, runners, billing and deploy guides say how it works and what an operator sets up; pinning a computer to your own runner, its browser and take-over come next.
1d ago
desktop
preparing for cloud work
1d ago
docs
The phone app is given out on g1t.sh/download until it is in Google Play, and g1t is built on Node 24.
1d ago
mobile
The phone app is given out on g1t.sh/download until it is in Google Play, and g1t is built on Node 24.
1d ago
status
docs.g1t.sh and status.g1t.sh follow your system's light or dark setting, and each has an Auto, Light and Dark switch that this browser remembers: the docs' in the header (at the foot of the menu on a phone), with code, search, the API reference and its explorer in both themes; the status page's in its header, chosen before anything is drawn; the workspaces guide says where.
1d ago
sudo
The 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.
1d ago
web
The phone app is given out on g1t.sh/download until it is in Google Play, and g1t is built on Node 24.
1d ago