Let Drive take phone tasks over one ntfy topic - #6
Merged
Merged
Conversation
Handoffs still ping the phone; inbound text on the same topic starts or steers the Phone thread, or answers a pending challenge. Drive subscribes from now and skips seen message ids, so a restart never replays the topic's cached backlog.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What and why
Drive can now run tasks sent from a phone over a single ntfy topic: inbound text starts or steers the
Phonethread, or answers a pending handoff; Drive posts Working and the result back to the same topic. Off unlessCASE_NTFY_CHAT=1plus a topic and a box key. The listener subscribes from now and skips seen message ids, so restarts never replay the topic's cached backlog. README documents topic setup (the name is the credential) and the Android/iOS send paths.Checklist
CLA-SIGNERS) — see CONTRIBUTING.mdSPDX-License-Identifierof their directory.venv/bin/python tests/test_lifecycle.py(and the others in CI)Touches credentials?
No vault, link-token, or injection paths touched. New surfaces:
CASE_NTFY_TOKENgoes out only as a bearer header to the configured ntfy server, andCASE_DRIVE_API_KEYstays in theuicontainer env and goes only to the configured provider. Case-originated ntfy posts are tagged and ignored on the way back in, and cased refuses to answer-listen when the answer topic equals the alert topic (loop guard).Made with Cursor