How-to guides

Keep your project in sync with your code

To work on your repository, DIJJI.ai keeps an up-to-date understanding of it — what it calls your AI engineer’s map. When code changes outside DIJJI.ai — you push to the branch directly, or merge a pull request elsewhere — that map can fall behind the real code. Before a run works against a stale picture, DIJJI.ai asks you to refresh it. This page covers that prompt and the sync it runs.

The “map is out of date” prompt

When you select Run on a task and your code has changed outside DIJJI.ai since it last looked, a dialog appears instead of starting the run:

Your AI engineer’s map is out of date Your code changed outside DIJJI, so your AI engineer’s map no longer matches the latest code. Sync it first to keep results accurate. Syncing is free.

It offers one action: Sync first. (Dismiss the dialog if you’d rather not run right now.) The prompt shows up the same way whether you start the task from the Tasks list or from the task’s own page.

Sync first

Select Sync first. DIJJI.ai refreshes its map by running a Syncing Dijji task — a short, read-only pass that brings its understanding back in line with your latest code. You’ll see Syncing Dijji appear in your task list while it runs.

The sync is free — it doesn’t draw down your balance. (See Credits and billing for what is and isn’t charged.)

Once the sync finishes, start your task again. It now works against an accurate picture of your code, so its plan and changes line up with what’s actually there.

When the queue is waiting on a sync

If a project’s task queue pauses with “Docs are out of date — sync them to continue,” it’s the same situation: queued tasks won’t run against a stale map. Run the sync, and the queue carries on.

What you don’t need to do

There’s no manual “sync” button to hunt for, and no setting to switch on — DIJJI.ai keeps its map current as you work through it, and prompts you only when something changed outside it that it can’t reconcile on its own. When you see the prompt, Sync first is the whole job.

A sync only catches the map up. If its understanding looks not just behind but wrong, a heavier rebuild exists — see Reset Dijji.