blun-king-cli 9.1.91 → 9.1.93
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/LIESMICH.txt +1 -1
- package/README.md +1 -1
- package/blun.mjs +2 -0
- package/package.json +1 -1
package/LIESMICH.txt
CHANGED
package/README.md
CHANGED
package/blun.mjs
CHANGED
|
@@ -252197,6 +252197,7 @@ var init_agent$1 = __esmMin((() => {
|
|
|
252197
252197
|
}).describe("Cumulative token usage")
|
|
252198
252198
|
});
|
|
252199
252199
|
BACKGROUND_AGENT_UNAVAILABLE = "Background agent execution is not available for this agent because TaskList, TaskOutput, and TaskStop are not enabled.";
|
|
252200
|
+
agent_default = "Launch a subagent for substantial, multi-step work in its own context and wire file. It returns a final report while keeping intermediate file contents out of your context.\n\nThe subagent starts with zero conversation context. Give it a self-contained prompt with the goal, known facts, constraints, and required result. For a direct lookup, include the exact path or command. For an investigation, state the question and evidence needed instead of prescribing rigid steps.\n\nWhen continuing earlier work, resume the existing agent ID instead of spawning a new agent; its context remains available. A subagent report is only visible to you, so relay the relevant conclusions to the user. `timeout_minutes` sets the wall-clock interval before the same agent continues automatically with preserved context; `timeout_minutes=0` disables that interval.\n\nUse Agent for complex, context-heavy work, not a trivial one- or two-step task. Launch independent agents in parallel in one response when useful. After assigning a scope, do not duplicate its searches or reads and do not abandon it to redo the same work manually; both erase the intended context savings.";
|
|
252200
252201
|
AgentTool = class {
|
|
252201
252202
|
subagentHost;
|
|
252202
252203
|
backgroundManager;
|
|
@@ -252985,6 +252986,7 @@ var init_edit = __esmMin((() => {
|
|
|
252985
252986
|
replace_all: boolean$1().optional().describe("Set true only when every occurrence of old_string should be replaced."),
|
|
252986
252987
|
single_file_override: boolean$1().optional().describe("Set true only when the latest direct user message explicitly requires one single source file. The tool verifies that request and reports the override visibly.")
|
|
252987
252988
|
});
|
|
252989
|
+
edit_default = "Perform exact replacements in existing files. Use Edit for every incremental change instead of Write or Bash `sed`. Read the target immediately before every Edit; take `old_string` and `new_string` from that current Read output, remove the line-number prefix and tab, and never guess from memory.\n\n`old_string` must be exact and unique unless `replace_all` is true. Add surrounding context when it is ambiguous. Use `replace_all` only when every occurrence should change, and keep `new_string` different from `old_string`. Parallel Edit calls may target different files only. Before another Edit on the same file, read it again because the first replacement can invalidate the next `old_string`.\n\nFor pure CRLF files, Read shows LF; use LF in both strings and Edit restores CRLF. For mixed endings or lone carriage returns, include the displayed `\\r` escapes exactly.\n\nSource files may contain at most 500 lines. An already oversized file may only be edited when the result has fewer lines. Set `single_file_override=true` only when the latest direct user message explicitly requires one single file; the accepted override is shown to the user.";
|
|
252988
252990
|
EditTool = class {
|
|
252989
252991
|
kaos;
|
|
252990
252992
|
workspace;
|