A focused environment for unfamiliar code

The repository is the interface.

Files, search, editing, terminal output, previews, and AI context stay together from the first question to the verified change.

COMMAND PALETTE

Find anything. Keep your place.

Search files and sourceShift Shift

ffffilename searchEnter

rgcontent searchEnter

@attach repository contextTab

WORKSPACE

Reference files and folders with @. GitGPT assembles structural context before the model answers.

Open multiple tabs, edit highlighted code, and preview Markdown, SVG, images, and PDFs.

Run commands inside the repository sandbox and keep history for the life of the session.

Use fff for filenames and ripgrep for content without replacing the repository tree.

Use included freemium inference or connect a supported custom AI provider from your profile.

Read disk, memory, and CPU usage from the active sandbox rather than host estimates.

SANDBOX

Idle repository files are removed after 15 minutes, with an absolute one-hour session lifetime.

Repository commands run without sandbox network access and with constrained CPU, memory, and disk.

Git provider installations expose only repositories selected by the user or organization.

For sensitive code, use an AI provider and key controlled by your organization.

FAQ

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.

Code context, without context switching.