Skip to main content

Not sure what went wrong?

Copy the error message into your AI chat and say:
Send to your agent
Include what you were trying to do and the last command or action. Remove passwords, API keys, and other private values before sharing an error message.
Start with jig doctor. It checks the machine, the project and your agent’s instructions, one line each, and prints a fix for every warning. On Windows, run it in Git Bash, or as .ai\scripts\jig.cmd doctor in PowerShell. If the trouble turns out to be Jig itself rather than your project, see Known issues — the faults we know about, and what to do instead of each.

The agent does not follow Jig

Installation

Projects and tasks

Verification and upgrades

upgrade: cannot determine the framework source root; pass --from <dir> in a project on Jig 0.38.1 or older usually means .ai/manifest has a jig.source: line naming another person’s folder. The project’s own copy cannot get past it — nor can your agent, or a jig shell function or alias that runs that copy. Run the upgrade once with the Jig on your machine, by its full path, in the project’s root folder. macOS and Linux:
Windows, in Git Bash:
Afterwards .ai/manifest says jig.source: global when that Jig is the one on your PATH (else it names its folder), and a plain jig upgrade works. More in Upgrading.

Writes on a branch of their own

A change to a roadmap or a decision on knowledge, made from a program or with jig writes ship, is committed on a branch of its own (Writes on a branch of their own). When Jig refuses it, the refusal has a code; nothing was written.

Reviewing a colleague’s pull request

These come from jig pr, used by the jig-pr-review skill (Skills). In each, nothing was posted.