fix(app): preserve conversational intent and plan App-first continuity - #5064
Open
huangruiteng wants to merge 3 commits into
Open
huangruiteng wants to merge 3 commits into
huangruiteng wants to merge 3 commits into
Conversation
Signed-off-by: huangruiteng <14976749+huangruiteng@users.noreply.github.com>
Signed-off-by: huangruiteng <14976749+huangruiteng@users.noreply.github.com>
Mirror the chat action normalization limits in the explicit Task and Goal forms so an over-long draft is explained and cannot be previewed, instead of failing at the preview boundary. Signed-off-by: huangruiteng <14976749+huangruiteng@users.noreply.github.com> Co-authored-by: Cursor <cursoragent@cursor.com>
This was referenced Sep 25, 2026
This branch has not been deployed
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
1 participant
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.
Problem and result
An ordinary question such as “解释一下 monitor 的工作原理” was intercepted by browser keyword rules and turned into a scheduling preview. Goal creation, Todo changes and assignment had the same parallel intent parser. Free text now reaches the selected conversation intact; the conversation Agent owns interpretation and existing runtime/action review owns execution.
Explicit Goal, task and scheduling controls use editable forms and the existing reviewed preview/apply path. They preserve unsent chat text, validate fields and keep configuration on preview failure. Goal permissions are selected explicitly, preserving the existing workspace-write-on-confirmation default; boundary prose no longer silently sets permissions. Status-only shows a labelled snapshot. Converting a reply to a task preserves its text for review instead of extracting a sentence by keywords.
Product direction
The App-first integration RFC connects the overall roadmap, presentation, semantic handoff, TS migration and golden queries. Managed and attached work should continue inside LoopX with one execution driver, truthful activity, steering/stop/recovery and results returned to the original conversation. Generic async inbox work reuses existing coordination owners; Lark keeps provider-specific transport concerns. Public visual research informs hierarchy, not runtime claims.
This PR qualifies the entry repair, not full Agent task completion, attached-host continuity or live two-cycle team collaboration. Those remain explicit planned acceptance. No backend authority or persisted message contract changes.
Validation
conversation-input: ten Chinese/English/quoted/compound requests, scoped Chat delivery without manufactured actions; explicit forms, invalid input, failed preview recovery, preserved chat draft, Escape and 390px layout.typed-actionsbrowser scenario: Goal creation/apply/readback, task operations, Heartbeat activation gate, scheduling and semantic protected-action preview.chat-recoveryscenario, including images and refresh recovery.Visual review: the initial home/navigation composition is unchanged. Forms appear only after explicit controls; desktop and narrow views retain the Goal identity, necessary fields, review/cancel and visible failures. Whole-viewport checks retain the original conversation behind the form. Browser scenarios generate reproducible visual evidence.
Future-facing pass: retired the browser intent classifier and magic composer templates, kept the structured Todo parser at its owning editor, and reused the existing action service. No second dispatcher or inbox store.