Command Explorer › re: — the reply's form › text
re:text
Reply as text — the written channel, named.
What it does
The reply is delivered as written text. It is the default every reply already travels in when no channel is named; the command names the default so it can be addressed — and stacked: with another channel, both render the answer in the one reply.
The registry's own words: Reply as text: the written channel — the answer is delivered as written text in the reply. The default when no channel is named: every reply is a text reply until a channel mode says otherwise. Naming the default makes it composable — stacked with another channel (re:voice/text, re:show/text), the channels are co-present in one reply, each rendering the answer in its own medium. 'on' = text replies until cleared; 'off' = clear the text claim (the floor is text either way).
Fire it — usage examples
“Send me that summary.
re:text”→ the summary as written text in the reply — readable, quotable, searchable.
“Give me both:
re:voice/text”→ a voice note and the full text of the same answer, in one reply — each the whole answer in its medium.
re:text on— keep everything in text.→ text replies from now on, until you say
re:text off.
Spoken. Inside a marked span opened by the wake word “Lingo”, the spoken form is “reply text”. Dictated directives fire deliberately, never by accident.
What the agent actually does
The agent delivers the answer as written text in the reply — no other rendering is owed. In a stack it renders the answer in each named medium; no channel is presented as a label or summary of another. With on, it also writes “text replies on” into its persistent memory of you and confirms the save.
The baseline procedure, its edge cases, and this directive's full guide live in the implementation guide: implementation/IMPLEMENTATION.md#cmd-re-text ↗.
When the host can't
No host capability required; text is the floor every host delivers. Always executable.
Conformance — “done when”
The reply's substance was delivered as written text (in a stack, in every named medium), and any state change is persisted and confirmed.
Persistence class: mode-state. Execution report in the reply: not required. A user can test any of this by hand — fire the directive, then check the result against the store, the schedule, or the reply itself.