Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Surface failed AI CLI calls from `generate_with_memory`

Open
  • Is something wrong?
#101 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
python
Domain
ai, cli

Research direction

Start in CoderMind/scripts/common/llm_client.py at generate_with_memory and trace the retry-exhaustion path, then review the /cmind.encode flow in run_encode.py and refactor_tree.py. Reproduce the Claude-backend failure described in the issue; done means the final CLI exit code and concise stderr summary are surfaced after retries instead of an opaque None failure.

Written by the indexing model from the issue text.

Description

When the AI CLI exits nonzero or returns empty output, generate_with_memory catches the failure and returns None after retries (https://github.com/microsoft/RPG-ZeroRepo/blob/f0947723cc07fe10fb0d6b14c8aa837847f57b0d/CoderMind/scripts/common/llm_client.py#L469-L479, https://github.com/microsoft/RPG-ZeroRepo/blob/f0947723cc07fe10fb0d6b14c8aa837847f57b0d/CoderMind/scripts/common/llm_client.py#L527-L528, https://github.com/microsoft/RPG-ZeroRepo/blob/f0947723cc07fe10fb0d6b14c8aa837847f57b0d/CoderMind/scripts/common/llm_client.py#L594-L648). parse_solution_output(None) then raises 'NoneType' object has no attribute 'split' each functional-area iteration; the loop returns an empty plan and AssertionError: functional_areas must not be empty aborts before run_encode reaches its dependency-graph build/save steps, so no dependency graph is saved (https://github.com/microsoft/RPG-ZeroRepo/blob/f0947723cc07fe10fb0d6b14c8aa837847f57b0d/CoderMind/scripts/common/utils.py#L761-L776, https://github.com/microsoft/RPG-ZeroRepo/blob/f0947723cc07fe10fb0d6b14c8aa837847f57b0d/CoderMind/scripts/rpg_encoder/refactor_tree.py#L516-L543, https://github.com/microsoft/RPG-ZeroRepo/blob/f0947723cc07fe10fb0d6b14c8aa837847f57b0d/CoderMind/scripts/rpg_encoder/refactor_tree.py#L581-L585, https://github.com/microsoft/RPG-ZeroRepo/blob/f0947723cc07fe10fb0d6b14c8aa837847f57b0d/CoderMind/scripts/rpg_encoder/refactor_tree.py#L769-L773, https://github.com/microsoft/RPG-ZeroRepo/blob/f0947723cc07fe10fb0d6b14c8aa837847f57b0d/CoderMind/scripts/rpg_encoder/run_encode.py#L89-L92, https://github.com/microsoft/RPG-ZeroRepo/blob/f0947723cc07fe10fb0d6b14c8aa837847f57b0d/CoderMind/scripts/rpg_encoder/run_encode.py#L124-L135).

This reproduced with the Claude backend on a 7-file Python repo. The workspace had a .cmind/config.toml matching the documented cmind init --ai claude layout; cmind init itself was not run. The /cmind.encode command failed on all three functional-area requests. Please surface the final CLI exit code and a concise stderr summary when generate_with_memory exhausts its retries, rather than returning None and failing later. The open PR at https://github.com/microsoft/RPG-ZeroRepo/pull/99 touches llm_client.py, so maintainers could fold this in there.

This issue was AI-generated at the human operator's direction and reviewed by the operator before submission.

Dominant language
Python
Stars
553
Forks
42
No merged PRs in 30d

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/RPG-ZeroRepo

All issues in microsoft/RPG-ZeroRepo

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.