Building machines that learn.

npm i -g @letta-ai/letta-code
Joined August 2024
Introducing FrontierMemory: a new way to evaluate agent memory through downstream task performance. While existing memory benchmarks focus on recall (saturated via agentic search), FrontierMemory focuses on how agents learn from experience.
36
28
23
226
42,863
Letta retweeted
Recommended reading and a super-interesting benchmark for measuring continual learning capabilities through memory. Agent memory is largely unsolved. As agents advance in capabilities like long-horizon work, it's unclear which models or harnesses work best, or which memory systems and types to use. Opus 5.5 at the top is not a surprise. But it's exciting that open-weight models like GLM-5.3 perform so well on memory generation. My big question is how this (better memory systems and persistent agent capabilities) translates into more performant, efficient RSI agents and harnesses.
Introducing FrontierMemory: a new way to evaluate agent memory through downstream task performance. While existing memory benchmarks focus on recall (saturated via agentic search), FrontierMemory focuses on how agents learn from experience.
41
11
2
94
11,260
Memory is becoming a core part of agent harnesses/products (e.g. Instinct, @Muse, @cognition Devin, @PrimeIntellect Prime Agent, @NousResearch Hermes, @openclaw, @LangChain Deep Agents, @Letta_AI) -- yet despite every agent claiming to "continually learn", there's no benchmark to actually measure that capability. A big problem is that memory benchmarks today only measure recall (e.g. simple Q/A about past events). They don't measure if/how agents actually learn from experience to get better at work. At the same time, benchmarks for coding/knowledge work consist of many isolated, unrelated tasks - so they also don't allow for measuring cross-task learning. The context needed for a task is fully specified up-front (very unrealistic). In practice, both agents and humans work through sequences of many *related* tasks. Experience from past work provides context and learnings that apply to future work. This is why if you're a manager, you have to provide a lot more context when assigning tasks to a brand new employee or external contractor. Meanwhile, a great senior employee might not need any instructions at all. With FrontierMemory, we adapt existing benchmark tasks for coding and knowledge work so that instead of all the necessary context being provided up-front and within the task, it has to be learned from past experience. This allows us to compare how well different models and harnesses learn over time.
Introducing FrontierMemory: a new way to evaluate agent memory through downstream task performance. While existing memory benchmarks focus on recall (saturated via agentic search), FrontierMemory focuses on how agents learn from experience.
27
14
3
204
14,850
FrontierMemory from @Letta_AI is the first benchmark to measure memory based on performance on downstream tasks. Memory remains one of the biggest unsolved challenges in AI. FrontierMemory ACTUALLY gives us a way to actually measure and compare memory capabilities across different harnesses and models.
Introducing FrontierMemory: a new way to evaluate agent memory through downstream task performance. While existing memory benchmarks focus on recall (saturated via agentic search), FrontierMemory focuses on how agents learn from experience.
2
3
14
1,037
Truly capable agents must learn from experience, not merely recall facts. The FrontierMemory benchmark evaluates agent memory directly by measuring its impact on downstream task performance.
Introducing FrontierMemory: a new way to evaluate agent memory through downstream task performance. While existing memory benchmarks focus on recall (saturated via agentic search), FrontierMemory focuses on how agents learn from experience.
10
7
1
53
2,995
FrontierMemory is a continuous benchmark. In our next release, we plan to add longer-horizon tasks that enable RSI from memory. For more details see: frontiermemory.com
1
1
19
1,274
Thanks to our partners for providing early feedback and inference to support the benchmark @AnthropicAI @OpenAI @nvidia @databricks @Snowflake @baseten @FireworksAI_HQ
1
6
978
Letta Code now supports dynamic workflows to compose model-agnostic subagents and decision models.
9
1
4
29
11,560
Using Muse to dispatch work to my @Letta_AI cloud agent, which can be orchestrated via MCP MCP is the real A2A
4
1
2
13
2,145
Opus 5.5, GPT 6 Sol, and GPT 6 Luna are now all available on Letta Code!
2
2
9
1,456
It's AI Infra night at @Letta_AI HQ! Here's Letta cofounder @sarahwooders showing off Letta, cloud sandboxes, Slack, and teleportation from her laptop to the cloud.
1
1
9
616
Mods in @Letta_AI are very cool, and they work on cloud agents too! (you just need to move the mod into the agent's memory so it becomes part of the agent-owned context) letta.com/blog/introducing-m…
1
2
11
1,316
I have learned a lot about agent design and more through these office hours sessions @just_cameron hosts weekly for @Letta_AI
LETTA OFFICE HOURS TODAY AT 11:30 AM PACIFIC Come hang out on our Discord and learn about recent developments in @Letta_AI: cloud agents, the Agent SDK, shared memory, OpenRouter OAuth, and MORE. Bring questions, comments, compliments, and high-fives. Link to join below 👇
1
1
2
406
LETTA OFFICE HOURS TODAY AT 11:30 AM PACIFIC Come hang out on our Discord and learn about recent developments in @Letta_AI: cloud agents, the Agent SDK, shared memory, OpenRouter OAuth, and MORE. Bring questions, comments, compliments, and high-fives. Link to join below 👇
1
1
1
3
958
We’re releasing the Letta Agent SDK: A TypeScript library for working with stateful agents. Persistent agents can be invoked across computers (local/remote) while retaining memory and state. Use it to create your own stateful agent UIs or to build dynamic workflows.
21
3
2
53
7,591
The Letta Agents SDK allows you to decouple: - where the agent takes actions (executing client-side tools) - where the agent loop & state is managed This means you can use a remote "managed agent" locally, and vice-versa.
1
2
474