toolchain.scaffold_write_failed

You ran jadpo new or jadpo package new, and writing its files failed, usually because the folder they go in can't be written.

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

Why Jadpo refuses it

jadpo new writes a whole project or none of it. When the operating system refuses one of its files, it removes what it had already written and says which file and why, so you are never left with half a project that doesn't check.

Jadpo won't change permissions or pick another folder for you: both are decisions about your files.

What it looks like

The folder apps is read-only, and the project is asked for inside it:

mkdir appschmod a-w appsjadpo new apps/todo-app

(human) at the end of the next: line tells your coding agent to stop and ask you which fix you want, because the choice is yours to make: it decides who may write where the project goes.

How to fix it

If the folder should be writable, let yourself write to it, then run the command again:

chmod u+w appsjadpo new apps/todo-app

The whole project is written into apps/todo-app.

If the folder should stay read-only, make the project somewhere you can write:

jadpo new todo-app

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 apps is untouched.

Related

• jadpo new
• The jadpo command