Repository navigation
feat(lastcode): integrate resumable actions with composer stack - #180
Merged
lastobelus merged 3 commits intoSep 1, 2026
Merged
Conversation
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.
Resumable Actions still used the deleted legacy composer attachment model, while annotations and message-sync state competed for the same space outside the restored upstream composer stack. Completed Actions also flattened their structured findings into plain text.
This moves live Actions, thread annotations, and message-sync status onto the shared composer banner stack. Expanded live items detach above the composer; completed Action results remain collapsed, outcome-colored, expandable cards in the thread on web and mobile. The stack now expands through pointer or focus interaction and wraps multi-action controls below content on narrow screens. The old Action drawer, annotation post-it, sync pill, and their legacy styling are removed rather than restored.
Validation:
5728224b8d0e3a6f23d681ccf454e994b04972daagainst398a2ede369486a9f791019910228e29557ff749Implemented by GPT-5.6-sol in the T3 Code Codex harness.