Skip to content

[Bug]: Telegram channel drops / compact slash command - never appears in commands.log #89525

@bomberluke37-prog

Description

@bomberluke37-prog

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

After upgrading from 2026.5.18 to latest, manual compaction from Telegram no longer works. It has been tested and does not show up in the logs.

Steps to reproduce

Try /compact on Telegram, there is no response.

Expected behavior

The slash compact command should compact the context of the agent.

Actual behavior

Nothing happens, the agent doesn’t reply, and the command is silently dropped.

OpenClaw version

2026.5.28

Operating system

Raspberry pi lite

Install method

NPM global

Model

Claude sonnet 4.6

Provider / routing chain

Openclaw / telegram

Additional provider/model setup details

No response

Logs, screenshots, and evidence

No CLI compact command. Here's the situation honestly:

/compact from Telegram is broken in stable — Telegram intercepts the / prefix as a bot command and OpenClaw's Telegram plugin isn't routing it to the slash-command handler. Nothing in commands.log, no CLI equivalent, no API endpoint.

Workarounds:

1. Auto-compaction — already configured and will trigger automatically when context fills up (your maxActiveTranscriptBytes: 20mb + truncateAfterCompaction: true config is correct)
2. /new — starts a fresh session (harder reset, loses recent context)
3. Control UI — if you open http://192.168.1.200:18789 in a browser, the Control UI may have a compact button that works natively

I'd recommend reporting this to the OpenClaw GitHub (github.com/openclaw/openclaw) as a stable bug: "Telegram channel drops /compact slash command — never appears in commands.log." It's a clean, reproducible bug report.

Impact and severity

No response

Additional information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Normal backlog priority with limited blast radius.bugSomething isn't workingclawsweeper:needs-live-reproClawSweeper needs live local, crabbox, or manual validation to confirm this issue.impact:message-lossChannel message delivery can be lost, duplicated, or misrouted.impact:session-stateSession, memory, transcript, context, or agent state can drift or corrupt.issue-rating: 🐚 platinum hermitGood issue quality with a plausible reproduction path needing some confirmation.regressionBehavior that previously worked and now fails

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions