feat(design): resume conversations and repair document tool schema - #178
Merged
Conversation
filipeforattini
enabled auto-merge (squash)
September 9, 2026 00:05
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.
Add
/design-opento resume an existing Design conversation through the same searchable modal pattern as/sessions. The picker shows prototype names, conversation titles and state, groups prototypes owned by the same conversation, and preserves its history and current agent. Design conversations that have not created a document yet remain discoverable. The modal explains that/design-reviewopens the preview after resuming.The authenticated Design list is scoped to the current workspace and excludes archived or deleted sessions. Empty, loading, search-empty and HTTP error states stay inside the modal.
Also repair
design_document's provider schema: advertise an object with a required action and explicit invocation guidance, then decode into the discriminated union before executing. TUI and Core share the contract. An HTTP regression through the actual OpenRouter SDK fails on the previous rootanyOfschema and passes on this implementation. The exact cause of the reported GLM session's repeated{}calls remains unconfirmed without its trace.Validation:
bun typecheckpasses in TUI, Schema, Core and Redcode.The README now walks through the app-admin dark-mode example from prototype to browser feedback, approval, planning and implementation. It includes a workflow diagram, current command behavior and release availability, and separates regular TUI instructions from the optional Design terminal, where
/resumehas a different meaning.