Skip to content

Use ~/.local/bin per XDG Base Directory Specification instead of ~/.agentmemory/bin #871

Open

Description

@HaleTom

Problem

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

  1. Change agentmemoryBinDir() to return $HOME/.local/bin
  2. Update the prompt label to say ~/.local/bin
  3. 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

  1. HaleTom commented on Jun 9, 2026

    @HaleTom
    Author

    If you want to ensure that you have your own specific version of iii:

    Change agentmemoryBinDir() to return $HOME/.local/bin/agentmemory

    Then you can have a private $HOME/.local/bin/agentmemory/iii

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions