Skip to content

Add recipient-scoped service senders for agent notifications - #31

Draft
ishwar00 wants to merge 1 commit into
parasxos:mainfrom
ishwar00:feat/service-senders
Draft

ishwar00 wants to merge 1 commit into
parasxos:mainfrom
ishwar00:feat/service-senders

Conversation

@ishwar00

Copy link
Copy Markdown

A local service currently cannot notify a registered agent without impersonating a live session. Add recipient-owned service grants so an explicitly authorized daemon can send a pointer notice using Postbag’s existing delivery transports.

  • Add service-grant, service-check, and service-send --json, with rotation, expiry, revocation, and recipient-registration binding.
  • Store only hashed tokens in a private atomic sidecar. Keep existing ledgers readable by 2.3.0 clients and mark service letters distinctly.
  • Distinguish definite refusal from unknown submission. Find Codex in common install directories when a service manager has a minimal PATH.

Validation: full suite 686 passed; six new service tests cover credential scope, expiry/rejoin, revocation, sidecar permissions, old readers, and structured refusals. Synthetic reply and expiry notices were received in real Claude Code and Codex sessions through a local daemon fixture. No WhatsApp messages were sent.

Submission remains distinct from agent processing. Service credentials authorize user-role notice delivery to one recipient and should be short-lived; applications should send pointers and retrieve untrusted content through tools.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant