@letta-ai/letta-code 0.25.11 → 0.26.0

package/package.json

@@ -1,8 +1,9 @@
 {
   "name": "@letta-ai/letta-code",
-  "version": "0.25.11",
+  "version": "0.26.0",
   "description": "Letta Code is a CLI tool for interacting with stateful Letta agents from the terminal.",
   "type": "module",
+  "packageManager": "bun@1.3.0",
   "bin": {
     "letta": "letta.js"
   },
@@ -13,7 +14,8 @@
     "scripts",
     "skills",
     "vendor",
-    "dist/types"
+    "dist/types",
+    "docs"
   ],
   "exports": {
     ".": "./letta.js",

package/scripts/check-layer-boundaries.js

@@ -3,9 +3,11 @@
  * Enforces architectural import boundaries between top-level modules.
  *
  * Rules:
- *   tools/    must not import from  cli/
- *   backend/  must not import from  cli/  or  websocket/
- *   providers/ must not import from  agent/  or  cli/
+ *   tools/              must not import from  cli/
+ *   backend/            must not import from  cli/  or  websocket/
+ *   providers/          must not import from  agent/  or  cli/
+ *   websocket/listener/ must not import from  backend/api/client  or  backend/api/conversations
+ *   telemetry/          must not import from  cli/  agent/  websocket/  or  tools/
  *
  * These are currently violation-free. Adding a rule here means you must
  * also ensure no existing code violates it.
@@ -43,6 +45,24 @@ const RULES = [
     description:
       "providers/ are pure LLM adapters — they must not import from agent/ or cli/",
   },
+  {
+    layer: "websocket/listener",
+    forbidden: ["backend/api/client", "backend/api/conversations"],
+    description:
+      "websocket/listener/ uses the getBackend() abstraction — it must not import the raw API client or conversations module directly",
+  },
+  {
+    layer: "cli/app",
+    forbidden: ["backend/api/conversations"],
+    description:
+      "cli/app/ uses the getBackend() abstraction for conversation operations — it must not import the raw conversations module directly",
+  },
+  {
+    layer: "telemetry",
+    forbidden: ["cli", "agent", "websocket", "tools"],
+    description:
+      "telemetry/ is a leaf observer — it must not import from cli/, agent/, websocket/, or tools/ (only backend/api/ for submitting data is permitted)",
+  },
 ];
 
 // Matches: import ... from "@/forbidden/..." (static imports only)

package/scripts/run-unit-tests.cjs

@@ -18,7 +18,6 @@ const dirs = [
   "src/permissions",
   "src/providers",
   "src/queue",
-  "src/ralph",
   "src/reminders",
   "src/skills",
   "src/telemetry",

package/skills/initializing-memory/SKILL.md

@@ -50,7 +50,7 @@ You should determine what the users goals and motivations are, to help yourself
 Understanding the user's personality and other attributes about them will help contextualize their interactions and allow you to engage with them more effectively. Can you pattern match them to common personas? Do they have unique attributes, quirks, or linguistic patterns? How would you describe them as a person? 
 
 **Understanding their preferences**: 
-You should learn how the user wants work to be done, and how they want to collaborate with AIs like yourself. Examples of this can include coding preferences (e.g. "Prefer functional components over class components", "Use early returns instead of nested conditionals"), but also higher-level preferences such as when to use plan mode, the scope of changes, how to communicate in different scenarios, etc. 
+You should learn how the user wants work to be done, and how they want to collaborate with AIs like yourself. Examples of this can include coding preferences (e.g. "Prefer functional components over class components", "Use early returns instead of nested conditionals"), but also higher-level preferences such as when to ask before planning or implementing, the scope of changes, how to communicate in different scenarios, etc.
 
 ### Understanding the codebase and existing work
 You should also learn as much as possible about the existing codebase and work. Think of this as your onboarding period - an opportunity to maximize your performance for future tasks. Learn things like: 
@@ -718,4 +718,3 @@ git push
 **Write findings to memory as you go** — don't wait until the end.
 **Edit memory files directly via the filesystem** — memory is projected to `$MEMORY_DIR` specifically for ease of bulk modification. Use standard file tools (Read, Write, Edit) and git to manage changes during initialization.
 
-