Envoy 0.2.4 (git_commit bbedb403a9363f012e186a4f9e0d76d321cf4628, build 2026-05-16T15:39:44Z) showed a mismatch between local reported capability state and effective authorization.
Observed
On macOS, local status/MCP reported capability_epoch 1 for a shared space. Messages from the same identity were accepted at epoch 7.
Effective write was verified by sending a test message and reading it back from shared history:
message_id: msg_8785be8c2edbd5b5a7b34c9accdffd1c
cursor: 40
Expected
Diagnostic/status/permissions output should either:
- report the effective capability epoch used for authorization;
- distinguish local cached epoch from relay/effective epoch;
- or warn that local capability diagnostics may be stale and recommend an actual refresh/repair/check command.
Impact
Operators may incorrectly conclude a participant cannot write, or may waste time repairing a client that is still effectively authorized. The safe workaround was to perform a real send/read-back test.
Envoy 0.2.4 (
git_commit bbedb403a9363f012e186a4f9e0d76d321cf4628, build2026-05-16T15:39:44Z) showed a mismatch between local reported capability state and effective authorization.Observed
On macOS, local status/MCP reported
capability_epoch 1for a shared space. Messages from the same identity were accepted at epoch7.Effective write was verified by sending a test message and reading it back from shared history:
Expected
Diagnostic/status/permissions output should either:
Impact
Operators may incorrectly conclude a participant cannot write, or may waste time repairing a client that is still effectively authorized. The safe workaround was to perform a real send/read-back test.