Troubleshooting¶

This guide explains common problems and how to fix them.

Problem: AgentTrace Says It Must Run Inside A Git Repository¶

Message:

AgentTrace must be run inside a Git repository. Run `git init` first.

Fix:

Go to your project folder and run:

git init

Then run:

agenttrace init

Message:

AgentTrace is not initialized in this workspace. Run `agenttrace init` first.

Fix:

agenttrace init

Message:

No active AgentTrace run. Run `agenttrace start "<task>"` first.

Fix:

Start a run:

agenttrace start "describe your task"

Message:

Review file does not exist

Fix:

Create the review file first.

Example:

notepad review-notes.md

Then run:

agenttrace add-review review-notes.md

Message:

Could not infer GitHub repository from remote `origin`.

This happens when AgentTrace cannot tell which GitHub repository your project belongs to.

Fix option 1: pass the full pull request URL:

agenttrace pr https://github.com/acme/widgets/pull/42

Fix option 2: add a GitHub remote to your Git repo:

git remote add origin https://github.com/acme/widgets.git

Then:

agenttrace pr 42

If you run:

agenttrace add-test "your test command"

and the test command fails, AgentTrace still records the result.

That is useful because the report can show that a test failed.

Fix the code or test setup, then run the test command again:

agenttrace add-test "your test command"

You may see a warning like:

running scripts is disabled on this system

This warning comes from PowerShell trying to load a profile script. It is usually separate from AgentTrace.

If the AgentTrace command still runs, you can continue.

If PowerShell blocks your work, ask someone who manages your machine before changing execution policy.