Skip to content

feat(daemon): add remote messaging control#39

Open
rmacomber wants to merge 1 commit into
get-vix:mainfrom
rmacomber:feat/remote-control-messaging
Open

feat(daemon): add remote messaging control#39
rmacomber wants to merge 1 commit into
get-vix:mainfrom
rmacomber:feat/remote-control-messaging

Conversation

@rmacomber

Copy link
Copy Markdown

Summary

  • add opt-in Telegram and WhatsApp remote control for vixd
  • require explicit feature/config enablement plus sender allowlists before accepting remote prompts
  • run remote prompts in isolated headless sessions and deny unattended permission/plan interactions
  • document remote-control configuration in the README

PR cleanliness

Verification

  • gofmt check passed for changed Go files
  • go build ./cmd/vix ./cmd/vixd
  • go test ./cmd/vixd ./internal/config
  • go test ./internal/daemon -run 'Test(AuthorizedRemoteIDRequiresAllowlist|RemoteSessionOptionsDisableAutomaticPermissions|RemoteUnattendedEventsDoNotAutoApprove|TelegramSendMessageRedactsBotTokenFromErrors|WhatsAppStartFailsWhenWebhookAddrAlreadyBound|TelegramSendMessagePostsChatIDAndText|TelegramGetUpdatesRedactsBotTokenFromErrors|WhatsAppWebhookVerificationAndAllowlist)'
  • go test ./cmd/vix ./cmd/vixd ./internal/agent ./internal/auth ./internal/config

Note: full go test ./... currently fails in pre-existing internal/daemon tests unrelated to this branch: missing testdata/tmp.go fixture expectations in VFS/minify tests and Landlock sandbox environment assumptions. The changed remote-control tests pass.

Add opt-in Telegram and WhatsApp remote control for vixd. Incoming allowlisted messages run isolated headless sessions and reply through the chat provider, with WhatsApp webhook signature verification and Telegram token redaction on provider errors.

Co-authored-by: vix <290354907+vix-agent@users.noreply.github.com>
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