Skip to content

Fix PowerShell chat result flow and prompt example UX - #26

Closed
papanda925 wants to merge 6 commits into
mainfrom
fix/powershell-chat-result-ux
Closed

Fix PowerShell chat result flow and prompt example UX#26
papanda925 wants to merge 6 commits into
mainfrom
fix/powershell-chat-result-ux

Conversation

@papanda925

Copy link
Copy Markdown
Owner

Fixes

Addresses the PowerShell/WPF behavior reported after the priority-one merge.

  • Prompt example is now clearly labeled as optional.
  • Selecting an example no longer overwrites the Question automatically.
  • Added an explicit 質問欄へ反映 button.
  • Sending no longer flashes the current question in the Answer box while waiting.
  • The existing conversation remains visible during the request.
  • API/worker errors no longer force-switch to the Trace tab.
  • Errors stay visible in the Answer tab together with the question.
  • Developer tab now receives HTTP status, elapsed time, request, and response/error body even when the API request fails.
  • Worker preserves the latest request/response metadata for error reporting.
  • Added WPF regression checks for prompt-example behavior and error-display behavior.
  • Updated PowerShell README and getting-started documentation.

No real API key is committed and CI does not make a live paid OrcaRouter request.

@papanda925 papanda925 closed this Sep 2, 2026
@papanda925
papanda925 deleted the fix/powershell-chat-result-ux branch September 2, 2026 19:37
@papanda925
papanda925 restored the fix/powershell-chat-result-ux branch September 2, 2026 19:37
@papanda925
papanda925 deleted the fix/powershell-chat-result-ux branch September 2, 2026 19:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant