# Use native client commands and connection options

The supplied native client provides interactive SQL, history and completion. Its documented options select the address, identity, database and query. A custom prompt-format option is not part of the public command-line contract.

```sh
./coordinator client --addr 127.0.0.1:7400 --database data
```

## Confirm the connection explicitly

Use a distinct terminal title or your terminal application's labeling when several environments are open. Keep the chosen address and database visible in your own session notes. Do not assume that changing a shell prompt changes the database selected by an already running SQL connection.

In the interactive client, `help` lists commands and `.quit` exits. Up and Down recall history, and Tab completes keywords, databases, tables and columns. A final SQL semicolon is optional for complete input. Incomplete quotes and trigger bodies continue onto another line.

## Keep automation separate

Use `--query` for a scripted request that writes only exact result bytes to stdout. Piped SQL does not read or write interactive history. For secrets, the password can come from `COORDINATOR_PASSWORD`; avoid placing real credentials in shared command examples or terminal screenshots.

See [native client](https://coordinatordb.com/docs/concepts/features/interfaces/client), [command-line syntax](https://coordinatordb.com/docs/concepts/features/interfaces/cli) and [USE](https://coordinatordb.com/docs/reference/statements/use).