fix(qqbot): support QQBOT_DATA_DIR environment variable#77218
Conversation
Allow users to customize QQBot data directory by setting QQBOT_DATA_DIR environment variable. Falls back to ~/.openclaw/qqbot when not set. Fixes openclaw#39461
|
Codex review: needs changes before merge. Summary Reproducibility: yes. Source inspection gives a high-confidence path: with Next step before merge Security Review findings
Review detailsBest possible solution: Centralize effective QQBot data-dir resolution, treat blank overrides as unset, make diagnostics use the effective path, and add focused regression coverage while keeping the new docs and changelog entry. Do we have a high-confidence way to reproduce the issue? Yes. Source inspection gives a high-confidence path: with Is this the best way to solve the issue? No. The PR changes the right owner-owned helper and adds docs/changelog, but it should also handle blank env values, update diagnostics, and add regression tests before merge. Full review comments:
Overall correctness: patch is incorrect Acceptance criteria:
What I checked:
Likely related people:
Remaining risk / open question:
Codex review notes: model gpt-5.5, reasoning high; reviewed against 89a15fddaf84. |
Add QQBOT_DATA_DIR to qqbot.md configuration docs and CHANGELOG.md. Refs openclaw#39461
Summary
Allow users to customize QQBot data directory by setting QQBOT_DATA_DIR environment variable. Falls back to ~/.openclaw/qqbot when not set.
Change Type (select all)
Scope (select all touched areas)
Linked Issue/PR
Root Cause (if applicable)
For bug fixes or regressions, explain why this happened, not just what changed. Otherwise write
N/A. If the cause is unclear, writeUnknown.Regression Test Plan (if applicable)
For bug fixes or regressions, name the smallest reliable test coverage that should catch this. Otherwise write
N/A.User-visible / Behavior Changes
List user-visible changes (including defaults/config).
If none, write
None.Diagram (if applicable)
For UI changes or non-trivial logic flows, include a small ASCII diagram reviewers can scan quickly. Otherwise write
N/A.Security Impact (required)
Yes/No)Yes/No)Yes/No)Yes/No)Yes/No)Yes, explain risk + mitigation:Repro + Verification
Environment
Steps
Expected
Actual
Evidence
Attach at least one:
Human Verification (required)
What you personally verified (not just CI), and how:
Review Conversations
If a bot review conversation is addressed by this PR, resolve that conversation yourself. Do not leave bot review conversation cleanup for maintainers.
Compatibility / Migration
Yes/No)Yes/No)Yes/No)Risks and Mitigations
List only real risks for this PR. Add/remove entries as needed. If none, write
None.