Canonical: https://instain.ru/en/ai/letta/ Language: en Letta platform for agents with memory # Letta. Persistent agent state with explicit memory blocks 4.28 / 5 [Directory score](https://instain.ru/en/ai/letta/#editorial-rating) [Official website ](https://docs.letta.com/) Letta allows you to store agent information separately from a particular dialog. In the application, you can give the agent the right to update the agreed memory blocks. ![Letta documentation for agents with a long-term condition](https://instain.ru/assets/images/letta-screen-c147213be7d5-1200.webp) Letta documentation for agents with a long-term condition. [Open the source ](https://docs.letta.com/) ## When History and Memory Differ The learning assistant heard a request to write to work mail, and later received a correction. If every time you send models the entire dialogue, the old and new values will lie side by side. In Letta, you can store the active option in a separate agent memory unit and check it between sessions. The team decides which records the agent has the right to change and which changes require explicit confirmation from the person. ## Scenario with correction Create a test agent and set a secure block structure. Give a fictional preference, close the dialogue and open a new one. Ask to name the current channel, and then correct the value. Check the block itself, and then ask the question again in a separate session. If the user's phrase is ambiguous, the agent must clarify the intent. This rule will need to be set and checked in the application. Make a second test account. The record of the first should not appear in his answer or in the list of available blocks. ## Period and area of storage Check how to delete a record, revoke consent, and find the reason for the last update. If the application keeps full messages, set the terms separately for the journal and for short memory information. Cloud access and self-hosting differ in the configuration of storage and maintenance. In both cases, the stored field should be considered verifiable data, especially when a method of communication or action in an external system is selected for it. ## Suitable tasks - Maintain confirmed preference between sessions - Verify the correction of an outdated value in memory Features ## Strengths - Describes memory through individual agent blocks - Documenting the status and work with agents via SDK Things to consider ## Limitations - Decide in advance what information may be stored - Saved records can become outdated or contain errors ## Selection and conditions Free access Not confirmed Trial period Not confirmed No sign-up required Not confirmed Russian interface Not confirmed Local installation Yes API Yes “Not confirmed” means there is not enough information. The feature may still be available; check the developer’s terms. Input formats Text, Data Result Text, Data ### Terms The cloud platform has its own plans. For self-hosting, budget for the model, storage, and maintenance. Decide in advance what information may be stored. From task to first result ## Practical example Task Maintain confirmed preference between sessions What to prepare Two synthetic accounts and three dialogues about channel change. ### Task brief or prompt Keep a confirmed communication channel, then update it upon explicit request. In the next session, show the current value. ### Expected result Verified value in memory with clear access area. ### How to check the result - Read the memory block after correction. - Make sure the other account doesn’t get that preference. An editorial teaching example of a task brief, not the result of hands-on testing of the service. Check that the required mode is available, that you have rights to the source material and that the intended use of the result is permitted. Check details ## Official sources - [Official documentation of Letta ](https://docs.letta.com/) - [Agents with a fortune in Letta ](https://docs.letta.com/v1-sdk/concepts/stateful-agents) - [Plans and access Letta ](https://docs.letta.com/pricing) This description is based on the developer’s material. Features, prices and availability may change; check the primary source before use. About the tool Developer Letta Category [Code](https://instain.ru/en/category/code/) Access Choose the managed service or follow the self-hosting documentation. Configure model access and cloud API access separately. Payment The cloud platform has its own plans. For self-hosting, budget for the model, storage, and maintenance. API Yes, from the developer [Developer terms ](https://docs.letta.com/pricing) Directory score 4.28 / 5 Features 4.40 / 5 Workflows 4.10 / 5 Ecosystem 4.10 / 5 Documentation 4.50 / 5 Scores are an editorial guide to the directory. They are not user reviews or the results of personal testing. [See the methodology ](https://instain.ru/en/methodology/)