Repository navigation
Description
Description
AgentMemory asks me to install iii Console every time I start it, even though I already selected Yes and ran the installer.
I'm using v0.9.29 on Ubuntu WSL2. The iii engine is installed, but AgentMemory still cannot find iii-console and repeats the prompt.
I checked the current main branch and found that the installer and detection logic still disagree.
Environment
- OS: Ubuntu 26.04.1 LTS on WSL2
- Node.js: v24.19.0, managed by nvm
- npm: v12.0.2
- AgentMemory: v0.9.29
Steps to reproduce
- Run
agentmemory. - Select Yes when prompted to install iii Console.
- Run
agentmemoryagain. - The same installation prompt appears.
I haven't captured the installer's full output, so I can't confirm whether every installation step succeeded.
What I found
The iii engine is present:
$ command -v iii
/home/wsl/.local/bin/iii
$ ls -l ~/.agentmemory/bin/iii
-rwxr-xr-x 1 wsl wsl 33220928 Apr 21 01:25 /home/wsl/.agentmemory/bin/iii
But iii-console is missing:
$ command -v iii-console
(no output)
$ ls -l ~/.local/bin/iii-console
(no executable found)
In src/cli.ts, detectIiiConsole() looks for iii-console.
However, ensureIiiConsole() runs the installer at:
https://install.iii.dev/iii/main/install.sh
That installs the iii engine. The CLI then checks for iii-console again. If that executable is still missing, AgentMemory treats the console as uninstalled.
Answering Yes also doesn't save a preference that would prevent another prompt.
Expected behavior
After I accept the installation prompt, AgentMemory should detect a working console or explain why the installation failed.
It shouldn't ask me to repeat an installation that cannot satisfy its detection check.
The fix should also account for iii version differences. The iii v0.11.2 documentation describes a standalone iii-console binary, while newer documentation uses iii console. Finding an iii executable alone may not prove that the console is available.
Related issues and previous PR
This problem overlaps with several earlier reports:
- [#680](Bug: Incorrect iii console install URL in doctor diagnostics #680) reported the incorrect console installer URL. It was closed as completed, but correcting the URL hasn't resolved this detection mismatch.
- [#712](iii-console install - Illegal option -o pipefail #712) reports a console installation failure on Ubuntu involving
shandpipefail. That issue is still open. I haven't confirmed that particular error on my machine. - [#874](doctor: "iii-on-path-not-local-bin" and fixes is a no-op -- install succeeds but check still finds other binary first #874) and [#875](engine-version-mismatch fix doesn't update PATH — iii-on-path-not-local-bin still fails after install #875) report related problems with iii executable detection. Both remain open. engine-version-mismatch fix doesn't update PATH — iii-on-path-not-local-bin still fails after install #875 also documents a successful console installation message followed by another installation hint.
- [PR #506](fix: correct iii console install guidance #506) proposed changes to the installer and detection logic, but it was closed without merging.
The repeated prompt still occurs in v0.9.29. The current main branch also retains the installer and detection mismatch, so this does not appear to be resolved.
Activity
rohitg00 commentedon Oct 8, 2026
@heykay-47 fixed in v0.9.30: the console install prompt and the
skipConsoleInstallpreference are gone;agentmemory consolelaunches the console through the pinned engine. https://github.com/rohitg00/agentmemory/releases/tag/v0.9.30