Repository navigation
Share Slack context and reply handling with durable agent hosts - #25
Merged
Merged
Conversation
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
1 participant
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.
A host with its own durable Slack inbox should not have to reimplement event routing, thread context, or reply payloads. Previously, normalized events and history discarded Slack link previews, so a reply such as “do we support this?” could lose its parent announcement.
This adds
SlackHostfor authenticated host-owned ingress. Shared Rust code preserves quoted mentions, projects previews and file references, reads bounded paginated context, and reports partial or unavailable coverage. Current signed-event previews survive unavailable history and can be retained without reading earlier DM messages. Python bindings provide an authorized request callback; authentication, persistence, and retries remain with the host.message_requestalso prepares validated post/update payloads using the existing renderer, including safe Slack flags and clearing stale rich content. Existing Slack channel APIs remain supported and share event/history interpretation with the host API.Moyai adoption: BerriAI/moyai#523. Merge this SDK change before the consumer PR.
Validation: 570 Python tests and 77 Rust workspace tests pass; whole-repository Ruff, public Python typing smoke, Cargo formatting, Clippy (
--workspace --all-targets -- -D warnings), no-default-features and Slack-example checks pass. Node package build/typecheck, 10 tests and package smoke pass; Node examples typecheck and 4 tests pass. Verified conflict-free against current main2d4f1ee.Local Rust checks used 1.95. The existing minimum-version CI job verifies 1.88; that toolchain is unavailable locally.