#OPENCLAW TELEGRAM DELIVERY ISSUE — BYPASS AGENT ROUTING

7 messages · Page 1 of 1 (latest)

proud dust
#

OPENCLAW TELEGRAM DELIVERY ISSUE

Version:
OpenClaw 2026.4.12

OBJECTIVE:
Send output from /root/jobs_pipeline.js to Telegram group -5154421744 without triggering any agent response or transformation.

PROBLEM:
Telegram shows generated job summaries ("Current Job Market Scan...") instead of the pipeline output.

VERIFIED:
• node /root/jobs_pipeline.js → correct output
• Group ID correct
• Script prints correct output locally

ATTEMPTS:
• Removed jobs agent binding
• Switched agent → chat
• Used --to flag
• Tried message, file, and stdin methods

→ Output still replaced by agent response

ISSUE:
Messages sent via openclaw chat appear to trigger agent processing instead of being forwarded as-is.

QUESTION:
What is the correct way to send a message to a Telegram group so that:

• the message is delivered exactly as produced
• no agent response is triggered
• no additional processing occurs

GOAL:
Pipeline output → Telegram group → unchanged

#

@halcyon surge

halcyon surgeBOT
#

Let me verify the docs path and the exact non-agent send path.

#

You’re on the wrong command path.

Use openclaw message send, not openclaw agent, chat, or any session-bound flow.

payload="$(node /root/jobs_pipeline.js)"
openclaw message send \
  --channel telegram \
  --target -5154421744 \
  --message "$payload"

Why this works:

  • openclaw message send is the outbound delivery command
  • it does not run an agent
  • it does not generate/rewrite a reply
#
  • it sends the text straight to Telegram via the channel plugin

So yes, your current behavior makes sense if you used an agent/chat path. Those commands are designed to produce an AI response.

If the output is long or whitespace-sensitive, safer option:

node /root/jobs_pipeline.js > /tmp/jobs_pipeline.txt
openclaw message send \
  --channel telegram \
  --target -5154421744 \
  --media /tmp/jobs_pipeline.txt

That avoids Telegram text-length weirdness.

Docs:

#

One extra gotcha I should call out:

  • --to is the agent/session flag
  • --target is the raw outbound messaging flag

So for your case, the shape needs to be:

openclaw message send --channel telegram --target -5154421744 --message "$payload"

Not:

openclaw agent ... --to ...