Skip to main content

🤔 When to Use Which Agent

Early AI offers multiple agents — each optimized for different code lifecycle events.
This guide helps you quickly determine which one fits your use case based on:

  • 🧪 What triggers the generation?
  • 🔄 How frequently do you want tests to be generated?
  • ⚙️ Which CI/CD platform are you using?
  • 🧱 Do you want PR-based coverage or repo-wide?

📌 Quick Decision Guide​

🟢 Use the GitHub PR Agent if:​

  • You're using GitHub Actions
  • You want test generation to run automatically on every PR
  • You prefer a zero-config GitHub-native experience

→ GitHub PR Agent →

🟡 Use the CLI PR Agent if:​

  • You work with pull requests, but not in GitHub Actions
  • You're using Jenkins, CircleCI, or another CI system
  • You want to run test generation on PR creation or update

→ CLI PR Agent →

🔵 Use the CLI Commit Agent if:​

  • You want to trigger generation on each commit
  • You’re using push-based pipelines (e.g. on: push)
  • You're not working with PRs (e.g., internal repos, trunk-based development)

→ Commit CLI Agent →

🟣 Use the CLI Repository Agent if:​

  • You want to raise coverage across a folder or legacy area
  • You want to run it weekly or on-demand
  • You want a one-shot coverage boost

→ Repo CLI Agent →

📊 Agent Comparison Table​

AgentTriggerTarget ScopeSCM SupportBest For
GitHub PR AgentPR opened/updatedChanged filesGitHub onlyGitHub-native PR automation
CLI PR AgentPR-based jobsChanged filesGitHub, BitbucketPR workflows in non-GitHub CI
CLI Commit AgentCommit pushChanged filesGitHub, BitbucketCommit-driven CI (Jenkins, GitHub)
CLI Repo AgentManual / CronWhole foldersAll (GitHub, Bitbucket, GitLab planned)Coverage boost across entire areas

🧠 Common Questions​

What if I use Bitbucket?​

Use CLI PR, CLI Commit, or Repo CLI — all support Bitbucket via --scm-provider bitbucket.

Can I use multiple agents in the same repo?​

Yes!
For example:

  • Use PR-based agents for daily dev
  • Use the Repo agent weekly to backfill missing coverage

How do I choose between generate-pr, generate-commit, and generate-folder?​

Depends on your workflow:

  • generate-pr → fine-grained, change-specific testing
  • generate-commit → broader but still scoped to what changed
  • generate-folder → strategic coverage upgrade for legacy areas

📎 Next Steps​