Repository navigation
Render live Codex conversations - #4
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
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
Render the selected Codex thread's live conversation in the Figma v2 center work area from AISuite's current immutable frontend State.
Base SHA:
1599c5913fa8860a30687248af15836f67f7be8eDepends on AISuite draft PR #20, which scopes provider item identity by thread and turn so repeated full reads remain valid on one observer session.
Public AISuite APIs used
client::State::threads(),thread(...),turn(...), parent-scopeditem(threadId, turnId, itemId), andpendingRequests()ThreadState::orderedTurnsandTurnState::orderedItemsclient::Threads::read(typed::ThreadReadParams{includeTurns=true}, ...)to populate canonical State; operation results are not rendered or retainedclient::itemSemanticView(...)withAgentMessageSemanticView,CommandExecutionSemanticView,FileChangeSemanticView,ToolCallSemanticView,WebSearchSemanticView,CollabAgentToolCallSemanticView,PlanSemanticView, andSubAgentActivitySemanticViewclient::tokenUsageView(...),failureView(...),realtimeSemanticView(...), andpendingRequestPresentation(...)Rendering coverage
UserMessage,AgentMessageCommandExecution,FileChange,McpToolCall,DynamicToolCall,WebSearch,CollabAgentToolCall,Plan,SubAgentActivityReasoning,ContextCompaction,EnteredReviewMode,ExitedReviewMode,HookPrompt,ImageGeneration,ImageView,SleepSequential-read repair
UI scope
Live: selected-thread header, canonical turns/items, user/Codex messages, lifecycle, current-turn summary, typed activity, token/failure/realtime/truncation presentation, and
stateChanged()rerender with near-bottom follow.Intentionally non-functional/demo: composer actions, thread mutations, approvals/controller ownership, right Inspector preview, and shell-level deterministic status decoration outside the center.
Validation
cmake --build build --parallel 28: passeditem-1identities on one persistent observer connectiongit diff --check: passed in both repositories1, backend connectionconn=1:019ffbed-6412-7a51-92ee-5b8660e730cc(“CodexUI III”): request 2 completed, 30 items019ffba3-8dd9-7971-8a33-be6cdee746d5: request 3 completed, 2 items; no stale A widgets019ffb56-7e8a-7bd3-8fec-d4b4cfe40760(“CodexUI II”): request 4 completed, 8 items; no stale B widgetsQ3 remains read-only and adds no controller acquisition, prompt sending, new thread, interrupt/stop backend operation, approvals, manual protocol handling, transport change, second canonical State store, generic Qt model hierarchy, or SNode.C change.