Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Feature]: Support for WPS Office Global (wps.com) in the kdocs skill [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#73062•Fetched 2026-04-28 06:28:00
View on GitHub
Comments
0
Participants
1
Timeline
1
Reactions
0
Author
lexcorplexcorp
Participants
lexcorplexcorp
Timeline (top)
labeled ×1

The current kdocs skill and kdocs-cli tool are exclusively integrated with the Chinese ecosystem (kdocs.cn / wps.cn). Users of WPS Office Global (wps.com) have no way to connect OpenClaw to their cloud documents.

Root Cause

The current kdocs skill and kdocs-cli tool are exclusively integrated with the Chinese ecosystem (kdocs.cn / wps.cn). Users of WPS Office Global (wps.com) have no way to connect OpenClaw to their cloud documents.

Code Example

kdocs-cli auth login --platform global   # uses wps.com
kdocs-cli auth login --platform cn       # uses wps.cn (current default)
RAW_BUFFERClick to expand / collapse

Summary

Feature Request: Support for WPS Office Global (wps.com) in the kdocs skill

Summary

The current kdocs skill and kdocs-cli tool are exclusively integrated with the Chinese ecosystem (kdocs.cn / wps.cn). Users of WPS Office Global (wps.com) have no way to connect OpenClaw to their cloud documents.

Current behavior

  • kdocs-cli auth login redirects to account.wps.cn (Chinese platform)
  • The OAuth flow is hardcoded to api.wps.cn
  • The token generated only works with the .cn endpoints
  • Using --endpoint https://www.wps.com returns HTTP 403
  • There is no developer/open platform equivalent to open.wps.cn for the global version

Expected behavior

  • kdocs-cli should support authentication against wps.com (global)
  • Users should be able to generate a token from their global WPS account and use it with auth set-token
  • The --endpoint flag should work with a documented global API endpoint

User impact

WPS Office has millions of users on the global platform (wps.com). Currently, all of them are excluded from using the kdocs skill with OpenClaw. This is a significant barrier to adoption outside of China.

Suggested approach

This likely requires Kingsoft to expose a public developer API for wps.com global (similar to open.wps.cn). OpenClaw could then support both endpoints via a configurable option:

kdocs-cli auth login --platform global   # uses wps.com
kdocs-cli auth login --platform cn       # uses wps.cn (current default)

Environment

  • OpenClaw version: latest
  • OS: Linux
  • WPS Office: Global version (wps.com), personal account

References

Problem to solve

The current kdocs skill and kdocs-cli tool are exclusively integrated with the Chinese ecosystem (kdocs.cn / wps.cn). Users of WPS Office Global (wps.com) have no way to connect OpenClaw to their cloud documents.

Proposed solution

This likely requires Kingsoft to expose a public developer API for wps.com global (similar to open.wps.cn). OpenClaw could then support both endpoints via a configurable option:

kdocs-cli auth login --platform global   # uses wps.com
kdocs-cli auth login --platform cn       # uses wps.cn (current default)

### Alternatives considered

_No response_

### Impact

Severity: Medium

### Evidence/examples

_No response_

### Additional information

_No response_

extent analysis

TL;DR

To support WPS Office Global, Kingsoft needs to expose a public developer API for wps.com, and OpenClaw should add a configurable option to use either the global or Chinese endpoint.

Guidance

  • The current kdocs skill and kdocs-cli tool are hardcoded to use the Chinese ecosystem (kdocs.cn / wps.cn), which needs to be modified to support the global version (wps.com).
  • A potential solution is to add a --platform flag to the kdocs-cli auth login command to allow users to choose between the global and Chinese platforms.
  • The --endpoint flag should be updated to work with a documented global API endpoint, if available.
  • Users should be able to generate a token from their global WPS account and use it with auth set-token once the global API is supported.

Example

kdocs-cli auth login --platform global   # uses wps.com
kdocs-cli auth login --platform cn       # uses wps.cn (current default)

Notes

The solution relies on Kingsoft exposing a public developer API for wps.com, which is currently not available. Without this API, OpenClaw cannot support the global version of WPS Office.

Recommendation

Apply workaround: Wait for Kingsoft to expose a public developer API for wps.com and then update OpenClaw to support both endpoints via a configurable option. This will allow users to connect to their cloud documents on the global platform.

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…

FAQ

Expected behavior

  • kdocs-cli should support authentication against wps.com (global)
  • Users should be able to generate a token from their global WPS account and use it with auth set-token
  • The --endpoint flag should work with a documented global API endpoint
#api#container setup#orchestration issue#cache issue#memory leak

Still need to ship something?

×6

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

Back to top recommendations

TRENDING