@letta-ai/letta-code 0.14.1 → 0.14.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +0 -1
- package/letta.js +2156 -1515
- package/package.json +1 -1
- package/skills/syncing-memory-filesystem/SKILL.md +2 -2
package/package.json
CHANGED
|
@@ -5,7 +5,7 @@ description: Manage memory filesystem sync conflicts with git-like commands. Loa
|
|
|
5
5
|
|
|
6
6
|
# Memory Filesystem Sync
|
|
7
7
|
|
|
8
|
-
When memFS is enabled, your memory blocks are mirrored as `.md` files on disk at `~/.letta/agents/<agent-id>/memory/`. Changes to blocks or files are detected via content hashing and synced at startup and on manual `/memfs
|
|
8
|
+
When memFS is enabled, your memory blocks are mirrored as `.md` files on disk at `~/.letta/agents/<agent-id>/memory/`. Changes to blocks or files are detected via content hashing and synced at startup and on manual `/memfs sync`.
|
|
9
9
|
|
|
10
10
|
**Conflicts** occur when both the file and the block are modified since the last sync (e.g., user edits a file in their editor while the block is also updated manually by the user via the API). Non-conflicting changes (only one side changed) are resolved automatically during the next sync.
|
|
11
11
|
|
|
@@ -96,5 +96,5 @@ npx tsx <SKILL_DIR>/scripts/memfs-resolve.ts $LETTA_AGENT_ID --resolutions '[{"l
|
|
|
96
96
|
## Notes
|
|
97
97
|
|
|
98
98
|
- Non-conflicting changes (only one side modified) are resolved automatically during the next sync — you only need to intervene for true conflicts
|
|
99
|
-
- The `/memfs
|
|
99
|
+
- The `/memfs sync` command is still available for users to manually trigger sync and resolve conflicts via the CLI overlay
|
|
100
100
|
- After resolving, the sync state is updated so the same conflicts won't reappear
|