Import from OpenClaw or Hermes
Ódinn can inspect compatible OpenClaw and Hermes installations during onboarding. Imports copy selected material; they do not mutate the source installation.
The recommended path is:
odinn onboardChoose a detected import when the review matches what you intend to copy.
Import OAuth only
Section titled “Import OAuth only”Reuse a compatible OpenClaw OAuth session:
odinn auth import openclawYou can select a provider, profile, or source path with the advanced options shown by odinn help --all.
Imported credentials are copied into Ódinn’s owner-only OAuth store. A successful import still requires a real model verification.
Import framework state
Section titled “Import framework state”Preview an import first:
odinn import openclaw --dry-runodinn import hermes --dry-runApply the reviewed import:
odinn import openclawodinn import hermesUse --auth-only or --skills-only when you need a narrower transfer.
Trust boundary
Section titled “Trust boundary”Imported configuration, skills, manifests, and instructions are untrusted until reviewed. Discovery or copying does not grant capabilities, enable a package, or make its code safe.
Keep the source and destination state directories separate. After import:
odinn doctorodinn onboard --verify --non-interactiveReview imported skills in the Agents and skills area and inspect provider configuration in Providers.
