orchestrate - needs better configuration overrides for model choice
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 8.2k
- Forks
- 751
- Avg merge
- 12h 1m
- Merged PRs (30d)
- 43
Description
The /orchestrate skill is impressive, however the model schema is not particularly cost efficient - especially compared against this article https://cursor.com/blog/agent-swarm-model-economics - where ops 4.8 paired with composer 2.5 was the most cost effective pairing
It should be possible to define the runtime value of https://github.com/cursor/plugins/blob/main/orchestrate/skills/orchestrate/scripts/models.ts#L23 from a config file or env var (env var probably easier for cursor configuration)
e.g. I've actually had a lot of success on smaller scale tasks (e.g. not an sqlite rewrite) with grok + composer, and that's very cost effective
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the /orchestrate skill and the model definition at orchestrate/skills/orchestrate/scripts/models.ts#L23, then inspect how its runtime configuration is supplied. Done means the model pairing can be overridden through a configuration value or environment variable while the existing orchestration behavior remains available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- ai, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 67/100