Bisecting Bugs With AI Help

Git bisect is a precision tool — and AI agents are excellent bisecters. Learn to structure a bisect session with an agent, including auto-bisect with an AI-written test script.

11 min · Reviewed 2026

When the Bug Was Born

A regression is a bug that didn't used to be there. Knowing when it appeared is more than half the fight. `git bisect` performs binary search through your history, asking you to mark each commit good or bad until it finds the first bad one. AI agents are surprisingly good at running this loop for you.

The 5-step manual bisect

# 1. Start the bisect at a known-bad and a known-good commit
git bisect start
git bisect bad HEAD            # current commit is broken
git bisect good v2.4.0         # last release was fine

# Git checks out a middle commit and waits for your verdict.

# 2. Test it. Either run a script, run the app, or both.
npm test -- --grep "login flow"

# 3. Tell git what you found
git bisect bad      # or `good` if the test passed

# 4. Repeat (5-7 iterations for ~100 commits)

# 5. When done
git bisect resetManual bisect, the textbook flow. AI changes step 2 and step 3 dramatically.

Where AI plugs in

Step	Manual	With AI
Decide good vs bad	You run the test, eyeball output	Agent runs the test and reports verdict
Diagnose between commits	You diff the commits, read the changes	Agent summarizes commit diffs and risk areas
Write the repro test	You write it before bisecting	Agent generates a minimal repro from your bug report
Final root cause	You read the offending diff	Agent explains why that diff broke things

AI-assisted automated bisect

`git bisect run` takes a script and runs it on each candidate commit. The script's exit code (0 = good, non-zero = bad) decides the verdict. Have an AI agent write the script for you, then unleash bisect on it.

# Step 1: ask the agent to write a minimal repro script
# Prompt: "Write a bash script test-regression.sh that exits 0
#   if our login redirects to /dashboard, and 1 if it 500s.
#   Use curl. No browser. Save the response."

# Step 2: make sure the script works on HEAD (should fail) and on v2.4.0 (should pass)
chmod +x test-regression.sh
./test-regression.sh; echo $?      # 1
git checkout v2.4.0
./test-regression.sh; echo $?      # 0

# Step 3: run automated bisect
git bisect start HEAD v2.4.0
git bisect run ./test-regression.sh

# Git crawls the history, runs the script per commit,
# and prints the first bad commit when done. ~30 seconds for 100 commits.The agent writes the test, git does the search. You drink coffee.

Common bisect failures and AI fixes

Test fails for unrelated reasons (missing dep) — agent re-runs `npm install` per commit
Old commits don't build — agent marks those as `git bisect skip`
Bug is intermittent — agent runs the test 5 times and votes majority
Bug needs DB state — agent reseeds the DB before each test

# Useful prompt to a Claude Code session

"I have a regression. Bug: <description>.
Steps to reproduce: <steps>.

1. Find the last commit where this worked (assume it's tagged or in the last 200 commits).
2. Write a minimal bash script test-regression.sh that returns 0/1 based on whether the bug is present.
3. Validate the script works on HEAD (returns 1) and on the suspected good commit (returns 0).
4. Run `git bisect run ./test-regression.sh` and report the first bad commit.
5. Open that commit's diff and summarize, in 3 bullets, why this change introduced the bug."End-to-end automated regression hunt — works in any git project.

After the bisect

Once the agent finds the first bad commit, the next prompt is gold: "Read the diff of <commit-hash>. Explain in plain English what changed, why someone made that change, and the most surgical fix that preserves the original intent." You get history, intent, and a fix in one turn.

Bisect is the closest thing software has to a time machine.
— Linus Torvalds, more or less

The big idea: bisect plus AI agent equals a near-automated regression detective. Spend your effort writing a tight repro script and let the machinery handle the search. The first-bad-commit you find is usually so small the fix is obvious.

End-of-lesson check

15 questions · take it digitally for instant feedback at tendril.neural-forge.io/learn/quiz/end-coding-debug-bisecting-with-ai-creators

What is the core idea behind "Bisecting Bugs With AI Help"?
1. Git bisect is a precision tool — and AI agents are excellent bisecters. Learn to structure a bisect session with an agent, including auto-bisect with an AI-written test script.
2. Are the goals concrete? "Cleaner" is not a goal. "Reduce auth.
3. Open-source projects with copyright provenance requirements
4. AI happily writes code with classic vulnerabilities.
Which term best describes a foundational idea in "Bisecting Bugs With AI Help"?
1. regression
2. git bisect
3. minimal repro
4. bisect run
A learner studying Bisecting Bugs With AI Help would need to understand which concept?
1. git bisect
2. minimal repro
3. regression
4. bisect run
Which of these is directly relevant to Bisecting Bugs With AI Help?
1. git bisect
2. regression
3. bisect run
4. minimal repro
Which of the following is a key point about Bisecting Bugs With AI Help?
1. Test fails for unrelated reasons (missing dep) — agent re-runs `npm install` per commit
2. Old commits don't build — agent marks those as `git bisect skip`
3. Bug is intermittent — agent runs the test 5 times and votes majority
4. Bug needs DB state — agent reseeds the DB before each test
Which of these does NOT belong in a discussion of Bisecting Bugs With AI Help?
1. Are the goals concrete? "Cleaner" is not a goal. "Reduce auth.
2. Test fails for unrelated reasons (missing dep) — agent re-runs `npm install` per commit
3. Bug is intermittent — agent runs the test 5 times and votes majority
4. Old commits don't build — agent marks those as `git bisect skip`
What is the key insight about "The repro script is the hard part" in the context of Bisecting Bugs With AI Help?
1. Are the goals concrete? "Cleaner" is not a goal. "Reduce auth.
2. Open-source projects with copyright provenance requirements
3. Bisect is mechanical. Writing a 5-line script that reliably reproduces the bug, with no false positives, is where the sk…
4. AI happily writes code with classic vulnerabilities.
What is the key insight about "Don't bisect what you can't reproduce" in the context of Bisecting Bugs With AI Help?
1. Are the goals concrete? "Cleaner" is not a goal. "Reduce auth.
2. Open-source projects with copyright provenance requirements
3. AI happily writes code with classic vulnerabilities.
4. If the bug only happens in production with real data, bisecting against a local repo will lie to you.
Which statement accurately describes an aspect of Bisecting Bugs With AI Help?
1. A regression is a bug that didn't used to be there. Knowing when it appeared is more than half the fight.
2. Are the goals concrete? "Cleaner" is not a goal. "Reduce auth.
3. Open-source projects with copyright provenance requirements
4. AI happily writes code with classic vulnerabilities.
What does working with Bisecting Bugs With AI Help typically involve?
1. Are the goals concrete? "Cleaner" is not a goal. "Reduce auth.
2. `git bisect run` takes a script and runs it on each candidate commit. The script's exit code (0 = good, non-zero = bad) decides the verdict.
3. Open-source projects with copyright provenance requirements
4. AI happily writes code with classic vulnerabilities.
Which of the following is true about Bisecting Bugs With AI Help?
1. Are the goals concrete? "Cleaner" is not a goal. "Reduce auth.
2. Open-source projects with copyright provenance requirements
3. Once the agent finds the first bad commit, the next prompt is gold: "Read the diff of <commit-hash>.
4. AI happily writes code with classic vulnerabilities.
Which best describes the scope of "Bisecting Bugs With AI Help"?
1. It is unrelated to ai-coding workflows
2. It applies only to the opposite beginner tier
3. It was deprecated in 2024 and no longer relevant
4. It focuses on Git bisect is a precision tool — and AI agents are excellent bisecters. Learn to structure a bisect
Which section heading best belongs in a lesson about Bisecting Bugs With AI Help?
1. The 5-step manual bisect
2. Are the goals concrete? "Cleaner" is not a goal. "Reduce auth.
3. Open-source projects with copyright provenance requirements
4. AI happily writes code with classic vulnerabilities.
Which section heading best belongs in a lesson about Bisecting Bugs With AI Help?
1. Are the goals concrete? "Cleaner" is not a goal. "Reduce auth.
2. Where AI plugs in
3. Open-source projects with copyright provenance requirements
4. AI happily writes code with classic vulnerabilities.
Which section heading best belongs in a lesson about Bisecting Bugs With AI Help?
1. Are the goals concrete? "Cleaner" is not a goal. "Reduce auth.
2. Open-source projects with copyright provenance requirements
3. AI-assisted automated bisect
4. AI happily writes code with classic vulnerabilities.

← Back to interactive lesson

Tendril · Creators · AI-Assisted Coding