feat(relaygate): default policy declares inboxDefaults for gid 11

Merged
KH
5d ago
+80-11

Companion to AgentWorkforce/relaygate#43 (an inbox no prefix covers follows its registered agent's group).

Adds to charts/relaygate/values.yaml policy:

inboxDefaults:
  - { gid: 11, mode: "660", acl: [{ gid: 22, perm: "r" }] }

Mirrors the relaycast:inbox/local- rule: device-enrolled Desktop agents (cursor-…, claude-…) in gid 11 can DM each other, the pit may read, never write. Older relaygate images ignore the key (schema strips unknown fields), so this is safe to merge before or after relaygate#43; it takes effect with an image containing it. Deployments with their own policy override must add it themselves (mirror their local- ACL).

Checked: helm lint, and the rendered policy.json parses with relaygate#43's loadPolicyFile.

🤖 Generated with Claude Code


Autofix with [code]smith
Open in [code]smith · Need help on this PR? Tag @codesmith-bot with what you need.


Summary by cubic

Adds inboxDefaults for gid 11 to the relaygate chart's default policy so device-enrolled Desktop agent inboxes (cursor-, claude-, codex-) get the same permissions as the local- rule: mode 660, pit may read, never write. Bumps relaygate to 0.1.10 and agent-relay to 0.7.54, and records both in the self-hosted requirements matrix.

  • The chart default is applied in the template only when policy omits inboxDefaults; it is dropped when policy.groups lacks gid 11 or 22, so a policy override that replaces groups no longer renders a stale entry relaygate would refuse to load.
  • Any inboxDefaults the operator sets that names an undefined gid fails the render, so a restrictive mode never loosens to relaygate's 660 fallback.
  • Older relaygate images ignore the key, so this can merge before or after relaygate#43.
  • Deployments overriding policy should set inboxDefaults to match their own groups, or [] to opt out (desktop inboxes then get 660, same group only); CI checks the default, both drops, the opt-out, and both render failures.