FAQ: first-run setup

기준일: 2026-07-26
공식 기준: FAQ: first-run setup

FAQ: first-run setup 문서는 OpenClaw 공식 문서(help/faq-first-run)를 한국어로 정리한 가이드입니다. FAQ: quick-start and first-run setup — install, onboard, auth, subscriptions, initial failures 명령·설정 키·코드 예시는 공식 문서를 그대로 보존하며, 해석과 절차 안내는 한국어로 제공합니다. 최종 동작은 설치된 CLI 버전과 공식 원문을 확인하세요.

핵심 요약

FAQ: quick-start and first-run setup — install, onboard, auth, subscriptions, initial failures

한국어 가이드 범위: help/faq-first-run 경로의 설정·명령·제약·예시를 학습용으로 재구성합니다.

문서 구성

공식 문서의 주요 섹션은 다음과 같습니다.

Quick start and first-run setup
관련 문서

상세 내용

본문

Quick-start and first-run Q&A. For everyday operations, models, auth, sessions, and troubleshooting see the main FAQ.

위 내용은 공식 문서의 해당 섹션 요지입니다. 세부 플래그·기본값은 원문과 --help를 확인하세요.

Quick start and first-run setup

Use a local AI agent that can see your machine. Most "I'm stuck" cases are

위 내용은 공식 문서의 해당 섹션 요지입니다. 세부 플래그·기본값은 원문과 --help를 확인하세요.

주요 항목:

Claude Code: https://www.anthropic.com/claude-code/
OpenAI Codex: https://openai.com/codex/
Open http://127.0.0.1:18789/.
If it asks for shared-secret auth, paste the configured token or password into Control UI settings.
Token source: gateway.auth.token (or OPENCLAW_GATEWAY_TOKEN).
Password source: gateway.auth.password (or OPENCLAW_GATEWAY_PASSWORD).
No shared secret configured yet? Run openclaw doctor --generate-gateway-token (or openclaw doctor --fix --generate-gateway-token).
Tailscale Serve (recommended): keep bind loopback, run openclaw gateway --tailscale serve, open https://<magicdns>/. With gateway.auth.allowTailscale: true, identity headers satisfy Control UI/WebSocket auth (no pasted shared secret, assumes a trusted gateway host); HTTP APIs still need shared-secret auth unless you deliberately use private-ingress none or trusted-proxy HTTP auth.
Tailnet bind: run openclaw gateway --bind tailnet --token "<token>" (or configure password auth), open http://<tailscale-ip>:18789/, paste the matching shared secret in dashboard settings.
Identity-aware reverse proxy: keep the Gateway behind a trusted proxy, set gateway.auth.mode: "trusted-proxy", open the proxy URL. Same-host loopback proxies need explicit gateway.auth.trustedProxy.allowLoopback: true.
SSH tunnel: ssh -N -L 18789:127.0.0.1:18789 user@gateway-host, then open http://127.0.0.1:18789/. Shared-secret auth still applies over the tunnel; paste the configured token or password if prompted.
approvals.exec - forwards approval prompts to chat destinations.
channels.<channel>.execApprovals - makes that channel a native approval client for exec approvals.
If the chat already supports commands and replies, same-chat /approve works through the shared path.
When a supported native channel can infer approvers safely, OpenClaw auto-enables DM-first native approvals if channels.<channel>.execApprovals.enabled is unset or "auto".
When native approval cards/buttons are available, that UI is primary; only mention a manual /approve command if the tool result says chat approvals are unavailable.
Use approvals.exec only when prompts must also reach other chats or explicit ops rooms.
Use channels.<channel>.execApprovals.target: "channel" or "both" only when you want approval prompts posted back into the originating room/topic.
Plugin approvals are separate: same-chat /approve by default, optional approvals.plugin forwarding, and only some native channels keep native handling for those too.
Use a 64-bit OS; do not use 32-bit Raspberry Pi OS.
Add swap on 2 GB or smaller boards.
Prefer a USB SSD over an SD card for performance and longevity.
Prefer the hackable (git) install so you can see logs and update fast.
Start without channels/skills, add them one by one.
Weird binary failures ("exec format error") are usually a missing ARM64 build for an optional skill tool.

curl -fsSL --proto '=https' --tlsv1.2 https://openclaw.ai/install.sh | bash -s -- --install-method git

curl -fsSL --proto '=https' --tlsv1.2 https://openclaw.ai/install.sh | bash
    openclaw onboard --install-daemon

git clone https://github.com/openclaw/openclaw.git
    cd openclaw
    pnpm install
    pnpm build
    pnpm ui:build
    openclaw onboard

openclaw gateway restart

실습 체크리스트

공식 문서와 로컬 버전을 대조합니다: https://docs.openclaw.ai/help/faq-first-run
관련 CLI는 openclaw --help 및 하위 명령 --help로 옵션을 확인합니다.
설정 변경 시 openclaw config / openclaw doctor로 유효성을 검사합니다.
Gateway·채널·플러그인 변경 후에는 필요 시 Gateway를 재시작합니다.

자주 쓰는 명령·설정 예시

curl -fsSL --proto '=https' --tlsv1.2 https://openclaw.ai/install.sh | bash -s -- --install-method git

curl -fsSL --proto '=https' --tlsv1.2 https://openclaw.ai/install.sh | bash
    openclaw onboard --install-daemon

git clone https://github.com/openclaw/openclaw.git
    cd openclaw
    pnpm install
    pnpm build
    pnpm ui:build
    openclaw onboard

openclaw gateway restart

openclaw status
    openclaw models status
    openclaw logs --follow

openclaw doctor

