feat(agents): multi-channel routing — named channels, multi-inbound, per-channel delivery - #478
Merged
Conversation
…per-schedule/trigger delivery Lift agents from a single DefaultNotifyConnection to many named channels: API types + REST handlers with inbound-uniqueness validation, outbound routing, multi-inbound routeChannelAgent, and portal support (Wiring-tab channel editor, Flow-canvas multi-channel wiring, schedule/trigger channel dropdowns). Design doc: docs/agents-multi-channel.md. Split out of the metering-wip branch (PR #470) so it can land independently. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
mjudeikis
added a commit
that referenced
this pull request
Jul 29, 2026
Metering part 1: census identity + APIExport bootstrap, metering-store workspace with example Plans, org CensusBound condition, hub --enable-metering wiring, Tilt METERING_ENABLED switch, and docs/platform-providers.md. Agents multi-channel work moved to #478. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
Lifts agents from a single
DefaultNotifyConnectionto many named channels, split out of #470 so it can land independently of the metering work:AgentSpecchannel list + inbound/outbound roles, schedule/triggerchannelfield, REST handlers with inbound-uniqueness validation (providers/agents/api,apis/v1alpha1, regenerated CRDs/schemas).routeChannelAgentso users can talk to an agent from several connections.docs/agents-multi-channel.mddesign doc (status: implemented, not yet driven e2e against a running hub).The agents provider is its own Go module; builds and vets clean with
GOWORK=off.Test plan
GOWORK=off go build ./...inproviders/agents🤖 Generated with Claude Code