Skip to content

Troubleshooting

Use the command output as the starting point. Atlante reports a stable diagnostic code, a source or location, the expected contract, and a recovery action when those details are available.

If the CLI reports config-not-found, run it from the project root or pass the explicit configuration path:

Terminal window
npx @atlante/cli validate ./path/to/atlante.jsonc

The supported filenames are exactly atlante.jsonc and atlante.json.

If the CLI reports ambiguous-config, remove the file that is not authoritative or pass an explicit path. Atlante never chooses between both files silently.

Check the locator and its containing file. Relative locators begin with ./ or ../; package locators use the package name and optional POSIX subpath.

Terminal window
npm install --save-dev @acme/review-pack
npx @atlante/cli validate

The package must be declared and installed before the CLI can resolve it.

The selected template owns fields after description, $template, $instance, and values. Read its template.jsonc schema and remove unsupported fields or supply the required input. A binding cannot use $template and $instance together.

Check the spelling of each {{values.key}} reference and confirm that the key is present in the global or binding-local values map. Values are strings, and a missing reference is an error before rendering.

Run a successful build first:

Terminal window
npx @atlante/cli validate
npx @atlante/cli build

Then confirm that opencode.jsonc registers @atlante/opencode. The adapter reads only .atlante/artifacts/; it does not load the source configuration.

A missing artifact tree means the project has not completed a build. A malformed or changed tree is rejected by the fail-closed reader. Re-run atlante build after fixing the source and keep .atlante/ local.

Run npx @atlante/cli build after changing atlante.jsonc, local resources, or selected pack content. Use --watch during active editing to rebuild the selected dependency graph automatically.