Skip to content

feat: retain OpenClaw onboarding credentials - #709

Merged
rogerchappel merged 6 commits into
mainfrom
codex/persist-openclaw-onboarding-auth
Jul 20, 2026
Merged

rogerchappel merged 6 commits into
mainfrom
codex/persist-openclaw-onboarding-auth

Conversation

@rogerchappel

Copy link
Copy Markdown
Owner

Summary

  • persist the sealed device identity and device-token bundle when onboarding creates an OpenClaw runtime
  • retain the shared Gateway token separately as an encrypted recovery credential
  • verify the runtime API preserves the opaque device-auth metadata

Why

A successful probe already receives the durable OpenClaw device token. Onboarding must save that sealed bundle with the runtime or the token lifecycle is lost before the first pooled connection.

Stack

Depends on #708, #707, #706, and #705.

Verification

  • pnpm test -- src/app/api/runtimes/route.test.ts src/app/api/runtimes/probe/route.test.ts
  • pnpm exec tsc --noEmit --pretty false --incremental false
  • pnpm exec eslint src/app/onboarding/page.tsx src/app/api/runtimes/route.test.ts
  • pre-push pnpm typecheck
  • pre-push pnpm build
  • git diff --check

@rogerchappel
rogerchappel changed the base branch from codex/seal-openclaw-probe-auth to main July 20, 2026 07:31
@rogerchappel
rogerchappel marked this pull request as ready for review July 20, 2026 07:32
@rogerchappel
rogerchappel merged commit 7dc1e20 into main Jul 20, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant