# `cli.routes_arguments`

A `jadpo routes` command is given an argument, which it doesn't take.

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

## Why Jadpo refuses it

`jadpo routes` lists every route the project serves, so it takes no name, and refuses a word rather than ignore it.

## What it looks like

A route is named:


```sh
jadpo routes greet
```

```text
error: `jadpo routes` takes no arguments
  reason: It was given `greet`.
  next: Run `jadpo routes` (agent)
  rule: cli.routes_arguments
  help: https://jadpo.dev/docs/errors/cli.routes_arguments
```

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

## How to fix it

**If you want the routes**, leave the argument out:

```sh
jadpo routes
```

It lists each route with its method, path and who may call it.

## Related

- [`jadpo routes`](/docs/commands-for-looking-into-and-changing-code.md#jadpo-routes)