@letta-ai/letta-agent-sdk 0.8.68 → 0.8.69
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/dist/client-entry.js +4 -4
- package/dist/client-entry.js.map +2 -2
- package/dist/index.js +5 -5
- package/dist/index.js.map +3 -3
- package/package.json +3 -3
package/dist/client-entry.js
CHANGED
|
@@ -11725,16 +11725,16 @@ When you encounter an obstacle, do not use destructive actions as a shortcut to
|
|
|
11725
11725
|
- You can call multiple tools in a single response. If you intend to call multiple tools and there are no dependencies between them, make all independent tool calls in parallel. Maximize use of parallel tool calls where possible to increase efficiency. However, if some tool calls depend on previous calls to inform dependent values, do NOT call these tools in parallel and instead call them sequentially. For instance, if one operation must complete before another starts, run these operations sequentially instead. Never use placeholders or guess missing parameters in tool calls.
|
|
11726
11726
|
- If the user specifies that they want you to run tools "in parallel", you MUST send a single message with multiple tool use content blocks. For example, if you need to launch multiple agents in parallel, send a single message with multiple Agent tool calls.
|
|
11727
11727
|
- Use specialized tools instead of bash commands when possible, as this provides a better user experience. For file operations, use dedicated tools: Read for reading files instead of cat/head/tail, Edit for editing instead of sed/awk, and Write for creating files instead of cat with heredoc or echo redirection. Reserve bash tools exclusively for actual system commands and terminal operations that require shell execution. NEVER use bash echo or other command-line tools to communicate thoughts, explanations, or instructions to the user. Output all communication directly in your response text instead.
|
|
11728
|
-
- For broader codebase exploration and deep research, use the Agent tool with subagent_type
|
|
11728
|
+
- For broader codebase exploration and deep research, use the Agent tool with the default Letta agent (omit subagent_type). This is slower than calling Glob or Grep directly so use this only when a simple, directed search proves to be insufficient or when your task will clearly require more than a few queries.
|
|
11729
11729
|
|
|
11730
11730
|
<example>
|
|
11731
11731
|
user: Where are errors from the client handled?
|
|
11732
|
-
assistant: [Uses the Agent tool with
|
|
11732
|
+
assistant: [Uses the Agent tool with the default Letta agent to find the files that handle client errors instead of using Glob or Grep directly]
|
|
11733
11733
|
</example>
|
|
11734
11734
|
|
|
11735
11735
|
<example>
|
|
11736
11736
|
user: What is the codebase structure?
|
|
11737
|
-
assistant: [Uses the Agent tool with
|
|
11737
|
+
assistant: [Uses the Agent tool with the default Letta agent]
|
|
11738
11738
|
</example>
|
|
11739
11739
|
|
|
11740
11740
|
Tools are executed in a user-selected permission mode. When you attempt to call a tool that is not automatically allowed by the user's permission mode or permission settings, the user will be prompted so that they can approve or deny the execution. If the user denies a tool you call, do not re-attempt the exact same tool call. Instead, think about why the user has denied the tool call and adjust your approach. If you do not understand why the user has denied a tool call, ask them using AskUserQuestion when available, or an ordinary message otherwise.
|
|
@@ -17842,4 +17842,4 @@ export {
|
|
|
17842
17842
|
CloudManagedSandboxExpiredError
|
|
17843
17843
|
};
|
|
17844
17844
|
|
|
17845
|
-
//# debugId=
|
|
17845
|
+
//# debugId=37BAC87F328A3A1864756E2164756E21
|