All directories
AgentEngineeringProduct

Letta

letta-ai/letta

Stateful agents with advanced memory (formerly MemGPT-lineage ideas). GitHub: letta-ai/letta (~24k stars).

00

GitHub repository

https://github.com/letta-ai/letta
01

Overview

Letta (letta-ai/letta) is listed in LimeDock Directories as an AI agent resource. Stateful agents with advanced memory (formerly MemGPT-lineage ideas). Group: memory-infra. Community size: ~24k GitHub stars. Repo (copy/paste): https://github.com/letta-ai/letta This page is a plain-English guide so searches for the GitHub project can land on how teams actually use it.

SaaSOther

Work with LimeDock

Using this skill? LimeDock can wire it into a durable automation you own.

Agents are a starting point. LimeDock turns the workflow into production automation your SaaS team owns — not another prompt library.

We sell owned automations for SaaS teams — live workflows that plug into Slack, CRM, and your internal platform — not just a skill list.

02

Link

https://github.com/letta-ai/letta
03

Installation guide

Open the GitHub repository, then follow the README for your stack.

Official GitHub repository: https://github.com/letta-ai/letta GitHub path: letta-ai/letta

How to open it: 1. Copy: https://github.com/letta-ai/letta 2. Clone or follow the README for your OS/stack. 3. Start with the smallest example before production use.

04

How to use it

**Simple example** You need agents that manage long-term memory deliberately, not just a chat log.

1. Install Letta. 2. Create a stateful agent. 3. Define memory rules; test across sessions.

05

Example prompts

  • Create a Letta agent that remembers project preferences.
  • Letta vs Mem0?
  • Memory hierarchical design tips.
06

Use cases and examples

  • Evaluate letta-ai/letta as an AI agent building block
  • Pilot Letta on one staging workflow
  • Compare against agents you already pay for
  • Document a team playbook after the pilot
07

Prerequisites

  • Runtime/hosting
  • Privacy rules
08

Tips

  • Stateful ≠ immortal — plan deletions.
  • Test multi-session explicitly.