Repository navigation
v0.24.0
- New provider: muse (Muse Code): route tasks to
muse/wonder(muse-wonder-1.0, standard tier). orch reads its verdict, tokens and quota windows (session and seven-day), and shows them in the dashboard's Tools, Usage and Quota pages. - Routes from the models your CLIs really have:
orch initandorch startask opencode, agy and codex which models they list and drop packaged routes they do not have, saying what is left unrouted. claude, gemini and muse keep the packaged routes. - Permissions granted by default:
initandstartadd orch's scoped done/block rules to each CLI the project routes to (--no-permissionsto skip).orch runwarns before the first dispatch when a CLI still lacks them. orch doctoris a readiness report: five sections (config, backends, tasks, permissions, environment) and a verdict, either "Ready toorch run." or the first blocker. New checks includetasks.parse,tasks.valid,tasks.readyandvcs.base_branch.--jsonaddssectionandverdict.- Planning by vertical slices:
orch-archandorch-specnow plan each phase as one PRD milestone that starts with a walking-skeleton task, after which the layers run in parallel on disjoint files. Runorch install-skillsafter upgrading to refresh the installed skills. - Dashboard: System › Skills has a "How it works" tab from idea to dispatched tasks, and task descriptions render as markdown with highlighted code.
What's Changed
- feat(providers): add muse (Muse Code) as a dispatch provider (#395) by @hectorcanaimero in #425
- feat(web): a "How it works" skills tab, and task descriptions as markdown with highlighted code (#427, #428) by @hectorcanaimero in #429
- feat(init): discover each installed CLI's models when building model_router.yaml (#397) by @hectorcanaimero in #430
- feat(init,start,doctor): grant orch's basic permissions by default and report readiness (#400, #392) by @hectorcanaimero in #431
- feat(skills): plan each phase as a vertical slice that starts with a walking skeleton by @hectorcanaimero in #432
Full Changelog: v0.23.0...v0.24.0