Add channel remote safety gate#1768
Merged
Merged
Conversation
tpae
approved these changes
Jul 1, 2026
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
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
Adds a provider-neutral remote safety layer for Agent Channels before live Discord, Slack, Telegram, or JSON adapters dispatch into an agent loop.
What changed
ChannelRemoteSafetyPolicyandChannelRemoteSafetyGate.sharedfor remote receive/reply/Computer Use handoff flows.ChannelVerifiedReplyTokenValidationwrapper so remote safety requests use reply-token validations produced byChannelReplyTokenService.Validation
git diff --checkswiftlint lint --quiet Packages/OsaurusCore/Models/Channels/ChannelRemoteSafetyPolicy.swift Packages/OsaurusCore/Services/Channels/ChannelRemoteSafetyGate.swift Packages/OsaurusCore/Services/Channels/ChannelReplyTokenService.swift Packages/OsaurusCore/Tests/Channels/ChannelRemoteSafetyGateTests.swiftOSAURUS_DISABLE_KEYCHAIN_FOR_TESTS=1 OSAURUS_TEST_ROOT=/tmp/osaurus-channel-remote-safety swift test --package-path Packages/OsaurusCore --filter ChannelRemoteSafetyGateTestsOSAURUS_DISABLE_KEYCHAIN_FOR_TESTS=1 OSAURUS_TEST_ROOT=/tmp/osaurus-channel-security swift test --package-path Packages/OsaurusCore --filter ChannelSecurityTestsOSAURUS_DISABLE_KEYCHAIN_FOR_TESTS=1 OSAURUS_TEST_ROOT=/tmp/osaurus-channel-substrate swift test --package-path Packages/OsaurusCore --filter AgentChannelAsyncSubstrateTestsOSAURUS_TEST_ROOT=/tmp/osaurus-channel-remote-safety-keychain swift test --package-path Packages/OsaurusCore --filter AgentManagerLifecycleNotificationTests/deleteSweepsPerAgentKeychainSecretsNotes
ChannelRemoteSafetyGate.shared.make testwith Keychain disabled hit the expected keychain-specific lifecycle failure; the isolated keychain test passed without the disabled-keychain flag.make testpass was started without the disabled-keychain flag but was interrupted after a prolonged local stall, so this draft does not claim full local-suite green evidence yet.