@letta-ai/letta-code 0.1.8 → 0.1.10

package/README.md

@@ -10,8 +10,10 @@ https://github.com/user-attachments/assets/5561a3ff-afd9-42a9-8601-55d245946394
 
 Letta Code is a command-line harness around the stateful Letta [Agents API](https://docs.letta.com/api-reference/overview). You can use Letta Code to create and connect with any Letta agent (even non-coding agents!) - Letta Code simply gives your agents the ability to interact with your local dev environment, directly in your terminal.
 
+Letta Code is model agnostic, and supports Sonnet 4.5, GPT-5, Gemini 2.5, GLM-4.6, and more.
+
 > [!IMPORTANT]
-> Letta Code is a **research preview** in active development, and may have bugs or unexpected issues. To learn more about the roadmap and chat with the dev team, visit our [Discord](https:/discord.gg/letta). Contributions welcome, join the fun.
+> Letta Code is a **research preview** in active development, and may have bugs or unexpected issues. To learn more about the roadmap and chat with the dev team, visit our [Discord](https://discord.gg/letta). Contributions welcome, join the fun.
 
 ## Quickstart
 
@@ -49,7 +51,7 @@ Letta Code uses a hierarchical memory system with both global and local blocks:
 **Local** (`./.letta/settings.json`)  
 - `project` block - stores project-specific context
 
-### Starting Letta
+### Starting Letta Code
 
 ```bash
 letta                    # New agent (attaches to existing memory blocks or creates new)
@@ -72,22 +74,68 @@ letta --agent <id>       # Open specific agent
 
 ### Headless Mode
 ```bash
-letta -p "your prompt"                           # Run non-interactive
-letta -p "commit changes" --continue             # Continue previous session
-letta -p "run tests" --allowedTools "Bash"       # Control tool permissions
-letta -p "run tests" --disallowedTools "Bash"    # Control tool permissions
+letta -p "Run bun lint and correct errors"              # Run non-interactive
+letta -p "Pick up where you left off" --continue        # Continue previous session
+letta -p "Run all the test" --allowedTools "Bash"       # Control tool permissions
+letta -p "Just read the code" --disallowedTools "Bash"  # Control tool permissions
 
 # Pipe input from stdin
 echo "Explain this code" | letta -p
 cat file.txt | letta -p
-gh pr diff 123 | letta -p --yolo                 # Review PR changes
+gh pr diff 123 | letta -p --yolo
+
+# Output formats
+letta -p "Analyze this codebase" --output-format json         # Structured JSON at end
+letta -p "Analyze this codebase" --output-format stream-json  # JSONL stream (one event per line)
 ```
 
 You can also use the `--tools` flag to control the underlying *attachment* of tools (not just the permissions).
 Compared to disallowing the tool, this will additionally remove the tool schema from the agent's context window.
 ```bash
-letta -p "run tests" --tools "Bash,Read"         # Only load specific tools
-letta -p "analyze code" --tools ""               # No tools (analysis only)
+letta -p "Run all tests" --tools "Bash,Read"         # Only load specific tools
+letta -p "Just analyze the code" --tools ""          # No tools (analysis only)
+```
+
+Use `--output-format json` to get structured output with metadata:
+```bash
+# regular text output
+$ letta -p "hi there"
+Hi! How can I help you today?
+
+# structured output (single JSON object at end)
+$ letta -p "hi there" --output-format json
+{
+  "type": "result",
+  "subtype": "success",
+  "is_error": false,
+  "duration_ms": 5454,
+  "duration_api_ms": 2098,
+  "num_turns": 1,
+  "result": "Hi! How can I help you today?",
+  "agent_id": "agent-8ab431ca-63e0-4ca1-ba83-b64d66d95a0f",
+  "usage": {
+    "prompt_tokens": 294,
+    "completion_tokens": 97,
+    "total_tokens": 391
+  }
+}
+```
+
+Use `--output-format stream-json` to get streaming outputs, in addition to a final JSON response.
+This is useful if you need to have data flowing to prevent automatic timeouts:
+```bash
+# streaming JSON output (JSONL - one event per line, token-level streaming)
+# Note: Messages are streamed at the token level - each chunk has the same otid and incrementing seqId.
+$ letta -p "hi there" --output-format stream-json
+{"type":"init","agent_id":"agent-...","model":"claude-sonnet-4-5-20250929","tools":[...]}
+{"type":"message","messageType":"reasoning_message","reasoning":"The user is asking","otid":"...","seqId":1}
+{"type":"message","messageType":"reasoning_message","reasoning":" me to say hello","otid":"...","seqId":2}
+{"type":"message","messageType":"reasoning_message","reasoning":". This is a simple","otid":"...","seqId":3}
+{"type":"message","messageType":"reasoning_message","reasoning":" greeting.","otid":"...","seqId":4}
+{"type":"message","messageType":"assistant_message","content":"Hi! How can I help you today?","otid":"...","seqId":5}
+{"type":"message","messageType":"stop_reason","stopReason":"end_turn"}
+{"type":"message","messageType":"usage_statistics","promptTokens":294,"completionTokens":97,"totalTokens":391}
+{"type":"result","subtype":"success","result":"Hi! How can I help you today?","agent_id":"agent-...","usage":{...}}
 ```
 
 ### Permissions
@@ -125,6 +173,11 @@ Permissions are also configured in `.letta/settings.json`:
 }
 ```
 
+## Self-hosting
+
+To use Letta Code with a self-hosted server, set `LETTA_BASE_URL` to your server IP, e.g. `export LETTA_BASE_URL="http://localhost:8283"`.
+See our [self-hosting guide](https://docs.letta.com/guides/selfhosting) for more information.
+
 ## Installing from source
 
 First, install Bun if you don't have it yet: [https://bun.com/docs/installation](https://bun.com/docs/installation)
@@ -135,8 +188,8 @@ First, install Bun if you don't have it yet: [https://bun.com/docs/installation]
 bun install
 
 # run the CLI from TypeScript sources (pick up changes immediately)
-bun run dev:ui
-bun run dev:ui -- -p "Hello world"  # example with args
+bun run dev
+bun run dev -- -p "Hello world"  # example with args
 ```
 
 ### Build + link the standalone binary