# `cli.lsp_arguments`

A `jadpo lsp` 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 lsp` is the language server your editor starts. It finds the project from the folder the editor opens, so it takes no path, and refuses a word rather than ignore it.

## What it looks like

A path is given:

```sh
jadpo lsp .
```

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

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

## How to fix it

**If your editor runs it**, leave the argument out:

```sh
jadpo lsp
```

It talks to the editor on its standard input and output.

## Related

- [Editor support](/docs/editor-support.md)
- [Commands for debugging, editors and help](/docs/commands-for-debugging-editors-and-help.md)