Skip to content
TheChatArchiveThe Chat Archive
GLMz-ai/glm-5.2· unknownHugging Face ibragim-bad/swe_rebench_07_2026_trajectories

ISSUE DESCRIPTION fix(installer): back navigation from Pi-only install shows unrelated…

  1. User

    ISSUE DESCRIPTION

    fix(installer): back navigation from Pi-only install shows unrelated Gentle AI configuration

    Pre-flight Checklist

    • I have searched existing issues and this is not a duplicate
    • I understand that PRs will be rejected if the linked issue does not have status:approved

    📝 Bug Description

    When running the gentle-pi installer from gentle-ai, if I select only Pi as the installation target and then use Back on the next step,
    the installer returns to an unexpected configuration flow.

    Instead of going back to the previous installation target selection, it shows configuration options that do not correspond to the selected
    Pi-only path, such as TDD configuration, multi-agent installation, communication style, and related Gentle AI setup options.

    🔄 Steps to Reproduce

    1. Start the gentle-ai installer.
      2. Select only Pi as the installation target.
      3. Continue to the next step.
      4. Select Back.
      5. Observe that the installer shows configuration screens for TDD, multi-agent setup, speaking style, etc.

    ✅ Expected Behavior

    After selecting Back, the installer should return to the previous relevant step in the Pi-only installation flow, likely the installation
    target selection screen.

    ❌ Actual Behavior

    The installer jumps to unrelated Gentle AI configuration screens, including TDD setup, multi-agent installation, communication style, and other
    options that were not expected after choosing a Pi-only installation.

    Gentle AI Version

    v 1.30.5

    Operating System

    macOS

    AI Agent / Client

    Other

    📋 Affected Area

    CLI (commands, flags)

    💡 Logs / Error Output

    No logs available. This appears to be an installer navigation/state-flow issue.
    

    Additional Context

    This happens specifically when selecting only Pi during installation and then navigating back from the following step.

    Interface

    No new interfaces are introduced.

    ADDITIONAL ADVICE

    Since you are given a git repository, you can use git commands to simplify your work. For example, if you made a mistake and want to revert your changes, you can use git checkout <file> to restore the file to its original state. You can also reset all changes in the repository using git reset --hard command. Additionally, you can use git stash and git stash pop to temporarily save your changes and restore them later. Finally, you can see the changes that you've made (which will be submitted when you call submit) using git status or git diff commands. However you don't need to use git add or git commit before submitting your changes. In fact, submit only submits currently unstaged changes because it uses git diff to get the changes that need to be submitted.

    CHECKLIST

    Before submitting your solution, please go over the following checklist and make sure you've done everything:

    • If an error was reported in the issue description, I have successfully reproduced it.
    • If an error was reported in the issue description, I have confirmed that my fix resolves the error.
    • I have thought about edge cases and made sure my fix handles them as well.
    • I have run existing tests in the repository that might have been affected by the change I made and confirmed that they pass. I want you to list every bullet from this checklist and write your reasoning for why you think you did it or didn't need to.

    Repository has been uploaded and your shell is currently at the repository root. Time to solve the issue!

    (Current directory: /gentle-ai, current file: none) bash-$

  2. GLM Assistant

    Let me explore the repository structure to understand the codebase and find the installer code.

  3. GLM Assistant

    Let me find the screen constants and understand the Pi installation flow.

  4. GLM Assistant

    Now let me understand how the Pi-only flow works. Let me look at the model.go to see how the flow is handled when only Pi is selected.

  5. GLM Assistant

    Let me look at the Back navigation handling for the install flow.

  6. GLM Assistant

    Now let me understand the Pi-only forward flow. Let me look at the confirmSelection and forward navigation logic.

  7. GLM Assistant

    Let me look at the ScreenDependencyTree confirmSelection logic and the screen rendering.

  8. GLM Assistant

    Now let me look at the ScreenDependencyTree confirmSelection (Enter) handling:

  9. GLM Assistant

    Now I understand the issue. For Pi-only:

    • The flow goes: ScreenAgents → ScreenDependencyTree (forward via confirmSelection in ScreenAgents case)
    • On ScreenDependencyTree, Cursor 0 = Continue → ScreenReview; Back option goes to ScreenPreset (the else branch).

    For Pi-only, the Back on ScreenDependencyTree goes to ScreenPreset which was never shown. It should go back to ScreenAgents.

    Let me check the goBack() Esc handling too:

    • For ScreenDependencyTree && Preset != Custom: checks shouldShowOpenCodePluginsScreen, shouldShowStrictTDDScreen, shouldShowClaudeModelPickerScreen. For Pi-only none apply, falls through to linearRoutes Backward = ScreenPreset.

    So both Esc (goBack) and Enter on Back button on ScreenDependencyTree go to ScreenPreset for Pi-only. That's the bug.

    The fix: For Pi-only agents, Back from ScreenDependencyTree should go to ScreenAgents.

    Let me look at the dependency_tree.go screen to understand how Pi-only is rendered and whether there's a Back option shown.

  10. GLM Assistant

    Now let me look at the existing Pi-only tests to understand expected navigation behavior.

  11. GLM Assistant

    Now I understand the flow. The fix needs to handle both:

    1. Esc (goBack) from ScreenDependencyTree for Pi-only → should go to ScreenAgents
    2. Enter on "Back" option from ScreenDependencyTree for Pi-only → should go to ScreenAgents

    Let me check the isPiOnlyAgents function and the selection state. The Selection.Preset for Pi-only - what's its value? Let me check. When Pi-only is selected from ScreenAgents, the components are set to piOnlyComponents() and it goes directly to ScreenDependencyTree without going through ScreenPersona/ScreenPreset. So the Selection.Preset value would be its zero/default value.

    Let me check the Preset zero value.

  12. GLM Assistant

    Now I understand the issue. For Pi-only, Selection.Preset is the empty string (not Custom). The Back navigation from ScreenDependencyTree falls through to ScreenPreset (via linearRoutes and via the else branch), but ScreenPreset was never shown in the Pi-only flow. It should go back to ScreenAgents.

    Let me make the fix in both places: the goBack() Esc handling and the confirmSelection Enter "Back" handling.

    First, the goBack block:

  13. GLM Assistant

    Now let me fix the confirmSelection Enter "Back" handling for ScreenDependencyTree:

  14. GLM Assistant

    Now let me verify the changes and build the project.

  15. GLM Assistant

    Build succeeds. Now let me write a temporary test to reproduce the issue and verify the fix.

  16. GLM Assistant

    Both tests pass. Let me verify the fix actually addresses the issue by reverting and confirming the tests would have failed before the fix.

  17. GLM Assistant

    Confirmed: before the fix, Back went to ScreenPreset (5); after the fix, it goes to ScreenAgents (3). Now let me run the existing tui tests to make sure nothing is broken.

  18. GLM Assistant

    All tests pass. Let me also run the broader test suite to ensure nothing else is broken.

  19. GLM Assistant

    These failures are environment-related (GOPATH set to /tmp/gopath instead of ~/go/bin), not related to my change. Let me confirm by running them on the original code.

  20. GLM Assistant

    Confirmed — those CLI test failures are pre-existing environment issues (GOPATH set to /tmp/gopath), unrelated to my change.

    Let me review my final diff.

  21. GLM Assistant

    The fix is complete and minimal. Let me run the tui test suite once more to confirm everything passes.

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.