Report each TUI publication stage in the live status - #168
Merged
nishu-builder merged 1 commit intoAug 31, 2026
Conversation
Publishing previously showed one generic status for its whole pipeline: the thread set "fetching the selected PR base" once, and after the preparation turn completed, the sidebar and activity row sat on "completed <hash>" while the branch push and gh PR lookup ran. Now both publish flows emit a status per stage — fetching the base tip, sending the base to the caos server, the preparation turn, validating the prepared workspace, pushing the branch, and finding or opening the PR — and a tool running inside the preparation turn shows through with its own verb instead of hiding behind "Publishing". The gh half of publish_conversation_pr is split into find_or_open_conversation_pr so the flow can report the branch push and the PR lookup separately. Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019FKeyxNMPfqcUR2Ts9ghqq
This was referenced Aug 28, 2026
nishu-builder
deleted the
claude/pr-publishing-caos-agent-mil3g8-1-status
branch
August 31, 2026 19:55
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
2 participants
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.
Independent PR based on
main(replaces #159, the last member of the original GitHub-managed stack, which cannot be edited or re-based via the API; merges cleanly in any order with #165 and #166).Publishing previously showed one generic status for its whole pipeline: the thread set "fetching the selected PR base" once, and after the preparation turn completed, the sidebar and activity row sat on "completed <hash>" while the branch push and
ghPR lookup were still running.Now:
Ctrl+Pand/publish-branch) send aTurnEvent::Statusper stage — fetching the base tip (named), sending the base to the caos server, starting the preparation turn, validating the prepared workspace, pushingcaos/<conversation>, and finding or opening the pull request.Running… $ cargo test) in the activity row and the sidebar, instead of hiding behind the generic "Publishing" — the publish branch ofrender_live_activity/sidebar_textyields to a running activity.ghhalf ofpublish_conversation_pris split intofind_or_open_conversation_prso the flow can report the branch push and the PR lookup separately (no behavior change in either half).Validation:
cargo test -p caos-clion this branch (140 tests, including two new rendering tests) andcargo fmt --check. The full caos suite (caos-cli run dev/run-testson a stack built from these sources) was run on the merge of this PR with #165 and #166 on currentmain: 46/47 passed — the one failure istests/world-guard, which SPEC ("Building and testing caos") documents as expected when the suite runs against a host stack instead of inside the test container.Generated by Claude Code