Repository navigation
fix(cli): drop the unwritten evolve spec from demo --algorithm next - #1151
Merged
Merged
Conversation
demo --algorithm NAME ended with evolve agentdescent.NAME.spec.json, but that file is only written later by algorithms run. Following the footer, --json next, or MCP demo next therefore exited 2. Keep algorithms run as the real-data step; it already prints evolve with the absolute path. Closes #1145.
Collaborator
Author
|
Review (Birfy) Tip SHA: c6a6e3c
|
Birfy
enabled auto-merge (squash)
November 17, 2026 16:28
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
demo --algorithm NAME(and the MCPdemotool /--jsonnext) ended withagentdescent evolve agentdescent.NAME.spec.json. That file does not exist until the user later runsalgorithms run, which writes it into the cwd at that time. Following the suggested command therefore exits 2.This removes that
evolvestep from the sharedown_stepslist (human footer,--jsonnext, and MCPdemo). The footer still points atalgorithms run NAME … --rounds 1 --workers 1, which plans and then printsevolvewith the absolute path it just wrote.demowithout--algorithmis unchanged (init→doctor→plan).Closes #1145.
Tests
tests/test_demo.py:test_demo_algorithm_next_steps_keep_the_algorithmnow asserts the unwritten evolve path is absent from the human footer and--jsonnext, whilealgorithms run NAMEremains. The evoskill human and JSON rows pin the same.tests/test_mcp.py: MCPdemo(algorithm="gepa")anddemo(algorithm="evoskill")assert the samenextshape.Checklist
changelog.d/1145-demo-algorithm-next-evolve.md