Routing and offline queue between the local model and Copilot
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 46/100
Research direction
This issue is part of #1170 and depends on offline queuing in #1172; start by reading those issues and locating the routing and queue entry points in the repository. Implement the experiment outcome: send light PRs to local advisory review, keep heavy PRs on Copilot, and run Copilot alongside local review for light PRs. Done means offline light reviews queue until the Mac returns, with no Copilot fallback or timeout.
Written by the indexing model from the issue text.
Description
Part of #1170.
Outcome
Light PRs get the local advisory review; heavy PRs get Copilot as now. During the experiment Copilot also reviews light PRs, so the two can be compared.
If the Mac is asleep or offline, light reviews queue until it is back (#1172). There is no Copilot fallback and no timeout to Copilot Lite.
Notes
- Decision 2026-10-23. Copilot failure or quota fallback to the local model is out of scope for the experiment; revisit after the usage report (#1176).
- Dominant language
- Python
- Stars
- 1
- Forks
- 0
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 43
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
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.
More from akasper/plate
-
Documentation
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
area:docs Task
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area:cli Bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
area:cli Bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
need:refinement status:stub
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
vllm-project/vllm#64845 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
dekobon/big-code-analysis#1729 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
pydantic/pydantic-ai#12091 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100