> ## Documentation Index
> Fetch the complete documentation index at: https://radiusbrowser.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Chat turns

> Start an agent turn from the command line, follow it, and answer its permission prompts.

`radius chat` starts and follows agent turns in a running Radius. Combined
with [`--on`](https://radiusbrowser.com/docs/radius-cli/machines), the turn runs on another Mac: the agent
works in that Mac's files and uses that Mac's browser and signed-in sites.

## Start a turn

```bash theme={"theme":{"light":"github-light","dark":"github-dark"}}
radius chat send "Run the tests and fix what fails" --project-path /Users/me/code/app
```

This opens a chat for that project in a background tab, sends the prompt, and
prints the conversation ID. The chat is an ordinary Radius chat: it appears in
the project's group and in chat history.

The chat uses that Radius's default agent and model. To choose, pass both
`--provider` and `--model`:

```bash theme={"theme":{"light":"github-light","dark":"github-dark"}}
radius chat send "Run the tests" --project-path /Users/me/code/app \
  --provider codex-bridge --model gpt-6.1-sol
```

Add `--watch` to stay attached until the turn ends:

```bash theme={"theme":{"light":"github-light","dark":"github-dark"}}
radius --on studio chat send "Run the tests" --project-path /Users/me/code/app --watch
```

With `--watch`, the command prints JSON Lines. The first line identifies the
conversation; each following line is one agent event with a `cursor`:

```json theme={"theme":{"light":"github-light","dark":"github-dark"}}
{"kind":"radius.chat.sent","conversationId":"…","projectPath":"/Users/me/code/app","tabId":"tab_42"}
{"cursor":"turn-…:0","kind":"turn.started", …}
```

The command exits `0` when the conversation is idle, and non-zero with
`CHAT_TURN_FAILED` when the turn failed.

A turn that was still running when Radius quit or crashed is reported as
failed, so reconnecting to it ends with `CHAT_TURN_FAILED`, not success.

To send another message to the same conversation, pass `--conversation`. If a
turn is running there, the message waits its turn and `--watch` waits with it:

```bash theme={"theme":{"light":"github-light","dark":"github-dark"}}
radius chat send "Now run the linter too" --conversation <conversation-id> --watch
```

## Reconnect to a running turn

The turn belongs to the Radius it runs in. Stopping `radius chat`, closing
your laptop, or losing the ssh connection does not stop it.

To pick up where you left off, pass the last `cursor` you saw:

```bash theme={"theme":{"light":"github-light","dark":"github-dark"}}
radius --on studio chat events <conversation-id> --after <cursor> --watch
```

Without `--watch`, `chat events` prints what is available now and exits.

## Permission prompts

When the agent needs permission, the event stream shows a
`permission.requested` event, and the turn waits.

```bash theme={"theme":{"light":"github-light","dark":"github-dark"}}
radius chat status <conversation-id>
radius chat approve <conversation-id>
radius chat deny <conversation-id> --guidance "Use the staging database"
```

`approve` allows that one request. When several prompts are waiting, name the
one to answer: `radius chat approve <conversation-id> <permission-id>`.

Agents cannot answer permission prompts, or use any other `radius chat`
command: in a terminal that Radius opened for an agent, they are refused.

## Stop a turn

```bash theme={"theme":{"light":"github-light","dark":"github-dark"}}
radius chat cancel <conversation-id>
```


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.