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

cli.migrate_arguments

On this page

A jadpo migrate command names no action, one it doesn't have, a purpose for an action that takes none, or a --drop of what isn't retired.

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

Why Jadpo refuses it

jadpo migrate new writes the next migration, apply runs a database's pending ones, and status lists them. Changing a database is never done for a word it doesn't know.

What it looks like

The action is misspelt:

shell
jadpo migrate aply
jadpo migrate

error aply isn't something jadpo migrate does

reason
jadpo migrate new writes the next migration, apply runs a database's pending ones, and status lists them.
next
Use jadpo migrate new, jadpo migrate apply or jadpo migrate status (agent)
rule
cli.migrate_arguments
help
https://jadpo.dev/docs/errors/cli.migrate_arguments

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

A purpose after an action that takes none is refused rather than ignored:

shell
jadpo migrate status add_due_date
jadpo migrate

error jadpo migrate status takes no purpose

reason
Only jadpo migrate new takes a purpose; add_due_date would be ignored.
next
Run jadpo migrate status (agent)
rule
cli.migrate_arguments
help
https://jadpo.dev/docs/errors/cli.migrate_arguments

How to fix it

If you meant to apply the migrations, name apply:

shell
jadpo migrate apply

It runs the pending migrations on the database config.database_url names.

If you meant a new migration, give the purpose to new:

shell
jadpo migrate new add_due_date

It writes the next migration, named after its purpose.

Markdown for agents: /docs/errors/cli.migrate_arguments.md.Built from Jadpo main at aee2e8f.