ISSUE DESCRIPTION fix(installer): back navigation from Pi-only install shows unrelated…
- 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-piinstaller fromgentle-ai, if I select onlyPias the installation target and then useBackon 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
- Start the
gentle-aiinstaller.
2. Select onlyPias the installation target.
3. Continue to the next step.
4. SelectBack.
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
Piduring 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 usinggit reset --hardcommand. Additionally, you can usegit stashandgit stash popto temporarily save your changes and restore them later. Finally, you can see the changes that you've made (which will be submitted when you callsubmit) usinggit statusorgit diffcommands. However you don't need to usegit addorgit commitbefore submitting your changes. In fact,submitonly submits currently unstaged changes because it usesgit diffto 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-$
- Assistant
I'll start by exploring the repository structure and locating the installer navigation/flow logic related to Pi-only installation.
- Assistant
This is a Go project. Let me search for installer-related code more carefully.
- Assistant
Let me look at the installcmd and tui directories, as well as search for Pi-related installer flow.
- Assistant
rg is not found - maybe I need to use grep. Let me use grep instead.
- Assistant
I found
isPiOnlyAgentsandpiOnlyComponents— next I'll inspect router and navigation handling around those. - Assistant
Found the router skip path for Pi-only installs — inspecting forward/back handling next.
- Assistant
Inspecting
goBackand dependency-tree reverse navigation next for the Pi-only path. - Assistant
Checking DependencyTree confirm/back path and existing Pi-only tests.
- Assistant
Reviewing existing Pi-only tests and the full back-nav path from DependencyTree.
- Assistant
Checking the
shouldShow*predicates against the Pi-only defaults. - Assistant
Root cause: Pi-only jumps
Agents → DependencyTree, but back nav returns toPreset/persona/TDD. Fixing both Back paths to return toScreenAgents. - Assistant
I need to fix both places: I'll help you fix this navigation bug in the installer. Let me analyze the current state and plan the changes needed.
First, let me check the current code structure to understand the exact locations where the navigation logic needs to be updated. I'll use git to see the relevant files. Let me start by examining the installer code.
- Assistant
Applying the navigation fix in both DependencyTree back-paths.
- Assistant
I'll update goBack and confirmSelection.
- Assistant
Now fix the confirmSelection path for DependencyTree Back.
- Assistant
I also notice confirmSelection for DependencyTree Back is missing OpenCode plugins check that goBack has - but for consistency on this fix, I'll add pi-only check first. Looking at confirmSelection pa...
- Assistant
Verifying the fix with a temporary test script:
- Assistant
Looking at the tests in model_test.go - they use package tui and unexported things. My external test package might not work well. Better to put it in package tui like other tests.
- Assistant
There's a screensAgentOptions helper that returns []model.AgentID not []screens.AgentOption. Let me check.
- Assistant
Running focused Pi-only navigation tests and existing related tests.
- Assistant
Need to set GOPATH
- Assistant
Only one test ran — checking whether the temporary test file is present.
- Assistant
The filename must end with
_test.go— renaming it. - Assistant
Confirming the pre-fix failure, then cleaning up the temporary tests.
- Assistant
Bug reproduced (screen 5 = Preset). Restoring the fix.
- Assistant
Removing the duplicate comment that was introduced.
- Assistant
Remove duplicate comment lines.
- Assistant
The edit left a broken if-block — rewriting that section cleanly.
- Assistant
Restoring the full comment block above that section.
- Assistant
Looks good. Removing the temp test file and running the related suite.
- Assistant
Running the full TUI package test suite.
- Assistant
Confirming the diff only contains the intended navigator fix.
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.
Identical first prompt
claude-sonnet-5Compare side by side →
claude-sonnet-5Compare side by side →
claude-sonnet-5Compare side by side →
claude-sonnet-5Compare side by side →
claude-sonnet-5Compare side by side →
Qwen/Qwen3.6-35B-A3BCompare side by side →
Qwen/Qwen3.6-35B-A3BCompare side by side →
Qwen/Qwen3.6-35B-A3BCompare side by side →
Qwen/Qwen3.6-35B-A3BCompare side by side →
Qwen/Qwen3.6-35B-A3BCompare side by side →
Qwen/Qwen3.6-27BCompare side by side →
Qwen/Qwen3.5-35B-A3BCompare side by side →