FAQ: first-run setup

기준일: 2026-07-26
공식 기준: FAQ: first-run setup

핵심 요약

FAQ: quick-start and first-run setup — install, onboard, auth, subscriptions, initial failures

한국어 가이드 범위: help/faq-first-run 경로의 설정·명령·제약·예시를 학습용으로 재구성합니다.

문서 구성

공식 문서의 주요 섹션은 다음과 같습니다.

Quick start and first-run setup
관련 문서

상세 내용

본문

Quick-start and first-run Q&A. For everyday operations, models, auth, sessions, and troubleshooting see the main FAQ.

위 내용은 공식 문서의 해당 섹션 요지입니다. 세부 플래그·기본값은 원문과 --help를 확인하세요.

Quick start and first-run setup

Use a local AI agent that can see your machine. Most "I'm stuck" cases are

위 내용은 공식 문서의 해당 섹션 요지입니다. 세부 플래그·기본값은 원문과 --help를 확인하세요.

주요 항목:

Claude Code: https://www.anthropic.com/claude-code/
OpenAI Codex: https://openai.com/codex/
Open http://127.0.0.1:18789/.
If it asks for shared-secret auth, paste the configured token or password into Control UI settings.
Token source: gateway.auth.token (or OPENCLAW_GATEWAY_TOKEN).
Password source: gateway.auth.password (or OPENCLAW_GATEWAY_PASSWORD).
No shared secret configured yet? Run openclaw doctor --generate-gateway-token (or openclaw doctor --fix --generate-gateway-token).
Tailscale Serve (recommended): keep bind loopback, run openclaw gateway --tailscale serve, open https://<magicdns>/. With gateway.auth.allowTailscale: true, identity headers satisfy Control UI/WebSocket auth (no pasted shared secret, assumes a trusted gateway host); HTTP APIs still need shared-secret auth unless you deliberately use private-ingress none or trusted-proxy HTTP auth.
Tailnet bind: run openclaw gateway --bind tailnet --token "<token>" (or configure password auth), open http://<tailscale-ip>:18789/, paste the matching shared secret in dashboard settings.
Identity-aware reverse proxy: keep the Gateway behind a trusted proxy, set gateway.auth.mode: "trusted-proxy", open the proxy URL. Same-host loopback proxies need explicit gateway.auth.trustedProxy.allowLoopback: true.
SSH tunnel: ssh -N -L 18789:127.0.0.1:18789 user@gateway-host, then open http://127.0.0.1:18789/. Shared-secret auth still applies over the tunnel; paste the configured token or password if prompted.
approvals.exec - forwards approval prompts to chat destinations.
channels.<channel>.execApprovals - makes that channel a native approval client for exec approvals.
If the chat already supports commands and replies, same-chat /approve works through the shared path.
When a supported native channel can infer approvers safely, OpenClaw auto-enables DM-first native approvals if channels.<channel>.execApprovals.enabled is unset or "auto".
When native approval cards/buttons are available, that UI is primary; only mention a manual /approve command if the tool result says chat approvals are unavailable.
Use approvals.exec only when prompts must also reach other chats or explicit ops rooms.
Use channels.<channel>.execApprovals.target: "channel" or "both" only when you want approval prompts posted back into the originating room/topic.
Plugin approvals are separate: same-chat /approve by default, optional approvals.plugin forwarding, and only some native channels keep native handling for those too.
Use a 64-bit OS; do not use 32-bit Raspberry Pi OS.
Add swap on 2 GB or smaller boards.
Prefer a USB SSD over an SD card for performance and longevity.
Prefer the hackable (git) install so you can see logs and update fast.
Start without channels/skills, add them one by one.
Weird binary failures ("exec format error") are usually a missing ARM64 build for an optional skill tool.

curl -fsSL --proto '=https' --tlsv1.2 https://openclaw.ai/install.sh | bash -s -- --install-method git

curl -fsSL --proto '=https' --tlsv1.2 https://openclaw.ai/install.sh | bash
    openclaw onboard --install-daemon

git clone https://github.com/openclaw/openclaw.git
    cd openclaw
    pnpm install
    pnpm build
    pnpm ui:build
    openclaw onboard

openclaw gateway restart

실습 체크리스트

공식 문서와 로컬 버전을 대조합니다: https://docs.openclaw.ai/help/faq-first-run
관련 CLI는 openclaw --help 및 하위 명령 --help로 옵션을 확인합니다.
설정 변경 시 openclaw config / openclaw doctor로 유효성을 검사합니다.
Gateway·채널·플러그인 변경 후에는 필요 시 Gateway를 재시작합니다.

자주 쓰는 명령·설정 예시

curl -fsSL --proto '=https' --tlsv1.2 https://openclaw.ai/install.sh | bash -s -- --install-method git

curl -fsSL --proto '=https' --tlsv1.2 https://openclaw.ai/install.sh | bash
    openclaw onboard --install-daemon

git clone https://github.com/openclaw/openclaw.git
    cd openclaw
    pnpm install
    pnpm build
    pnpm ui:build
    openclaw onboard

openclaw gateway restart

openclaw status
    openclaw models status
    openclaw logs --follow

openclaw doctor

FAQ: first-run setup

핵심 요약

문서 구성

상세 내용

본문

Quick start and first-run setup

관련 문서

실습 체크리스트

자주 쓰는 명령·설정 예시

관련 링크

관련 가이드

FAQ: first-run setup

핵심 요약

문서 구성

상세 내용

본문

Quick start and first-run setup

관련 문서

실습 체크리스트

자주 쓰는 명령·설정 예시

관련 링크

관련 가이드