Issue Station
Sign In
Tools hereToolbox

openclaw - ✅(Solved) Fix [Feature]: Document ZALOUSER_PROFILE and ZCA_PROFILE env vars in Zalo Personal channel docs [3 pull requests, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#65864•Fetched 2026-04-14 05:39:52
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
Jah-yeeJah-yee
Participants
Jah-yeeJah-yee
Timeline (top)
cross-referenced ×3

Document the ZALOUSER_PROFILE and ZCA_PROFILE environment variables in docs/channels/zalouser.md. These env vars are declared in the plugin manifest and actively read by the code, but the channel docs page does not mention them.

Root Cause

Document the ZALOUSER_PROFILE and ZCA_PROFILE environment variables in docs/channels/zalouser.md. These env vars are declared in the plugin manifest and actively read by the code, but the channel docs page does not mention them.

Fix Action

Fixed

PR fix notes

PR #65877: docs(zalouser): document profile environment overrides

Description (problem / solution / changelog)

Summary

  • fixes #65864
  • document ZALOUSER_PROFILE and ZCA_PROFILE in the Zalo Personal channel docs

Why

The runtime already reads these environment variables for profile resolution, but users had no discoverable documentation in docs/channels/zalouser.md.

Changes

  • docs/channels/zalouser.md
    • add a Profile environment overrides section under multi-account docs
    • describe both variables and their fallback order

Validation

  • pnpm check:no-conflict-markers

Notes

  • docs-only update
  • local validation passed before PR creation

Made with Cursor

Changed files

  • docs/channels/zalouser.md (modified, +9/-0)

PR #65932: docs(zalouser): document profile environment overrides

Description (problem / solution / changelog)

Summary

  • fixes #65864
  • document ZALOUSER_PROFILE and ZCA_PROFILE plus resolution order

Changes

  • docs/channels/zalouser.md
    • add profile environment override section under multi-account

Validation

  • pnpm check:no-conflict-markers

Notes

  • docs-only update
  • local validation passed

Made with Cursor

Changed files

  • docs/channels/zalouser.md (modified, +9/-0)

PR #65942: docs(zalouser): document profile environment overrides

Description (problem / solution / changelog)

Summary

  • fixes #65864
  • document ZALOUSER_PROFILE and ZCA_PROFILE for Zalouser profile resolution

Why

Runtime supports these env overrides, but docs did not expose them.

Changes

  • docs/channels/zalouser.md
    • add profile environment override section and resolution order

Validation

  • pnpm check:no-conflict-markers

Notes

  • docs-only update
  • local validation passed

Made with Cursor

Changed files

  • docs/channels/zalouser.md (modified, +9/-0)

Code Example

// extensions/zalouser/openclaw.plugin.json
"channelEnvVars": { "zalouser": ["ZALOUSER_PROFILE", "ZCA_PROFILE"] }

---

// extensions/zalouser/src/accounts.ts lines 44-48
const profileDir = process.env.ZALOUSER_PROFILE || process.env.ZCA_PROFILE;

---

$ rg "ZALOUSER_PROFILE|ZCA_PROFILE" docs/channels/zalouser.md
(no matches)
RAW_BUFFERClick to expand / collapse

Summary

Document the ZALOUSER_PROFILE and ZCA_PROFILE environment variables in docs/channels/zalouser.md. These env vars are declared in the plugin manifest and actively read by the code, but the channel docs page does not mention them.

Problem to solve

Users setting up the Zalo Personal (zalouser) channel have no documentation about the ZALOUSER_PROFILE and ZCA_PROFILE environment variables. The manifest declares them as channelEnvVars, and the code reads them in extensions/zalouser/src/accounts.ts (lines 44-48), but the docs page docs/channels/zalouser.md does not reference either variable at all.

This means users must read the source code to discover configuration options for multi-account or profile-based Zalo setups.

Proposed solution

Add an "Environment variables" or "Configuration" section to docs/channels/zalouser.md that documents:

VariableDescription
ZALOUSER_PROFILEPath to the Zalo user profile directory (overrides default)
ZCA_PROFILEAlternative profile path (fallback if ZALOUSER_PROFILE is not set)

Include a brief explanation of when each variable is useful (e.g., running multiple Zalo accounts, CI/containerized setups).

Alternatives considered

  • Relying on code comments and manifest alone — insufficient for end users who don't read source code.
  • Adding a --help flag to the channel CLI — this exists but is not a substitute for proper docs.

Impact

  • Affected: Zalo Personal channel users, especially those with multi-account or non-default profile setups
  • Severity: Low (documentation gap, not a functional bug)
  • Frequency: Every Zalo Personal setup
  • Consequence: Users must reverse-engineer env vars from source code

Evidence/examples

Plugin manifest declares the env vars:

// extensions/zalouser/openclaw.plugin.json
"channelEnvVars": { "zalouser": ["ZALOUSER_PROFILE", "ZCA_PROFILE"] }

Code reads them:

// extensions/zalouser/src/accounts.ts lines 44-48
const profileDir = process.env.ZALOUSER_PROFILE || process.env.ZCA_PROFILE;

Docs page — grep returns no matches:

$ rg "ZALOUSER_PROFILE|ZCA_PROFILE" docs/channels/zalouser.md
(no matches)

Additional information

This follows the same pattern as other channel docs that document their env vars (e.g., docs/channels/qqbot.md documents QQBOT_APP_ID and QQBOT_CLIENT_SECRET).

extent analysis

TL;DR

Add documentation for ZALOUSER_PROFILE and ZCA_PROFILE environment variables to the docs/channels/zalouser.md page to inform users about configuration options for multi-account or profile-based Zalo setups.

Guidance

  • Review the proposed solution and add an "Environment variables" or "Configuration" section to docs/channels/zalouser.md with the described table and explanations.
  • Ensure the documentation includes brief explanations of when each variable is useful, such as for running multiple Zalo accounts or in CI/containerized setups.
  • Verify the documentation by checking that the variables are correctly described and that the explanations are clear and concise.
  • Consider following the pattern of other channel docs, such as docs/channels/qqbot.md, which documents environment variables like QQBOT_APP_ID and QQBOT_CLIENT_SECRET.

Example

### Environment variables

The following environment variables can be used to configure the Zalo Personal channel:

| Variable | Description |
|----------|-------------|
| `ZALOUSER_PROFILE` | Path to the Zalo user profile directory (overrides default) |
| `ZCA_PROFILE` | Alternative profile path (fallback if `ZALOUSER_PROFILE` is not set) |

These variables are useful when running multiple Zalo accounts or in CI/containerized setups.

Notes

The issue is a documentation gap, not a functional bug, so the severity is low. However, adding clear documentation will improve the user experience and reduce the need for users to reverse-engineer environment variables from source code.

Recommendation

Apply the proposed solution by adding the environment variable documentation to docs/channels/zalouser.md, as it directly addresses the issue and follows the pattern of other channel docs.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#environment variable#SSR setup#ISR setup#authentication setup#request error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING