Skip to content

chore: sync with cursor/plugins — fix(pstack): bug-fix/perf/hillclimb defaults to grok 4.6 (#365) - #40

Merged
github-actions[bot] merged 2 commits into
mainfrom
sync/fix-pstack-bug-fix-perf-hillclimb-defaults-to-grok-4-6-365
Sep 12, 2026
Merged

github-actions[bot] merged 2 commits into
mainfrom
sync/fix-pstack-bug-fix-perf-hillclimb-defaults-to-grok-4-6-365

Conversation

@github-actions

Copy link
Copy Markdown

Upstream changes

889ec4b fix(pstack): bug-fix/perf/hillclimb defaults to grok 4.6 (cursor#365)


Automated sync via sync-upstream workflow

poteto and others added 2 commits September 11, 2026 22:40
* fix(pstack): bug-fix/perf/hillclimb defaults to grok 4.6

Point the three code-delegate roles at grok-4.6-fast-xhigh, the slug feature and refactoring already use. The setup-pstack rule template and the playbook default annotations now agree. Judgment, prose, hardest tasks, explainers, synthesizers, and panels stay on Fable 5.1.

Co-authored-by: lauren <poteto@users.noreply.github.com>

* chore(pstack): bump to 0.15.3

Co-authored-by: lauren <poteto@users.noreply.github.com>

* docs(pstack): README blurb names the code roles on grok

The get-started paragraph said precisely-specified code goes to fable 5.1 and only fast mechanical code goes to grok. Bug fix, perf, and hillclimb now default to grok with feature and refactoring, so the blurb lists the five code roles on grok and keeps the hardest changes, prose, and judgment on fable.

Co-authored-by: lauren <poteto@users.noreply.github.com>

* Revert "chore(pstack): bump to 0.15.3"

This reverts commit aeef9b7.

---------

Co-authored-by: Cursor Agent <cursoragent@cursor.com>
…-fix-perf-hillclimb-defaults-to-grok-4-6-365
@github-actions github-actions Bot added the sync Automated upstream sync label Sep 12, 2026
@github-actions
github-actions Bot merged commit f29ad1b into main Sep 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

sync Automated upstream sync

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant