Skip to content

feat(event-bridge): wire on-relay agents to inbound webhook events (Slack) #1013

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
khaliqgant wants to merge 2 commits into
base: main
Choose a base branch
from
Open

feat(event-bridge): wire on-relay agents to inbound webhook events (Slack) #1013

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a4334a4
feat(event-bridge): wire on-relay agents to inbound webhook events
May 28, 2026
5e1b24b
fix(event-bridge): provision a /slack-scoped gateway token
May 28, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

### Added

- `@agent-relay/event-bridge` connects a long-lived on-relay agent to inbound integration webhook events: it subscribes to the relay gateway for provider file changes (Slack first), injects each new message into a target broker agent, and relays the agent's outbox reply files back through relayfile writeback to the source — no MCP, mount, or credentials required on the agent. The `agent-relay-event-bridge` daemon auto-bootstraps the gateway URL + scoped token from your cloud login (reusing deployed cloud, nothing to run locally), ships an `agent-relay-event-bridge-simulate` harness for a no-cloud loop test, and exposes a provider-adapter contract for adding Linear, Notion, etc.
Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot May 28, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The changelog entry is very long and detailed. According to the repository style guide, changelog entries should be concise and impact-first, preferring one short bullet per user-visible change. Name the package touched and its practical effect.

Suggested change
- `@agent-relay/event-bridge` connects a long-lived on-relay agent to inbound integration webhook events: it subscribes to the relay gateway for provider file changes (Slack first), injects each new message into a target broker agent, and relays the agent's outbox reply files back through relayfile writeback to the source — no MCP, mount, or credentials required on the agent. The `agent-relay-event-bridge` daemon auto-bootstraps the gateway URL + scoped token from your cloud login (reusing deployed cloud, nothing to run locally), ships an `agent-relay-event-bridge-simulate` harness for a no-cloud loop test, and exposes a provider-adapter contract for adding Linear, Notion, etc.
- `@agent-relay/event-bridge`: Adds a daemon to connect long-lived on-relay agents to inbound integration webhook events (starting with Slack) and relay replies back via outbox files, with automatic cloud bootstrap and a local simulation harness.
References
  1. Changelog entries should be concise and impact-first. Prefer one short bullet per user-visible change. (link)

- `agent-relay mcp` recovers from stale Relaycast agent tokens mid-session: a 401 carrying `agent_token_invalid` (or the legacy `Invalid agent token` message) now clears the dead token from the MCP session, returns recovery guidance pointing at `register_agent`, and lets strict-named sessions re-register without a process restart.
- `@agent-relay/sdk` exports `isInvalidAgentTokenError`, `isInvalidAgentTokenToolResult`, and `agentTokenRecoveryMessage` for consumers that need the same detection contract outside the bundled MCP server.
- `agent-relay-broker` adds `is_agent_token_invalid`, `is_agent_token_invalid_anyhow`, and `is_agent_token_invalid_code` on `crates/broker/src/relaycast/auth.rs`, and preserves the upstream `RelayError::Api` code through `relay_error_to_anyhow` so the same recovery signal is available to Rust callers.
Expand Down
Loading
Loading