Short-lived sessions
Idle repository files are removed after 15 minutes, with an absolute one-hour session lifetime.
Short-lived repository work by design
Isolation you can inspect.
Repository commands run inside a constrained Linux microsandbox with visible resource limits, live telemetry, and automatic cleanup.
- GitHub, GitLab & Bitbucket
- Microsandbox isolation
- Bring your own AI provider
MICROSANDBOX / ACTIVE
disk31 / 100 MB
ram59 / 128 MB
cpu0.04 / 0.2
NETWORKdisabled
SESSION TTL15 min idle
FILESYSTEMscoped
RUNTIMELinux
Repository process stays inside the visible boundary.
CONTROLS
Boundaries you can inspect
Network isolation
Repository commands run without sandbox network access and with constrained CPU, memory, and disk.
Scoped repository access
Git provider installations expose only repositories selected by the user or organization.
Private provider option
For sensitive code, use an AI provider and key controlled by your organization.
FAQ
Questions, answered
Can GitGPT open private repositories?
Yes. Install the GitHub App for selected repositories, or authorize GitLab or Bitbucket through OAuth.
Does the AI see my entire repository?
No. GitGPT selects structural and question-relevant context, including files explicitly referenced with @.
What happens when a session expires?
The sandbox stops, local repository files are removed, and workspace chat and terminal state are cleared.
Can I use my own AI model?
Yes. Add a supported provider or a public OpenAI-compatible HTTPS endpoint in your profile.
G
Open workspaceOpen a repository.
Code context, without context switching.