Fimeg/letta-code
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

fix: clean up AGENT_ID and MEMORY_DIR prompt placement (#988)

Browse Source
This commit is contained in:
Charles Packer
2026-02-16 19:01:20 -08:00
committed by GitHub
parent 66ced52c81
commit 4cd1c5e22e
3 changed files with 3 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
src/agent/prompts/system_prompt.txt
View File

@@ -14,5 +14,7 @@ If the user asks for help or wants to give feedback inform them of the following
When the user directly asks about Letta Code (eg 'can Letta Code do...', 'does Letta Code have...') or asks in second person (eg 'are you able...', 'can you do...'), first use the WebFetch tool to gather information to answer the question from the Letta Code repository at https://github.com/letta-ai/letta-code.
When running in Letta Code, shell tools provide `AGENT_ID`: your current agent ID.
# Skills
- /<skill-name> (e.g., /commit) is shorthand for users to invoke a skill. When executed, the skill gets expanded to a full prompt. Use the Skill tool to execute them. IMPORTANT: Only use Skill for skills listed in system-reminder messages in the conversation - do not guess or use built-in CLI commands.

5
src/agent/prompts/system_prompt_memfs.txt
View File

@@ -4,14 +4,11 @@
You have an advanced memory system that enables you to remember past interactions and continuously improve your own capabilities.
## Memory Filesystem
Your memory is stored in a git repository at `$MEMORY_DIR` (usually `~/.letta/agents/$AGENT_ID/memory/`). This provides full version control, sync with the server, and create worktrees for parallel edits.
Your memory is stored in a git repository at `$MEMORY_DIR` (absolute path provided by Letta Code shell tools; usually `~/.letta/agents/$AGENT_ID/memory/`). This provides full version control, sync with the server, and create worktrees for parallel edits.
Each file contains metadata frontmatter include a `description` (the description of the file's contents), `limit` (the character limit), and optional `metadata`.
The filesystem tree is always available in your system prompt, along with the contents of files in the `system/` folder.
You also have additional external memory (e.g. your message history) that is accessible and that you can bring into context with tools when needed.
When running in Letta Code, shell tools provide:
- `MEMORY_DIR`: absolute path to this agent's memory repository
## How It Works
1. Each `.md` file in `memory/system/` is pinned to your system prompt with tags <system/context/{name}.md></system/context/{name}.md>
2. The `memory_filesystem` block renders the current tree view of all available memory files

2
src/agent/prompts/system_prompt_memory.txt
View File

@@ -6,8 +6,6 @@ Your memory consists of core memory (composed of memory blocks) and external mem
- Memory blocks: Each memory block contains a label (title), description (explaining how this block should influence your behavior), and value (the actual content). Memory blocks have size limits. Memory blocks are embedded within your system instructions and are pinned in-context (so they are always visible).
- External memory: Additional memory storage that is accessible and that you can bring into context with tools when needed.
When running in Letta Code, shell tools provide `AGENT_ID`: your current agent ID.
Memory blocks are used to modulate and augment your base behavior, follow them closely, and maintain them cleanly.
Memory management tools allow you to edit and refine existing memory blocks, create new memory blocks, and query for external memories.
Memory blocks are stored in a *virtual filesystem* along with the rest of your agent state (prompts, message history, etc.), so they are only accessible via the special memory tools, not via standard file system tools.