Quickstart

This guide gets a running session in about 30 seconds. It uses the in-memory store and the fixture embedder, so you need no external services, no model files, and no toolchain.

Install the binary

Run the install script on macOS or Linux.

curl -fsSL https://github.com/nrynss/lambo/releases/latest/download/install.sh | sh

The script picks the binary for your platform, verifies its SHA-256 checksum, and installs it to ~/.local/bin. Confirm it with lambo --version. Windows binaries and a build-from-source path are in Installation.

Configure a quick session

Create a lambo.toml that selects a local SQLite file and the fixture embedder. This file is how you choose backends. The binary already carries all of them.

[store]
kind = "sqlite"
path = "./lambo.db"

[embedder]
kind = "fixture"
dim = 1024

SQLite rather than the in-memory store, because each command below runs as its own process. The in-memory store lives inside one process and is gone when that process exits, so a write from one command would not be visible to the next.

Create the schema once.

lambo --config lambo.toml provision

sqlite schema provisioned (init_schema, idempotent)

Write memory

Each small agent writes memory as one deterministic line. This command derives one concept into the demo session.

lambo --config lambo.toml derive --session demo --agent agent-a \
  --content "user schema" --kind entity

The one-shot command takes the session write lease, writes the concept, and releases the lease when it exits.

Recall memory

Read the concept back with recall. Recall is a read, so it works whether or not a server holds the session.

lambo --config lambo.toml recall --session demo --query "user schema"

user schema [Entity] (score 0.29)

The recall returns the matching concept with its type and score.

Serve a session

Start the server to let MCP clients connect. The server owns the session as its single writer.

lambo serve --config lambo.toml --session demo --agent agent-a

The server runs and waits for MCP clients. Leave it running in its own terminal. Do not run another command line write in the same terminal, because the server already holds the write lease.

What to try next

Pick whichever direction matches what you want to build.

• Connect an MCP client with an mcpServers block in Installation.
• Point the same binary at a durable store by editing lambo.toml. See Configuration.
• Run a full walkthrough in End to end.
• Run the scripted two-agent demo described in Demo.
• Explore the seven MCP tools.