[Feature] Native Slack task cards for Fast delegations - #1431
Draft
mrubens wants to merge 11 commits into
Draft
Conversation
- Wire card callbacks by the liveTaskStream payload flag for every payload kind (Fast children run as StandardTask; resumes as SnapshotResume), replacing the SlackAppMention-only wiring - Serve card stream data to workers through runScoped SDK endpoints; sandboxed workers cannot reach control-plane Redis - Key stream data by task id so resumes keep updating the same card - Inherit liveTaskStream across Fast-child snapshot resumes - Fit task_update chunks to Slack's 256-char limit before sending and log response warnings; oversized chunks were silently dropped, rendering the card as an empty message - Settle the card on Completed in onExit as a fallback when the completion event is lost or its Slack call fails
…kickoff - Start the card in_progress: Slack's timeline view does not render a pending-only stream, which delayed card visibility until the worker's first update (~sandbox boot time) - Emit one timeline task entry per todo with per-todo ids and statuses so the card shows the checklist progressing, with only changed entries re-sent per todo_update - Finalize outstanding todo entries when the stream settles so no row is left spinning - appendTaskStream/stopTaskStream accept multiple task entries per call
The Slack client does not render a stream whose only content is the opening task_update chunk (no warnings, chunk accepted); the card only appeared when the worker's first append arrived. Re-appending the same entry right after chat.startStream makes the card visible at kickoff.
'plan' display mode renders todo entries as rows inside a single card instead of separate sequential spinner cards.
…ckmarks - plan_update chunk carries the task title as the card header, fixing the duplicated-title rows - One active row shows the current step with the spinner and the View task link; completed todos accumulate as checkmark rows sent once each, so exactly one row is ever animated - Completion settles the active row to 'Task completed' with the real output text - Drop the assistant thread status for Fast turns: Slack replaces custom status text with its own rotating 'Generating response…' placeholders
Contributor
… task cards - The full todo checklist is emitted upfront in plan order, so rows flow top to bottom and check off in place; rows stay unchecked until completed, keeping the active row as the only animated one - Narrative and tool events feed a rolling transcript rendered as the active row's regular-weight details text under the short bold title - Relax per-field caps (details 3000 / output 4000): the surface demonstrably renders large card content, and Slack response warnings are logged if a chunk is ever dropped
Slack accumulates task-card sources per append instead of replacing them, so the repaint append and worker updates no longer re-send the link.
![roomote-community[bot]](https://avatars.githubusercontent.com/u/211522643?s=60&v=4){kind=small}
…view Rows appear in start order once a step has actually begun (unchecked, no animation) instead of rendering the whole pending checklist upfront.
One entry per card: the task title stays constant as the bold header, the latest progress update (current todo with progress, narrative text, waiting state) renders as regular-weight details, and completion settles the card with the run's full output. Drops the row checklist and the plan container; timeline mode renders a single entry as one card.
Slack appends each chunk's details to the entry body instead of replacing it (same as sources), which duplicated the launcher's opening line. Each update is now a newline-prefixed delta, consecutive duplicates are skipped, the repaint append carries no details, and the length cap preserves the delta's leading newline. The card body naturally accumulates a sequential transcript.
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.
Fast-delegated tasks now stream a native Slack agent task card into the parent thread, showing live progress instead of a static kickoff link.
What this does
chat.startStream, plan display mode) alongside the parent-owned kickoff: the card header carries the task title via aplan_updatechunk, and a single active row shows the current step with a spinner and a View task link.liveTaskStreampayload flag is inherited across snapshot resumes, so resumed runs keep updating the same card.StandardTask), with anonExitfallback that settles the card even if the completion event is lost.task_updatechunks are size-fitted and Slack response warnings are logged, so silently dropped chunks are visible.Still iterating (WIP)
detailsunder the bold row title)