Repository navigation
docs: Document Cursor native trace collection for PIG (analyzer 0.3.3+) - #1047
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
promptless
Bot
requested review from
adit-chandra,
frances720,
hawkeyexl and
mattlink
as code owners
September 22, 2026 23:31
2 of 3 tasks
…ive-trace-collection # Conflicts: # src/content/changelog/changelogs/september-2026.mdx
…ive-trace-collection # Conflicts: # src/content/changelog/changelogs/september-2026.mdx
…ive-trace-collection # Conflicts: # src/content/changelog/changelogs/september-2026.mdx
3 tasks done
3 tasks done
This branch was successfully 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
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.
Open in Promptless
Proposed changes
Adds Cursor desktop sessions as a native trace source for Promptless Instruction Governance (PIG). The pages state the analyzer version Cursor needs, what the Cursor collector covers, and what has not been qualified yet. Readers can then enable Cursor collection on a pilot host and confirm it works before they roll it out more widely.
This PR now carries only the Cursor-specific changes on top of
main, after the #1039 installation-guide merge (bc36138). Installation, enrollment, acceptance SQL, and dashboard checks come from #1039 unchanged. Verify your deployment already listscursoras a source onmain.Enroll your hosts: Cursor is now one of the supported host families. Prerequisites: Node.js for the Cursor launcher, and analyzer 0.3.3 or later. Step 1 tells readers to check that the Workers settings page shows Cursor ingestion supported, and states that the default enrollment policy adds Cursor when the analyzer reports support. A new Cursor collection section covers:
sessionStart,stop,sessionEnd,subagentStop) and their 250 ms timeoutPATH, and thecursor-launcher-status.jsondiagnostic--host cursorcommands withCURSOR_PLUGIN_ROOT, including Windowspy -3A troubleshooting row covers Cursor hosts that are enrolled but send no traces.
Trace object and sources: adds the
cursorsource row with its transcript glob, and per-OSstate.vscdbpaths with thePROMPTLESS_CURSOR_DATABASEoverride and the WindowsAPPDATAfallback. Also covers what the Cursor collector exports, its journal location and collection limits (including the 4,096 pending-notification limit), and that Cursor uses its own generated hooks.Supported agents, FAQ, How it works, Key concepts: list Cursor desktop sessions as a native trace source with analyzer 0.3.3 or later, and include Cursor in the
pigplugin targets that carry the host runtime.Changelog: one October 2026 entry, "Collect Cursor sessions as native traces". The first stable analyzer with Cursor support, 0.3.3, was published on 2026-10-07. The September
--deviceentry that the merge brought back is removed again, because docs: Complete the PIG 0.3.6 installation path, from release verification to a verified first session #1039 removed it as unshipped.Source and release evidence
Promptless/pig-deploycatalog/stable.jsonlists 0.3.1, 0.3.3, 0.3.4, 0.3.5, and 0.3.6. 0.3.6 (manifest sha256a4eafe78…, sourcedb79db5) ships analyzer imagesha256:0379f9d7…. Promptless/promptlessops/pig/candidate.jsonrecords that image as built from analyzer source625624a7.625624a7and the 0.3.3/0.3.4 analyzer source59a33727both include the Cursor ingestion merge from #5170 (5488e1f). Both report everyAgentHostvalue, includingcursor, in the check-in'ssupported_trace_sources(pig_trace_analyzer/sync/service.py). The 0.3.1 analyzer (21e72b8) predates #5170. The 0.3.5 image was built on 2026-10-09 from source after #5450, which also follows #5170. That is inferred from the build date and was not checked line by line.main,runtime/pig/policy.pyadds Cursor to the default policy only when the latest worker report includescursor.runtime/pig/routes.pyandWorkerStateCard.tsxshow Cursor ingestion supported on the Workers settings page.pig-toolchainfrom@main(4c02abf).managed_runtime.pyadds the runtime toclaude,codex, andcursorand writes the four Cursor hooks. The other details above come fromdocs/cursor-trace-ingestion.mdand the runtime sources: database paths and override, transcript glob, Python lookup, WAL check, journal limits, and scope exclusions.Qualification status (not claimed as tested)
The source and release support above comes from code, not from a capture test. The toolchain checked the adapter's data format against Cursor desktop 3.19.19, and synthetic tests cover the collector and analyzer contracts. Desktop dogfooding on macOS, Linux, and Windows is still listed as a release requirement. The 0.3.6 owner sign-off also lists live canonical trace analysis as unverified. The docs say end-to-end capture is not yet qualified, and tell readers to pilot one host per OS.
Coordination
Merge #1047 first, then #1125. The #1125 branch contains this PR’s final head (525383f) and resolves the shared-page overlap.
Checklist
Validation:
npm run check(typecheck, MCP and search tests, full build, search build checks) passed.npm run test:smokepassed (28/28).npm run lint:mdanddocmeta validatepassed (131/131). Vale reported no findings on the changed files, for both the collection rules and the canonical and Knowledge Base rules. Every new internal link and anchor resolves in the build output, and the Workers settings URL returns 200.Review requests addressed in this pass
The PR had no human review comments; prior threads were Promptless citation comments, which this pass replaced at the final line anchors. Adit Chandra's refresh request was applied as follows: merged
origin/mainatbc36138(no rebase or force-push); kept #1039's installation, enrollment, acceptance SQL, and dashboard checks unchanged; replaced the "no published analyzer includes Cursor support" hold with the verified requirement (analyzer 0.3.3 or later, current stable 0.3.6); removed the--devicechangelog entry the merge had brought back; and moved the Cursor changelog entry to October 2026 to match when a stable analyzer with Cursor support was published.Trigger Events