Fuzit

Troubleshooting

Troubleshooting documentation.

Repository root is wrong

bash
fuzit scan --list-roots

Then:

bash
fuzit scan --root /path/to/repository

File is missing

bash
fuzit scan --explain-path path/to/file

Inspect:

  • built-in exclusions;
  • `fuzit.config.json`;
  • `.fuzitignore`;
  • `.gitignore`;
  • CLI include/exclude;
  • sensitive-path policy.

Context is missing an important file

Use:

bash
fuzit context   --task "..."   --profile bug-fix   --budget-tokens 8000   --format json   --output context.json   --explain

Then:

bash
fuzit explain path path/to/file context.json

Possible remedies:

  • make the task more specific;
  • mention the relevant path;
  • increase the budget;
  • choose a more suitable profile;
  • inspect graph neighbors.

Index appears stale

bash
fuzit cache status --root .
fuzit cache verify --root .
fuzit cache rebuild --root . --dry-run
fuzit cache rebuild --root .

GitHub authentication failure

bash
fuzit auth status

Then:

bash
fuzit auth github

Or configure:

text
FUZIT_GITHUB_TOKEN

or:

text
GH_TOKEN

Verify repository access.

Invalid GitHub URL

PR:

text
https://github.com/OWNER/REPO/pull/123

Issue:

text
https://github.com/OWNER/REPO/issues/123

Use the matching command.

Output already exists

Fuzit avoids silently overwriting generated files. Choose a new output path or intentionally remove the existing artifact.

Do not use broad recursive deletion as a generic recovery mechanism.

------------------------------------------------------------------------

PreviousPipeline