Get Started

Installation

Installation channels and fallback behavior for each project.

Primary recommendation

Use hosted installers first. They keep install behavior consistent across all public docs, README instructions, and web quickstart surfaces.

Hosted installers

Hosted install commands

Run only the runtime you need. All projects remain standalone-first.

curl -fsSL https://agentralabs.tech/install/memory | bash

Desktop profile (MCP auto-merge)

Desktop profile configures supported local desktop MCP clients.

curl -fsSL https://agentralabs.tech/install/memory/desktop | bash

Terminal profile (no config writes)

Terminal profile installs binaries only.

curl -fsSL https://agentralabs.tech/install/memory/terminal | bash

Server profile (remote hosts)

Server profile installs binaries for remote/service environments without desktop config writes.

curl -fsSL https://agentralabs.tech/install/memory/server | bash

If a platform-specific release artifact is unavailable, installers fall back to source-based install (cargo install from canonical repo source).

Fallback example

[info] No GitHub release found; using source fallback.
[info] Installing from source...
[ok] Build complete.
[ok] Binary installed in ~/.local/bin

Rust channel

Direct installation from crates.io for environments that standardize on cargo-managed binaries.

cargo install agentic-memory agentic-memory-mcp

Python helper channel

Convenient memory setup helper for teams standardizing on Python-based agent tooling.

pip install amem-installer
amem-install install --auto

Guardrail

If command output diverges from these expectations, capture full terminal output and report it via Feedback and Community.