# `cli.seed_arguments`

A `jadpo seed` command names no seed, one the project doesn't have, or more than one.

Area 14, [Tools](/docs/tooling.md); not declinable; the next step is usually the agent's.

## Why Jadpo refuses it

A seed writes records into a database, so `jadpo seed` runs the one you name and never another.

## What it looks like

A project with no seeds, asked to run one:


```sh
jadpo seed demo
```

```text
error: `demo` isn't a seed
  reason: The project has no seeds: each is a file in `database/seeds/`.
  next: Write one in `database/seeds/<name>.jadpo`, as `seed { … }` (agent)
  rule: cli.seed_arguments
  help: https://jadpo.dev/docs/errors/cli.seed_arguments
```

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

## How to fix it

**If the seed isn't written yet**, write it in `database/seeds/demo.jadpo`, as `seed { … }`, then run it:

```sh
jadpo seed demo
```

It runs against the database on this machine.

## Related

- [`jadpo seed`](/docs/commands-for-the-database-settings-and-translations.md#jadpo-seed)
- [Seeds](/docs/seeds.md)