Skip to content

[Bug]: qqbot media directory ignores OPENCLAW_HOME, hardcodes ~/.openclaw/media/ #83562

@vipcxj

Description

@vipcxj

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

When OPENCLAW_HOME is set to a custom path, the qqbot media directory still resolves to ~/.openclaw/media/qqbot/ instead of $OPENCLAW_HOME/.openclaw/media/qqbot/, causing image sends to silently fail.

Steps to reproduce

  1. Set OPENCLAW_HOME to a custom path (e.g., /home/ps/workspace/docker/aichat/openclaw)
  2. Ensure HOME differs from the parent of OPENCLAW_HOME (e.g., HOME=/home/node)
  3. Have an agent generate or copy a file into $OPENCLAW_HOME/.openclaw/media/qqbot/
  4. Agent sends image via $OPENCLAW_HOME/.openclaw/media/qqbot/image.png
  5. Image fails to deliver — qqbot plugin reads from ~/.openclaw/media/qqbot/ instead

Expected behavior

qqbot media directory should resolve relative to OPENCLAW_HOME, not HOME. Files written to $OPENCLAW_HOME/.openclaw/media/qqbot/ should be readable and deliverable by the qqbot plugin.

Actual behavior

qqbot plugin resolves media directory as ~/.openclaw/media/qqbot/ (e.g., /home/node/.openclaw/media/qqbot/), ignoring OPENCLAW_HOME. Files written to the OPENCLAW_HOME-based path are never found, resulting in silent send failures.

OpenClaw version

2026.5.12

Operating system

Linux 6.8.0-110-generic (x64), running in Docker

Install method

docker

Model

Qwen3.6-27B (llamacpp)

Provider / routing chain

Direct gateway → qqbot channel plugin

Additional provider/model setup details

No response

Logs, screenshots, and evidence

- HOME=/home/node
- OPENCLAW_HOME=/home/ps/workspace/docker/aichat/openclaw
- File written to: /home/ps/workspace/docker/aichat/openclaw/.openclaw/media/qqbot/mojoco.png (8785 bytes, valid PNG)
- qqbot reads from: /home/node/.openclaw/media/qqbot/ (empty, no file)
- Result: image not delivered

Impact and severity

  • Affected users: All users with custom OPENCLAW_HOME who use qqbot media features
  • Severity: Blocks workflow — media sends silently fail with no error to the user
  • Frequency: Always, when OPENCLAW_HOME differs from HOME
  • Consequence: Users cannot send images/voice/video via qqbot when using custom home paths

Additional information

The qqbot-media SKILL.md explicitly states files should be in ~/.openclaw/media/qqbot/, but ~ expands to HOME, not OPENCLAW_HOME. The plugin should use OPENCLAW_HOME as the base path for all media operations.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Normal backlog priority with limited blast radius.bugSomething isn't workingbug:behaviorIncorrect behavior without a crashclawsweeper:fix-shape-clearClawSweeper found a clear likely implementation shape for this issue.clawsweeper:linked-pr-openClawSweeper found an open linked pull request for this issue.clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.clawsweeper:queueable-fixClawSweeper marked this issue as an existing queue_fix_pr work candidate.clawsweeper:source-reproClawSweeper found a high-confidence source-level issue reproduction.impact:message-lossChannel message delivery can be lost, duplicated, or misrouted.issue-rating: 🦞 diamond lobsterVery strong issue quality with high-confidence source-level or clear reproduction.

    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