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

# invoke

```bash theme={null}
telnyx-acp invoke support-agent --conversation alice "hi"
telnyx-acp invoke support-agent --conversation alice --stream "hi"
```

| Flag | Meaning |
| - | - |
| `--conversation <id>` | The conversation, which names the instance. Required. |
| `--stream` | Print each assistant message as it lands, one per harness step, not token by token. Ignored under `--json`, where the messages are `data.messages`. |
| `--local` | Target the running `dev` instead of the deployed agent. |

`invoke` posts one text to `/rpc/receive` on the conversation's address and reads the reply back from the instance's state stream. A run paused for an approval or canceled ends `invoke` with exit 1 and a line that says so; a run that produced no reply ends with `run <id> completed without a reply` on stderr and exit 0. None waits for a timeout. `invoke` carries no sender, so a fresh conversation's memory profile is its own name, `alice` here; a conversation that was earlier given a `from` through `rpc … receive` keeps that sender as its profile.

Anything else that speaks the wire can do the same, the `POST …/rpc/receive` call on [the address](/docs/agent-sdk/contract/address-and-transports) or the [AgentClient](/docs/agent-sdk/client-sdk/constructor). [The RPC Methods](/docs/agent-sdk/inside/request-handling/rpc-methods#receive) is where the call lands in the managed harness.