You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Relay: a route registry so apps can receive texts (including reactions and photos) without patching the bridge
#2580
An app that wants to answer texts from specific people has one way in today: edit LIFEOS/RELAY/bridge/index.ts so the bridge's chat dependency sends those senders somewhere else. Every LifeOS update overwrites that file, so the app has to notice the edit is gone and put it back. Two apps doing this would patch the same lines and fight.
The bridge also drops two things from contacts before any app could see them: reactions (tapbacks) and attachments (photos). An app that wants a one-tap rating or a photo of a grocery receipt can't get either.
What would fix it
A small, owner-controlled registry the bridge reads, so an app registers instead of patching:
The bridge, for a direct message from a contact whose handle matches a route:
Applies its existing admission, tripwire and service checks first.
Calls the route's export with (sender, history, content), where content is the text, or a reaction ({ type: "reaction", emoji, target }), or an attachment saved through the bridge's existing ingestAttachment (a path, never raw bytes).
Sends the returned reply. If the module throws or won't import, it replies with its standard "can't chat right now" and never falls through to the general assistant.
A sender who matches no route keeps today's behavior exactly.
Why this shape
The principal approves routes, so an app can't grant itself a sender. Ring rules still decide who is admitted at all.
Updates stop breaking apps, because no app edits system files.
Apps opt into reactions and images one by one, so nothing reaches a module that didn't ask for it.
What an app does until then
The meal planner keeps its idempotent, marked hook with a post-update check() and restore(), and documents that household contacts' tapbacks and photos are dropped (ratings arrive as text replies; receipts come through the installing member's own session).
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
The problem
An app that wants to answer texts from specific people has one way in today: edit
LIFEOS/RELAY/bridge/index.tsso the bridge'schatdependency sends those senders somewhere else. Every LifeOS update overwrites that file, so the app has to notice the edit is gone and put it back. Two apps doing this would patch the same lines and fight.The bridge also drops two things from contacts before any app could see them: reactions (tapbacks) and attachments (photos). An app that wants a one-tap rating or a photo of a grocery receipt can't get either.
What would fix it
A small, owner-controlled registry the bridge reads, so an app registers instead of patching:
The bridge, for a direct message from a contact whose handle matches a route:
(sender, history, content), where content is the text, or a reaction ({ type: "reaction", emoji, target }), or an attachment saved through the bridge's existingingestAttachment(a path, never raw bytes).A sender who matches no route keeps today's behavior exactly.
Why this shape
What an app does until then
The meal planner keeps its idempotent, marked hook with a post-update
check()andrestore(), and documents that household contacts' tapbacks and photos are dropped (ratings arrive as text replies; receipts come through the installing member's own session).Context
LifeOS 8.761.0 · macOS 27.0.1 (arm64) · claude-code
All reactions