Zayn Jarvis 58139b46ad fix(openclaw): make peer scope optional again and default to none (#4546) ...

* fix(openclaw): make peer scope optional again and default to none

Peer routing became an implicit default and then stopped being offered at
all. #2626 flipped the plugin default from peer_role=none to assistant, and
--peer-role example it documented. The flag still exists in the setup command
and in the installer, but nothing on the guided install path mentions it, so
a user installing through the skill gets assistant scoping with no visible
way to choose otherwise.

Restore the choice and put the default back to none:

- default peer_role is none again in config.ts, the setup command and the
  setup helper, so memories land under the OpenViking user unless the user
  asks for separation
- the install skill asks for the memory scope again and documents all three
  values, and its setup/installer invocations expose --peer-role
- reword the option everywhere in terms of what the user gets ("one shared
  memory" / "a separate memory per assistant" / "a separate memory per
  sender") instead of "peer identity mode"

peer_role=assistant and peer_role=person are unchanged for anyone who has
them configured; only the default and the wording move.

* fix(openclaw): rename person peer role to sender

2026-09-04 15:18:48 +08:00

..

identity-routing.ts

fix(openclaw): make peer scope optional again and default to none (#4546)

2026-09-04 15:18:48 +08:00

memory-uri.ts

feat(uri)!: remove uid-less current-user shorthand in favor of viking://~ (#4196)

2026-08-21 19:00:19 +08:00