# `cli.dev_arguments`

A `jadpo dev` command names an action it doesn't have, `token` without a user's id, or a `--url` the project's several stores can't share.

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

## Why Jadpo refuses it

`jadpo dev` serves the app, and `jadpo dev token <user-id>` signs a token for one user from its local issuer. A token for the wrong user would test the wrong access, so it signs none until it is told whose.

## What it looks like

The user's id is left out:


```sh
jadpo dev token
```

```text
error: `jadpo dev token` needs a user's id
  reason: It signs a token for that user's subject, from the local issuer `jadpo dev` runs in the provider's place.
  next: Run `jadpo dev token <user-id>`, with the user's `id` (agent)
  rule: cli.dev_arguments
  help: https://jadpo.dev/docs/errors/cli.dev_arguments
```

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

A word `jadpo dev` doesn't take is refused too:

```sh
jadpo dev serve
```

```text
error: `jadpo dev` has no `serve`
  reason: `jadpo dev` serves the app; `jadpo dev token <user-id>` signs a token from its local issuer.
  next: Run `jadpo dev`, or `jadpo dev token <user-id>` (agent)
  rule: cli.dev_arguments
  help: https://jadpo.dev/docs/errors/cli.dev_arguments
```

The answer is the same however many words follow it.

## How to fix it

**If you want a token**, give the user's `id`:

```sh
jadpo dev token user_1
```

It prints a token for that user's subject, which `jadpo dev` accepts.

**If you want to serve the app**, run it with nothing after it:

```sh
jadpo dev
```

It serves the app and restarts it on each save.

## Related

- [`jadpo dev`](/docs/the-jadpo-command.md#jadpo-dev)
- [Sign-in in development and tests](/docs/in-development-and-tests.md)