Expand description
ORCH-10 — the profile noun at the OBSERVED tier: one uniform row for
every named, routable config home supercode can see, read from each
harness’s own files and never written.
Four sources, four kinds:
preset— supercode’s owncrate::presets::RESERVED_PRESET_NAMES; the analog of a Codex profile for supercode itself (no home directory).codex_profile—[profiles.<name>]tables in$CODEX_HOME/config.toml, with the top-levelprofile = "<name>"naming the default.hermes_profile—HERMES_HOME/profiles/<name>/directories plus the implicitdefaultprofile (HERMES_HOME itself), routed bygateway.profile_routesinHERMES_HOME/config.yamland partitioned instate.dbby theprofile_namecolumn.openclaw_agent—<openclaw home>/agents/<id>/directories plus theagents.entriesmap inopenclaw.json, routed bybindings[].
Everything here is read-only: no harness home is created, written, or
migrated. A harness with no profile concept is refused with
ProfileError::UnsupportedHarness, never a silent empty list.
Structs§
- Profile
Row - One named config home, uniform across harnesses.
Enums§
- Profile
Error - Read-only profile failures.
- Profile
Kind - Which harness concept a row came from.
Constants§
- HERMES_
DEFAULT_ PROFILE - Hermes’s implicit profile: HERMES_HOME itself, the
profile_name IS NULLpartition ofstate.dband the target when no route matches. - OPENCLAW_
DEFAULT_ AGENT - OpenClaw’s conventional default agent — the id behind the
agent:<id>:mainsession key and theagents/mainconfig home. Used only when no entry declaresdefault: true. - PROFILES_
SCHEMA - Stable row schema shared by Rust, JSON-RPC, the SDKs, and the CLI.
- PROFILE_
HARNESSES - Harnesses that have a profile concept supercode reads, in product order.
Every other harness id is
ProfileError::UnsupportedHarness.
Functions§
- get_
profile - Read one profile by harness and name.
- list_
profiles - List every profile supercode can see, optionally restricted to one
harness. Rows are ordered by harness (as in
PROFILE_HARNESSES) then by name.