You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Use ~/.local/bin per XDG Base Directory Specification instead of ~/.agentmemory/bin #871
agentmemory's setup wizard installs the iii engine to ~/.agentmemory/bin/, but the iii engine's own install script (install.iii.dev/iii/main/install.sh) uses ~/.local/bin per XDG Base Directory Specification. This creates an inconsistency — two installers for the same binary, two different paths.
Current behavior
src/cli.ts line ~618: prompt offers Install iii v0.11.2 to ~/.agentmemory/bin (~6MB, ~5s)
agentmemoryBinDir() returns ~/.agentmemory/bin
runIiiInstaller() installs to that path
Expected behavior
Both the iii engine's own installer and agentmemory's setup wizard should use $HOME/.local/bin, which is the XDG-compliant default for user binaries.
Context
This was introduced in PR #774 (fixing #752) to isolate agentmemory's pinned iii version from a user-managed global install. The isolation goal is valid, but the mechanism creates a non-standard path that users must manually add to PATH.
Proposal
Change agentmemoryBinDir() to return $HOME/.local/bin
Update the prompt label to say ~/.local/bin
Handle version conflicts differently — e.g., warn the user if PATH already contains a different iii version, or use a wrapper script that sets the correct version before invoking the binary
Activity
HaleTom commentedon Jun 9, 2026
If you want to ensure that you have your own specific version of
iii:Change agentmemoryBinDir() to return
$HOME/.local/bin/agentmemoryThen you can have a private
$HOME/.local/bin/agentmemory/iii