orke session send
Send text to a session; --submit true writes Enter separately. A submission receipt is not execution success.
When to use it
Send text to a session; --submit true writes Enter separately. A submission receipt is not execution success.
Syntax
Terminal
orke session send --id <string> --text <string> --submit <true|false> [--expectedInputRevision <0..max>] [--stdin] [--json]Options
| Option | Required | Values and meaning |
|---|---|---|
--id | Required | Opaque target ID from a preceding readstring |
--text | Required | Exact text to send or save; --stdin is available where shownstring |
--submit | Required | true writes and flushes Enter after text; false sends only texttrue|false |
--expectedInputRevision | Optional | Exact input lease revision observed through screen/status0..max |
--stdin | Optional | Read strict UTF-8 input through standard input. |
Read common options and errors →
Role and constraints
operator · Windows, macOS, Linux
- Requires a running daemon owned by the same OS user; --help never connects.
- Use exactly one of --text or --stdin. Strict UTF-8, at most 1048576 bytes; input is preserved exactly.
- expectedInputRevision is the exact observed input lease revision. Raw control bytes may act even with submit=false. Inspect completedStages/writeProgress/outcomeUnknown on failure.
Examples
Terminal
orke session send --id session-id --text "hello" --submit true --jsonReplace example IDs, slugs, revisions, and files with actual observations and inputs.
Response and partial results
Inspect replies and errors with --json. Acceptance is not work completion.