@letta-ai/letta-code 0.31.4 → 0.31.5

package/skills/self-configuration/SKILL.md

@@ -88,15 +88,20 @@ If CLI behavior does not match the docs, stop and inspect `command -v letta`, `t
 
 Use memory when the user wants you to remember, prefer, learn, or change your identity/personality.
 
-Common files:
+Inspect the projected memory tree in the system prompt before choosing paths.
+Letta Code supports two layouts:
 
-| Path | Purpose |
-| --- | --- |
-| `$MEMORY_DIR/system/persona.md` | Identity, voice, behavioral defaults |
-| `$MEMORY_DIR/system/human.md` | Notes about the person you work with |
-| `$MEMORY_DIR/projects/` | Project-specific long-term context |
-| `$MEMORY_DIR/skills/` | Agent-owned reusable skills |
-| `$MEMORY_DIR/relationships/` | Relationship and collaboration notes |
+| Purpose | Root layout | Existing layout |
+| --- | --- | --- |
+| Identity and voice | `$MEMORY_DIR/persona.md` or another root persona file | `$MEMORY_DIR/system/persona.md` |
+| Notes about the user | `$MEMORY_DIR/human.md` or another root human file | `$MEMORY_DIR/system/human.md` |
+| Core memory | Other root Markdown files indexed by `MEMORY.md` | Markdown files under `$MEMORY_DIR/system/` |
+| Deferred memory | Directories with their own `MEMORY.md` | Files outside `$MEMORY_DIR/system/` |
+| Agent-owned skills | `$MEMORY_DIR/skills/` | `$MEMORY_DIR/skills/` |
+
+Use the active layout shown by the prompt and memory tools. Do not create a
+`system/` directory in a root-layout repository or move existing-layout memory
+to the root as part of an unrelated self-configuration request.
 
 After changing memory, inspect and commit the exact changed files. Push/sync according to the current harness reminder or the `syncing-memory-filesystem` skill; some environments sync committed memory automatically.
 

package/skills/syncing-memory-filesystem/SKILL.md

@@ -15,11 +15,16 @@ MemFS is a Git repository projected onto the computer where the agent is
 running. `$MEMORY_DIR` is the repository root. There is no second `memory/`
 directory inside it.
 
+The repository can use either memory layout. Inspect its current tree and the
+memory rules in the system prompt before editing files:
+
 ```text
-$MEMORY_DIR/
-├── .git/
-├── system/       # loaded into the system prompt
-├── reference/    # loaded only when read
+Root layout                         Existing layout
+$MEMORY_DIR/                        $MEMORY_DIR/
+├── MEMORY.md     # root index      ├── system/     # in-context memory
+├── persona.md    # core memory     ├── reference/  # deferred memory
+├── <topic>/                        └── skills/     # agent-owned skills
+│   └── MEMORY.md # child index
 └── skills/       # agent-owned skills
 ```
 
@@ -32,7 +37,7 @@ on the current machine. Do not run `git push` for normal MemFS sync; let the
 harness push after the turn.
 
 Committed memory changes do not alter the current compiled prompt immediately.
-Use `/recompile` when the current conversation must see new `system/` content
+Use `/recompile` when the current conversation must see changed core memory
 right away. Otherwise, the next prompt compilation or conversation will use
 the committed revision.
 
@@ -87,9 +92,13 @@ auth, branch tracking, and agent identity.
 
 ## Uncommitted Changes
 
-Raw file edits must preserve required frontmatter. Markdown files under
-`system/` and `reference/` need a non-empty `description`. `read_only` is
-protected and cannot be added, removed, or changed by the agent.
+Raw file edits must preserve the active layout's rules:
+
+- In the root layout, root and child `MEMORY.md` indexes have no frontmatter.
+  Every other memory Markdown file has exactly `name` and `description`.
+- In the existing layout, Markdown files under `system/` and `reference/` need
+  a non-empty `description`. `read_only` is protected and cannot be added,
+  removed, or changed by the agent.
 
 ```markdown
 ---
@@ -121,7 +130,7 @@ Resolve the conflict markers without deleting required frontmatter, then stage
 the resolved files by name. Finish the operation Git reports:
 
 ```bash
-git -C "$MEMORY_DIR" add system/example.md
+git -C "$MEMORY_DIR" add <resolved-memory-path>
 
 # If git status says a rebase is in progress:
 GIT_EDITOR=true git -C "$MEMORY_DIR" rebase --continue
@@ -163,7 +172,8 @@ MemFS synchronization.
 2. Check whether the backend is cloud-backed or local-only.
 3. Inspect `git status`, the origin URL, and the current Git operation.
 4. Use `/memfs enable` for a missing checkout and `/memfs sync` for a pull.
-5. Preserve frontmatter and finish any existing merge or rebase.
+5. Preserve the active layout's indexes and frontmatter, then finish any
+   existing merge or rebase.
 6. Leave hosted pushes to post-turn sync once the repository is clean.
 7. If the command still fails, rerun it with `LETTA_DEBUG=1` and report the
    redacted error. Never print or copy credential-helper values.