blun-king-cli 9.1.89 → 9.1.91
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
|
@@ -258636,6 +258636,7 @@ var init_read = __esmMin((() => {
|
|
|
258636
258636
|
MAX_BYTES_KB: MAX_BYTES / 1024,
|
|
258637
258637
|
MAX_LINE_LENGTH
|
|
258638
258638
|
});
|
|
258639
|
+
read_default = "Read a UTF-8 text file from the local filesystem. Use Read directly for a known concrete file path; missing or invalid paths return errors. Do not pre-check a known file with Glob or `ls`. Use Bash `ls` for a known directory, Glob for unknown file names, and Grep for unknown content. Issue independent Read calls in parallel when several files may help.\n\nRelative paths resolve from the working directory; paths outside it must be absolute. Each call returns at most {{ MAX_LINES }} lines or {{ MAX_BYTES_KB }} KB, whichever comes first, and truncates source lines beyond {{ MAX_LINE_LENGTH }} characters. Page large files with 1-based `line_offset` and `n_lines`; omit `n_lines` to use the {{ MAX_LINES }}-line cap. Negative line_offset reads from the end, up to {{ MAX_LINES }} lines. A capped result with more source lines names the exact next `line_offset`.\n\nSensitive files such as `.env`, credential stores, and SSH private keys are refused; templates and public keys remain readable. Only UTF-8 text without NUL bytes is accepted. Use ReadMediaFile for images or video and Bash or an MCP tool for other binary formats.\n\nOutput is `<line-number>\\t<content>` per line. A trailing `<system>...</system>` block reports line and byte counts, truncation, and line-ending notes; it is not file content. Pure CRLF is displayed as LF and preserved by Edit. Mixed or lone carriage returns appear as `\\r` and require exact `Edit.old_string` escapes.\n\nAfter a successful Edit or Write, do not re-read only to prove the write landed. When correctness depends on an exact file, API, or output shape, inspect that final external contract before finishing.";
|
|
258639
258640
|
ReadTool = class {
|
|
258640
258641
|
kaos;
|
|
258641
258642
|
workspace;
|
|
@@ -261747,6 +261748,7 @@ var init_bash = __esmMin((() => {
|
|
|
261747
261748
|
MAX_TIMEOUT_S,
|
|
261748
261749
|
MAX_BACKGROUND_TIMEOUT_S
|
|
261749
261750
|
};
|
|
261751
|
+
bash_default = "Execute a `{{ SHELL_NAME }}` command for pipes, environment variables, processes, git, package managers, build or test runners, and other genuine shell semantics.\n\nPrefer the dedicated tools when they fit: `Read` for a known file, `Write` to create or replace a file, `Edit` for exact changes, `Glob` to locate files, and `Grep` to search contents. Their output is bounded and their permissions are clearer.\n\nStdout and stderr are combined. Long output may be truncated. A non-zero command ends with its exit code; timeouts and user interrupts are reported separately.\n\nEach call runs in a fresh shell environment. Variables, `cd`, and shell history do not carry into later calls; pass `cwd` or use absolute paths. Foreground commands default to {{ DEFAULT_TIMEOUT_S }}s and allow up to {{ MAX_TIMEOUT_S }}s through `timeout`. Do not run interactive commands or commands that may run forever in the foreground.\n\nWith `run_in_background=true`, provide a short `description`; the tool returns a task ID and notifies you on completion. Background tasks default to {{ DEFAULT_BACKGROUND_TIMEOUT_S }}s and allow up to {{ MAX_BACKGROUND_TIMEOUT_S }}s. Use `disable_timeout=true` only when no deadline is appropriate. Use `TaskOutput` for a status or output snapshot and `TaskStop` only to cancel. After launch, normally return control instead of immediately waiting.\n\nQuote paths containing spaces. Chain dependent commands with `&&`; issue independent read-only checks as parallel tool calls. Use `;`, `||`, pipes, redirects, and shell control flow when their semantics are required.\n\nStay inside the working directory unless the user explicitly requests otherwise. Avoid `..`, and never require superuser privileges without explicit instruction. Command availability depends on the host; verify unfamiliar commands before relying on them.";
|
|
261750
261752
|
BashTool = class {
|
|
261751
261753
|
kaos;
|
|
261752
261754
|
cwd;
|