Build a map before making a move
TheGitAI searches the repository, finds relevant code, and reads the surrounding conventions before it changes anything.
- Exact, regex, and natural-language code search
- Fresh reads after files change
TheGitAI capabilities
Code, browsers and desktop apps in one agent. See how it works, choose where it can act, and explore the tools that carry the work through.
Let it work in front of you, or keep using your computer while it works in the background. The permission prompt puts that choice in your hands, every turn or for the session.
Choose where it works, and whether that choice lasts for this turn or this session. Try each option below.

Your mouse. Your keyboard. Still yours.
A separate screen with its own input. Keep using your own apps, or minimize the preview while the agent continues.
Work in signed-in dashboards, cloud consoles and admin panels from the same agent in your CLI or desktop app.
Get the Chrome extension Browser Control setup and permissions →Install it from the Chrome Web Store, then start the CLI or desktop app. It connects locally, with no pairing step.
Tell the agent which page to use and what to do. Default mode asks before it acts on a website.
Work stays in the session’s tab group. Remove a tab from the group to take it back, or use Stop in the extension popup.
Find a capability and open its guide.
Connect your existing Chrome to the CLI and desktop app.
Works from the command line next to any editor.
Conversations, files and changes side by side.
Use signed-in websites through the Chrome extension.
Choose your screen or the background, for one turn or the session.
Connect local or remote tools.
Teach it your workflows as SKILL.md folders.
Switch mid-session without losing the conversation.
Keep dev servers, watchers and local APIs running.
Run independent lookups together.
Follow the plan and its progress.
Investigate and plan before making changes.
Choose when the agent asks before taking action.
Recover agent changes without overwriting your own.
Resume a conversation later in the same project.
Read documents and edit Word files.
Show it what you are looking at.
Look up information while it works.
Work with branches, commits and reviews.
Send corrections without stopping the run.
Trace the cause, implement the fix, and prove the result against the real project.
Keep source, tests, configuration, and documentation moving together.
Keep servers, watchers, builds, and local APIs available while the agent works.
Ask the agent to reverse an edit, file, turn, or checkpoint without discarding unrelated work.
TheGitAI is built for work that crosses files, tools, and stages. Give it the outcome and let it gather the evidence needed to get there.
TheGitAI searches the repository, finds relevant code, and reads the surrounding conventions before it changes anything.
Ask for the feature, migration, refactor, or fix. The agent can create, patch, replace, and delete files while keeping the larger task in view.
It can reproduce failures, inspect diagnostics, run focused scripts, and use your own tests, builds, linters, and typecheckers as evidence.
TheGitAI works with Git when the task calls for it, reviews the resulting diff, and can carry work from investigation through a verified change.
Tree-sitter-backed mapping extracts useful structure for the languages below. Other project files remain available through normal reading, listing, and search tools.
Long tasks should not feel like watching one command finish at a time. TheGitAI parallelizes safe research, manages persistent processes, shows visible task progress, and accepts your next instruction before the current turn ends.
Reads, searches, listings, symbol queries, and web lookups can execute concurrently while edits and other mutations stay serial.
Multi-step work stays legible with pending, active, and completed steps. The current list remains in view and the finished snapshot stays in the transcript.
Type one follow-up while the agent is busy. It submits automatically when the turn finishes, or you can recall, edit, replace, or cancel it.
Run up to eight dev servers, watchers, builds, or local APIs without blocking the conversation. Follow live output, inspect the captured log, stop a job by id, and let the session clean up what remains.
Background jobs guideReal engineering work arrives in many formats. TheGitAI can bring those inputs into the same task instead of making you translate everything into a prompt first.
Read PDF, XLSX, and DOCX files as structured task context. Replace visible text in Word documents, including table content, and save the edited result.
Paste a screenshot or type an image path into the prompt. Vision-capable models can inspect UI states, diagrams, error screens, and visual references.
Search the public web and fetch specific pages as clean Markdown, with coverage and continuation metadata when the source is too large for one read.
Real tasks do not stop at the repository. TheGitAI works in the Chrome you are signed in to, calls the tools your MCP servers expose, and follows the skills you teach it.
With the TheGitAI Chrome extension, the agent works in the Chrome you already have open, signed in as you: cloud consoles, internal dashboards, and sites with no API or export button. It can also check the page you just built and click through the flow.
Connect local or remote MCP servers with ai mcp add, and the model can call their tools in the middle of a task, from library documentation to browser testing.
A skill is a folder with a SKILL.md: the steps for a release, a deploy checklist, or a review routine, plus any scripts and references it needs. TheGitAI uses one when a request calls for it, or when you type /<name>.
Choose the operating mode, review sensitive actions, and recover assistant changes without reaching for a destructive repository reset.
Default mode asks before edits and commands. Bypass all permissions removes every prompt for work you already trust. Plan mode stays read-only.
Every assistant edit is journaled. The agent can preview an undo, reverse one edit or a whole turn, and restore complete or selected files from a checkpoint.
Recent sessions are saved on your machine and scoped to each repository, alongside a compact global prompt history for requests you reuse.
Local repository tools run on your machine. Relevant task context is sent to the server-backed model so it can respond and decide which tools to use. Provider credentials and private orchestration remain server-side. We don't store your source files, your prompts, or your conversations on our servers - saved sessions keep metadata only. See the privacy policy.
The picker spans complementary frontier families for speed, depth, and cost. Every entry is selected for serious coding work, and switching models does not clear the session you have already built.
Zero config: every model works with your TheGitAI account.
The practical features available in TheGitAI today, grouped by the job they help you finish.
Want the operating details rather than the tour?
Read the capability guideRequest a feature. If it makes sense for TheGitAI, we'll build it, usually in a day or two, at no charge.
Open a repository you know and see how far it gets on its own.