You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The v0.8.59 release line now includes work that was originally staged for v0.8.60: provider/model correctness, sub-agent architecture, WhaleFlow workflow authoring, README/site localization, and broader cleanup. Without an execution roadmap, this turns into a flat backlog where an agent can spend time on the wrong layer or accidentally start several heavy sub-agent/workflow changes before the current TUI reliability problems are contained.
This issue is the execution roadmap for the promoted v0.8.59 push.
Promotion note
On 2026-06-11, the open v0.8.60 issues were promoted to v0.8.59 and retitled where they had an explicit v0.8.60 prefix:
This promotion does not mean every item is an equal release blocker. It means the v0.8.59 agent plan should pull these capability foundations forward and execute them in a sane order.
Operating rules for implementation agents
Start with user-visible reliability and invalid defaults before architecture.
Keep PRs narrow: one track or one coherent slice per branch.
When a broad issue cannot be completed in one release-sized PR, land a documented contract, tests, and a compatibility path rather than a half-migration.
Every PR should update the relevant issue with verification commands and remaining follow-up.
Roadmap
Track 0: Contain current v0.8.59 reliability and TUI breakage
Goal: make the app stop feeling stuck, misleading, or computer-heavy during normal usage.
Add scheduler-visible states and backpressure around current sub-agent fanout: queued, starting, model_wait, running_tool, completed, failed, cancelled, interrupted.
Define AgentWorkerSpec / AgentWorkerEvent independent of Ratatui widgets.
Make TUI cards/sidebar consume worker events as a projection only.
Connect WhaleFlow leaves to the same worker contract rather than building a second scheduler.
Add JS/TS workflow authoring as a compile/lowering layer into typed WhaleFlow IR, not as an unsupervised Node runtime.
Exit criteria:
A headless test can run worker lifecycle paths without constructing TUI cards.
The user sees compact workflow progress rather than raw nested sub-agent rows.
Cancellation/backpressure works before, during, and after model wait.
JS/TS-authored workflows validate as typed IR before any worker launches.
Track 4: Clean up user-facing naming, legacy compatibility, and stale issue load
Goal: make the project look coherent after the DeepSeek-TUI -> CodeWhale rename without breaking compatibility.
Normal UI does not expose implementation/tool IDs where a user-facing concept exists.
Legacy DeepSeek paths are documented as compatibility, migrated, or intentionally retained.
Stale issue automation exists before closing old issues in bulk.
Track 5: Docs, website, README, and localization endcap
Goal: make the public story match the product: DeepSeek-TUI history, CodeWhale rename, provider graph, supported/experimental/self-hosted routes, and real multilingual onboarding.
gh issue list --state open --label v0.8.60 should remain empty unless maintainers intentionally reopen the v0.8.60 line.
gh issue list --state open --label v0.8.59 should show all promoted issues and active release work.
For code PRs: run the narrow package tests named in each linked issue, plus cargo test -p codewhale-tui or cargo test -p codewhale-whaleflow --locked when touching those areas.
For docs/localization PRs: verify README links, website route links, provider/model naming, locale navigation, and install commands.
For workflow/sub-agent PRs: manually run a multi-agent prompt and verify queued/running/done/cancelled states without an unreadable activity wall.
Problem
The v0.8.59 release line now includes work that was originally staged for v0.8.60: provider/model correctness, sub-agent architecture, WhaleFlow workflow authoring, README/site localization, and broader cleanup. Without an execution roadmap, this turns into a flat backlog where an agent can spend time on the wrong layer or accidentally start several heavy sub-agent/workflow changes before the current TUI reliability problems are contained.
This issue is the execution roadmap for the promoted v0.8.59 push.
Promotion note
On 2026-06-11, the open
v0.8.60issues were promoted tov0.8.59and retitled where they had an explicit v0.8.60 prefix:web_searchvia SearXNG JSON backend, health checks, and visible statusThis promotion does not mean every item is an equal release blocker. It means the v0.8.59 agent plan should pull these capability foundations forward and execute them in a sane order.
Operating rules for implementation agents
Roadmap
Track 0: Contain current v0.8.59 reliability and TUI breakage
Goal: make the app stop feeling stuck, misleading, or computer-heavy during normal usage.
Primary issues:
Exit criteria:
Track 1: Make provider/model routing factual and API-backed
Goal: stop shipping invalid model IDs, stale provider claims, unknown pricing, and hard-coded model facts.
Primary issues:
web_searchbackend/statusSuggested sequence:
Exit criteria:
Track 2: Unify context budgets, compaction, and stream pressure
Goal: make context/window pressure observable and consistent across model metadata, compaction, output caps, and UI state.
Primary issues:
Exit criteria:
Track 3: Renovate sub-agents into headless workers and workflow orchestration
Goal: move from ad hoc fanout/TUI-shaped sub-agents to scheduler-owned workers, compact UI projections, and authorable workflows.
Primary issues:
Suggested sequence:
AgentWorkerSpec/AgentWorkerEventindependent of Ratatui widgets.Exit criteria:
Track 4: Clean up user-facing naming, legacy compatibility, and stale issue load
Goal: make the project look coherent after the DeepSeek-TUI -> CodeWhale rename without breaking compatibility.
Primary issues:
exec_shellinternal.deepseek/compatibility paths.codewhaleper-folder behaviorExit criteria:
Track 5: Docs, website, README, and localization endcap
Goal: make the public story match the product: DeepSeek-TUI history, CodeWhale rename, provider graph, supported/experimental/self-hosted routes, and real multilingual onboarding.
Primary issues:
Exit criteria:
Recommended first agent packet
If a single implementation agent starts now, execute in this order:
Verification
gh issue list --state open --label v0.8.60should remain empty unless maintainers intentionally reopen the v0.8.60 line.gh issue list --state open --label v0.8.59should show all promoted issues and active release work.cargo test -p codewhale-tuiorcargo test -p codewhale-whaleflow --lockedwhen touching those areas.