-
-
Notifications
You must be signed in to change notification settings - Fork 80.7k
feat: openclaw message send --message-file <path> #79182
Copy link
Copy link
Open
Labels
P2Normal backlog priority with limited blast radius.Normal backlog priority with limited blast radius.clawsweeper:linked-pr-openClawSweeper found an open linked pull request for this issue.ClawSweeper found an open linked pull request for this issue.clawsweeper:needs-product-decisionClawSweeper marked this issue as needing a product or behavior decision.ClawSweeper marked this issue as needing a product or behavior decision.clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.ClawSweeper does not recommend queueing a new automated fix PR for this issue.clawsweeper:source-reproClawSweeper found a high-confidence source-level issue reproduction.ClawSweeper found a high-confidence source-level issue reproduction.impact:message-lossChannel message delivery can be lost, duplicated, or misrouted.Channel message delivery can be lost, duplicated, or misrouted.issue-rating: 🦞 diamond lobsterVery strong issue quality with high-confidence source-level or clear reproduction.Very strong issue quality with high-confidence source-level or clear reproduction.
Description
Metadata
Metadata
Assignees
Labels
P2Normal backlog priority with limited blast radius.Normal backlog priority with limited blast radius.clawsweeper:linked-pr-openClawSweeper found an open linked pull request for this issue.ClawSweeper found an open linked pull request for this issue.clawsweeper:needs-product-decisionClawSweeper marked this issue as needing a product or behavior decision.ClawSweeper marked this issue as needing a product or behavior decision.clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.ClawSweeper does not recommend queueing a new automated fix PR for this issue.clawsweeper:source-reproClawSweeper found a high-confidence source-level issue reproduction.ClawSweeper found a high-confidence source-level issue reproduction.impact:message-lossChannel message delivery can be lost, duplicated, or misrouted.Channel message delivery can be lost, duplicated, or misrouted.issue-rating: 🦞 diamond lobsterVery strong issue quality with high-confidence source-level or clear reproduction.Very strong issue quality with high-confidence source-level or clear reproduction.
Type
Fields
Priority
None yet
Feature Request:
--message-fileflag foropenclaw message sendProblem
When AI agents generate completion reports containing code blocks, JSON, multiline content,
$references, backticks, or quotes, passing them via shell expansion to--messagecauses:line 1: bad substitution)Current workaround patterns are fragile and error-prone:
This means agent completion notifications — the primary way background tasks report back to users — are unreliable whenever output contains code.
Proposed Solution
Add a
--message-file <path>flag toopenclaw message send:Acceptance Criteria
--channel,--target,--account,--reply-to,--thread-id)--message(error if both provided)[truncated]) rather than silently dropping or failingUse Case
Agent completion notification pattern:
Context
Discovered during Log-it Android service fix where two background Claude Code agents completed their work but failed to send Telegram completion notifications due to shell expansion issues in the completion prompt.