@letta-ai/letta-code 0.8.0 → 0.9.0-next.1

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.
Files changed (3) hide show
  1. package/letta.js +44175 -42898
  2. package/package.json +1 -1
  3. package/skills/initializing-memory/SKILL.md +1 -1
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@letta-ai/letta-code",
3
- "version": "0.8.0",
3
+ "version": "0.9.0-next.1",
4
4
  "description": "Letta Code is a CLI tool for interacting with stateful Letta agents from the terminal.",
5
5
  "type": "module",
6
6
  "bin": {
package/skills/initializing-memory/SKILL.md CHANGED
@@ -215,7 +215,7 @@ You should ask these questions at the start (bundle them together in one AskUser
215
215
  1. **Research depth**: "Standard or deep research (comprehensive, as long as needed)?"
216
216
  2. **Identity**: "Which contributor are you?" (You can often infer this from git logs - e.g., if git shows "cpacker" as a top contributor, ask "Are you cpacker?")
217
217
  3. **Related repos**: "Are there other repositories I should know about and consider in my research?" (e.g., backend monorepo, shared libraries)
218
- 4. **Workflow style**: "How proactive should I be?" (auto-commit vs ask-first)
218
+ 4. **Memory updates**: "How often should I check if I should update my memory?" with options "Frequent (every 3-5 turns)" and "Occasional (every 8-10 turns)". This should be a binary question with "Memory" as the header.
219
219
  5. **Communication style**: "Terse or detailed responses?"
220
220
  6. **Any specific rules**: "Rules I should always follow?"
221
221