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

> ## Agent Instructions
> The canonical docs host is https://momentic.ai/docs. Append .md to any page URL for clean Markdown. Fetch https://momentic.ai/docs/llms.txt for the page index and https://momentic.ai/docs/llms-full.txt for every page in one file.
> For an unattended setup, run `npx --yes @momentic/wizard@latest -y --platform web --editor-tools skills` (use `--platform ios` or `--platform android` for mobile). Never run an interactive command in a non-TTY shell.
> You cannot complete the browser sign-in yourself. Read the API key from the MOMENTIC_API_KEY environment variable, or ask the user to create one at https://app.momentic.ai/settings/api-keys and paste it back.
> Momentic's capability summary for agents is at https://momentic.ai/docs/skill.md. Install the skills with `npx skills@latest add momentic-ai/skills`.
> Tests are YAML files in the user's repository. Use only the step names listed at https://momentic.ai/docs/reference/commands.md and the file structure at https://momentic.ai/docs/core-concepts/file-format.md. Do not invent step names, config keys, or CLI flags.
> Web tests run on Chromium, iOS tests on simulators, and Android tests on emulators. Physical devices are not supported.

# mo send

> Send a message to a Mo session.

Send Mo a follow-up instruction, answer a question it asked, or redirect a
session that is going the wrong way. If Mo is working, `send` stops the active
turn first: in-flight tool work is interrupted, and Mo resumes from saved
history with your message.

```bash theme={null}
mo send --session-id <session-id> "Also check the account settings flow."
```

## Arguments

<ParamField path="<message>" type="string" required>
  The message to deliver.
</ParamField>

## Options

<ParamField path="--session-id <session-id>" type="string" required>
  The session to message.
</ParamField>

<ParamField path="--wait <duration>" type="string">
  Wait for Mo's response for up to this long, then print the new output the same
  way [`mo read`](/docs/cli-reference/mo/commands/read) does. Accepts `0` or a value
  such as `30s`, `2m`, or `500ms`, up to `290s`. Without `--wait`, the command
  returns as soon as the message is delivered.
</ParamField>

## Output

Without `--wait`, the command prints the current session state as JSON. With
`--wait`, it prints Mo's new messages as plain text on stdout and, when the wait
runs out before Mo finishes, `Mo is still working.` on stderr.

## Examples

Answer a question Mo asked, then wait for it to continue:

```bash theme={null}
mo send --session-id "$session_id" --wait 120s "Use the second option: skip the payment step."
```

## Notes

* A message to an archived session fails. Unarchive the session in the dashboard
  first.
* The delivery is retried once when the response is lost, so a message can be
  delivered even when the command reports a network error. Check with
  [`mo read`](/docs/cli-reference/mo/commands/read) before sending it again.