Skip to content

Set device-name to agent name + host device in auth flow - #16

Merged
joerj123 merged 1 commit into
mainfrom
device-name-agent-and-device
Jun 11, 2026
Merged

Set device-name to agent name + host device in auth flow#16
joerj123 merged 1 commit into
mainfrom
device-name-agent-and-device

Conversation

@joerj123

Copy link
Copy Markdown
Collaborator

What

Guide agents to set --device-name to their own name + the host device (e.g. Max - Mac Mini) during sign-in, instead of a static placeholder, so the entry in Shop Connections is self-identifying.

Why

The auth flow's device_name is what the user sees in Shop Connections. Today the skill docs use a fixed placeholder (Joey McLobsterface) and the direct-API reference just says <short agent name> — neither tells the agent to use its real name or include the device it's running on. A name like Max - Mac Mini makes connections recognizable and revocable.

Where the agent name lives (per harness)

Harness Agent name stored in
OpenClaw IDENTITY.md (workspace root, Name: field)
Hermes Agent (Nous) ~/.hermes/SOUL.md (persona = identity)

Changes

  • skill/SKILL.md### Auth example now uses --device-name "<your name> - <device>" (e.g. Max - Mac Mini) + one line on where to source the name.
  • skill/references/direct-api.mddevice_name example mirrors the same convention for the manual API path.
  • Added a changeset (patch).

No code changes — the CLI already accepts --device-name and caps it at 40 chars; this is doc/skill guidance only.

Guide agents to pass their own name plus the host device to
--device-name (e.g. "Max - Mac Mini") so the Shop Connections entry
is self-identifying. Document where the agent name lives per harness:
IDENTITY.md (OpenClaw) or ~/.hermes/SOUL.md (Hermes).
@joerj123
joerj123 force-pushed the device-name-agent-and-device branch from 6855fa7 to 51000d8 Compare June 11, 2026 20:49
@joerj123
joerj123 merged commit 72019d5 into main Jun 11, 2026
1 check passed
@PawanP1808
PawanP1808 deleted the device-name-agent-and-device branch June 15, 2026 14:45
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