Customize Slack in-flight response status#1362
Open
cyrusagent wants to merge 2 commits into
Open
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
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
Implements Cyrus-branded Slack in-flight status for chat sessions and adds Slack stream helpers that keep each stream in a single mode.
assistant.threads.setStatuswith Cyrus-specific status/loading copy when a Slack turn starts or receives a streamed follow-up.chat.startStream/chat.appendStream/chat.stopStreamhelpers with runtime guardrails for markdown-vs-chunks mode mixing and required channel recipient fields.Validation
pnpm buildpnpm typecheckpnpm test:packages:runpnpm lintpnpm --dir packages/slack-event-transport exec vitest run test/SlackMessageService.test.tspnpm --dir packages/edge-worker exec vitest run test/chat-sessions.test.tsapps/f1/test-drives/2026-07-03-cypack-1367-slack-inflight-status.mdNotes
F1 validates the Slack chat handler path but cannot visually confirm Slack-rendered assistant status because it uses synthetic channels. A live Slack thread remains the final manual presentation check.
Linear: https://linear.app/ceedar/issue/CYPACK-1367/customize-cyrus-slack-in-flight-response-status-and-streaming