what is the default password of the Openclawgateway?

[shaoya730]

what is the default password of the Openclawgateway?
i have to install the node.js with sudo

[clawsweeper]

Thanks for writing this up. I checked the repo boundary, and this lives outside the OpenClaw source shell.

Current documentation and code show no universal OpenClaw gateway or sudo password: gateway access uses setup codes or tokens, while managed WSL administration uses an explicitly launched root shell. This is a setup-support question rather than source-level work.

So I’m closing this as outside the OpenClaw source repository rather than keeping it open as core work.

Review details

Best possible solution:

Keep gateway authentication token- and device-based, and direct managed-WSL users to an explicit root shell for protected commands rather than publishing or inventing a default password.

Do we have a high-confidence way to reproduce the issue?

Not applicable; this asks for credential and sudo guidance rather than reporting a reproducible product failure.

Is this the best way to solve the issue?

Yes; pointing to existing token/device authentication and the explicit root-shell workflow is the narrowest maintainable solution, while creating a default password would conflict with the managed gateway security model.

Security review:

Security review: No patch is proposed, and the issue does not report a security vulnerability.

AGENTS.md: found and applied where relevant.

What I checked:

• Managed gateway privilege model: The managed OpenClawGateway distro documentation states that its service account has no password-based sudo flow. (docs/WSL_GATEWAY_ADMIN.md:3, 0e61fa287afb)
• Supported administrative path: Protected commands are documented to run through an explicitly launched root WSL shell instead of an interactive default password. (docs/WSL_GATEWAY_ADMIN.md:99, 0e61fa287afb)
• Gateway setup model: Existing gateway setup accepts a gateway URL with a token or setup code; it does not define a universal default password. (docs/SETUP.md:55, 0e61fa287afb)
• Credential architecture: Current authentication precedence is paired device token, shared gateway token, then bootstrap token. (docs/CONNECTION_ARCHITECTURE.md:135, 0e61fa287afb)
• Current implementation: CredentialResolver implements token-based resolution and returns no credential when no device, shared, or bootstrap token is available. (src/OpenClaw.Connection/CredentialResolver.cs:20, 0e61fa287afb)
• Documentation history: Git history ties the current managed-WSL guidance to merged documentation work in commit 85445c7. (docs/WSL_GATEWAY_ADMIN.md:3, 85445c78066b)

Likely related people:

• christineyan4: Authored merged work containing the current managed-WSL administration and connection guidance relevant to this question. (role: recent gateway setup contributor; confidence: high; commits: 85445c78066b, e0a4b7c7c28d; files: docs/WSL_GATEWAY_ADMIN.md, docs/CONNECTION_ARCHITECTURE.md, README.md)
• ranjeshj: Merge history connects this person to the pull request containing the current setup and managed-WSL documentation. (role: merger of related documentation work; confidence: medium; commits: 85445c78066b; files: docs/WSL_GATEWAY_ADMIN.md, README.md)

Codex review notes: reasoning high; reviewed against 0e61fa287afb.

[ranjeshj]

There isn't a default password for the managed OpenClawGateway distro.

The gateway-management doc says the app-owned WSL gateway runs as the openclaw user and that "there is no password-based sudo flow": docs/WSL_GATEWAY_ADMIN.md. For normal gateway/config work, use the openclaw user. For protected-file work, intentionally open a root shell from Windows instead:

wsl.exe -d OpenClawGateway --user root -- bash