Repository navigation
Relay: non-English confirm replies are dropped, and docs still describe the countersign lock #2670
Erwin19919
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Two Relay observations from a fresh 8.761.0 install used by a German-speaking principal.
1. Confirmations only accept English words.
affirmative()inhooks/lib/texting-guard-core.ts(around line 1811) matchesyes,ok,go, 👍 and similar, but notja,jo,mach,losor other non-English replies. When the guard held a delete for an in-thread confirm, the principal replied "Ja". The bridge loggedconfirm_supersededand the held action was dropped, so the action never ran and the reason was invisible to the user. Idea: let the affirmative/negative word lists be extended from USER config (e.g. aconfirmWordsfield instate/bridge-config.json), or ship a small set of common languages, and when a short reply supersedes an open confirm, say so in the thread ("I didn't read that as a yes; reply 👍 to approve").2. The setup docs describe a lock the code no longer has.
LIFEOS/DOCUMENTATION/Setup/Relay.mdand the shippedUSER/RELAY/ISA.md(ISC-4) say the line starts locked and that writes wait for the countersign. InLIFEOS/RELAY/bridge/session.tsadmit()every admitted sender is unlocked on each inbound forPRINCIPAL_UNLOCK_MS, and a countersign text is swallowed as a "retired authentication phrase". On this install a texted file creation ran with guard reasonunlockedbefore any countersign. Destructive, send and code-reading actions are still held for an in-thread yes, which works. Either the docs and the ISA template should describe the current model (pinned allowlist as the authentication, confirm for destructive actions), or the countersign lock should be an opt-in setting for principals who want writes held too. As a user I'd like the opt-in.The setup flow also walks the user through
Countersign.ts set, which suggests it still matters; a note on what it does today would avoid confusion.Context
LifeOS 8.761.0 · macOS 26.5.1 (arm64) · claude-code
All reactions