Repository navigation
chore: Cursor messaging: enable context inject - #845
Merged
Merged
Conversation
getappz
marked this pull request as ready for review
October 3, 2026 07:39
|
Warning Review limit reachedEnable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. Next included review available in 3 minutes. View limit detailsLimit details: You’ve used all 2 included reviews currently available. Your 52 included PR review attempts over the past 7 days set your current allowance at 2 reviews per hour. Review configuration: ⚙️ Run configuration
📒 Files selected for processing (5)
Comment |
Owner
Author
|
Claiming self-repair for |
Owner
Author
supervisor — CI self-repair dispatchedFailing checks: clippy. Please investigate and push a fix. job: bVyO2meBJeJH4sTQX3lq6 |
added 2 commits
October 3, 2026 14:26
Co-authored-by: Cursor <cursoragent@cursor.com> Agentflare-Agent: cursor Agentflare-Branch: task/320-cursor-messaging-enable-context-inject Agentflare-Item: 320
Drop unused agent arg from sync_with_take, scope sync_with to tests, and fix orphaned PostToolUse docs so CI clippy is green. Co-authored-by: Cursor <cursoragent@cursor.com> Agentflare-Agent: cursor Agentflare-Branch: task/320-cursor-messaging-enable-context-inject Agentflare-Item: 320
getappz
force-pushed
the
task/320-cursor-messaging-enable-context-inject
branch
from
October 3, 2026 08:56
ae29aa3 to
fe1544a
Compare
getappz
enabled auto-merge (squash)
October 3, 2026 08:59
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.
Implementing Cursor context inject for
host_injects_context. Checking skills and current branch state first.Existing uncommitted changes on the branch — reviewing them against item #320 and#319dependency.Uncommitted work looks mostly done; fixing duplicate#[test]attrs and finishing verification. lean-ctx DB is readonly — falling back to native read/search.Fixing orphaned tests, then checkingpost_tool_useemit paths and compiling.#319 is done. Retrying the test attribute fixes with smaller edits.Running fmt and targeted tests in the foreground.hook_messages.rswas corrupted by lean-ctx output — restoring from git and re-applying the real changes.Re-applyinghook_messages.rschanges from the earlier diff onto the restored HEAD file.The patch failed on a missing semicolon insync_with— fixing and reapplying.All 18hook_messagestests passed. Fixing the unusedagentwarning, then running the parse tests.Status: done —3aa9f35ontask/320-cursor-messaging-enable-context-injectWhat changed
"cursor"tohost_injects_contextMailSurface/takes_mail_on: take mail only on Cursor inject surfaces (sessionStart,postToolUse,stop); hold onbeforeSubmitPrompt/ allow-pathpreToolUseadditional_context, stopfollowup_messagepostToolUse(PendingCursorMail); parseconversation_id/workspace_rootsTests (foreground):
cargo fmt --all;cargo test --bin agentflare hook_messages(18 ok);accepts_cursor+ related parse tests (4 ok)Concerns
beforeSubmitPromptstill cannot carry non-mail prompt context (optimize/memory) — messaging only on the three inject surfacesDone. Commit3aa9f35ontask/320-cursor-messaging-enable-context-inject: Cursor is inhost_injects_context, with inject onsessionStart/postToolUse/stopand mail held on surfaces that can’t inject. Unit tests forhook_messagesand the Cursor parse paths passed.Opened by
cursoron flared:51bb8de6c33b for item #320 via agentflare.