Jadpo is experimental and not ready for production. These docs follow the compiler's main branch as of 5 Nov 2026. What's built · Install 0.3.0
jadpo
ReferenceErrors

ErrorsTools · rule

toolchain.scaffold_name_invalid

On this page

You ran jadpo new with a path that doesn't end in a folder's name, such as .. or /.

Area 14, Tools; not declinable; the next step is usually the agent's.

Why Jadpo refuses it

jadpo new <name> makes the project in the folder its argument names, and names the project after that folder. A path ending in .., or / alone, names no folder of its own, so there is nothing to call the project, and the command writes nothing.

What it looks like

Asking for the project in the folder above:

shell
jadpo new ..
jadpo new

error .. doesn't name a folder for the project

reason
jadpo new makes the project in the folder its argument names, and names the project after that folder, so the argument ends in a folder's name.
next
Give the project's name, for example jadpo new my-app (agent)
rule
toolchain.scaffold_name_invalid
help
https://jadpo.dev/docs/errors/toolchain.scaffold_name_invalid

(agent) at the end of the next: line means your coding agent can make the fix itself.

How to fix it

If the project should go in the folder you are in, name it .. The folder must be empty, and the project is named after it:

shell
jadpo new .
output
Created .    jadpo  X.Y    route  POST /hello    files  14 writtennext: jadpo dev  serves it on http://localhost:3000

The project is written where you are.

If it should go in a new folder, name that folder:

shell
jadpo new todo-app
output
Created todo-app    jadpo  X.Y    route  POST /hello    files  14 writtennext: cd todo-app && jadpo dev  serves it on http://localhost:3000

The project is in todo-app, and named after it.

Markdown for agents: /docs/errors/toolchain.scaffold_name_invalid.md.Built from Jadpo main at aee2e8f.