Push notification when a remote/cloud-agent session needs input#4605
Open
iscekic wants to merge 2 commits into
Open
Push notification when a remote/cloud-agent session needs input#4605iscekic wants to merge 2 commits into
iscekic wants to merge 2 commits into
Conversation
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.
Summary
Enables push notifications when a Kilo session (remote CLI or cloud agent) needs user input.
REMOTE_SESSION_ATTENTION_PUSH_ENABLEDtotrue, enabling the existing remote-session attention push path for active CLI sessions.question.asked/permission.asked) and dispatches a push notification when such an event occurs on a cloud-agent-web session, gated by presence (suppressed if a client is actively viewing the session) and session/child-session identity checks.Both slices are additive and raise-only: there is no resolve/clear push, no outbox, scheduler, alarm, or migration. Push payload
statusremains'completed'for needs-input notifications, matching existing deployed-schema expectations (#4445).Testing
services/session-ingest: full suite green (449 passed, 5 skipped), typecheck, lint clean.services/cloud-agent-next: full suite green (2276 passed, 3 skipped), typecheck, lint clean.xcrun simctl push) for both payload shapes. Real APNs-to-physical-device delivery and live LLM-triggered question events are not verifiable in the local dev environment (missingEXPO_ACCESS_TOKEN, no deterministic interactive-prompt harness) and are documented as accepted limitations, consistent with prior related work (feat(mobile): notify when agent sessions need input #4545).No mobile app code changes are included; this is a backend push-trigger feature only.