Conversations pinned to a repo
Each Factory project mirrors one of your repos. Threads keep the full message history between you and the agent, along with the session that's currently doing the work.
How sessions workGitForge Spaces
Sandboxed AI coding agents. Managed game servers.
Factory runs sandboxed AI coding agents against the repos you already host on GitForge. Game runs managed game servers with snapshots and git-driven deployments. One workspace, one session, two new decks.
FactoryThreads Isolation
Sandboxed AI coding agents, working where your code lives.
Every agent session runs in an isolated sandbox with its own scoped credentials. You talk to it in threads pinned to a repo; it clones, branches, and pushes back through the same git transport you use.
Hardened sandboxes, scoped credentials
Sessions execute inside a dedicated sandbox image. Agent and source credentials are provisioned by the Factory control-plane and never leave it.
About credentialsGameServers Deployments
Managed game servers with git-driven deployments.
Register servers behind connectors, watch live status, take snapshots before risky changes, and ship content by deploying a git ref through staged pipelines.
Live status and snapshots
Connected servers report running / stopped / starting state and can be snapshotted on demand — size, timing, and reason tracked for every capture.
Server docsPick a server, pick a ref, ship
Deployments run as pipelines with visible stages and steps, pinned to the exact commit they shipped. Module mappings tie server content paths to the repos that own them.
Deployment docsGet started
Already on GitForge? You're one sign-in away.
Spaces uses your existing GitForge account and workspace. Sign in and ask a workspace admin to enable Factory or Game.