Uh oh!
There was an error while loading. Please reload this page.
feat(console-ai): make the "Proposed plan" card an actionable confirm gate - #1884
Merged
Conversation
… gate The plan card (#1875/#1878) was read-only — the user had to TYPE "build it" to proceed. Add a one-click gate, matching Airtable Omni's "Build it": - "Build it" button sends an approval message via the existing onSendMessage channel (same path as suggestion chips) → the agent proceeds to apply_blueprint. It's context-aware: when the plan still carries open questions, approval sends an accept-defaults message so a click never silently drops them. - "Adjust" button focuses the chat input so the user types changes in their own words (no canned answer forced on an open-ended plan). - Falls back to the existing static hint when the host hasn't wired onSendMessage. Localized labels + messages on both surfaces (AiChatPage t(), ConsoleFloatingChatbot locale; en + zh 开始搭建/调整方案). Per-question canned quick-replies are intentionally NOT added: propose_blueprint returns free-text questions with no structured options, so "Build it (with defaults)" + type-to-answer is the honest affordance. A structured questions:[{text,options}] from the backend would enable per-question chips later. Verification: 3 new render tests (approve-with-defaults when questions exist, plain approve when none, hint-fallback when sending unwired) — ChatbotEnhanced 40 green; plugin-chatbot + app-shell type-check clean. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The latest updates on your projects. Learn more about Vercel for GitHub. |
Contributor
✅ Console Performance Budget
📦 Bundle Size Report
Size Limits
|
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 freeto 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.
Why
The plan card (#1875/#1878) was read-only — to proceed the user had to type "build it". This adds the one-click confirm gate, matching Airtable Omni's Build it.
What
onSendMessagechannel (the same path suggestion chips use) → the agent proceeds toapply_blueprint. Context-aware: when the plan still has open questions, approval sends an accept-defaults message so a click never silently drops them.onSendMessageisn't wired. Localized on both surfaces (AiChatPaget(), ConsoleFloatingChatbotlocale; en + zh).Per-question canned quick-replies are intentionally not added:
propose_blueprintreturns free-text questions with no structured options, so Build-it-with-defaults + type-to-answer is the honest affordance. A structuredquestions:[{text,options}]from the backend would enable per-question chips later.Verification
3 new render tests (approve-with-defaults when questions exist; plain approve when none; hint-fallback when sending unwired) — ChatbotEnhanced 40 green; plugin-chatbot + app-shell type-check clean (forced, non-cached).
🤖 Generated with Claude Code