omnius 1.0.141 → 1.0.142

package/npm-shrinkwrap.json

@@ -1,12 +1,12 @@
 {
   "name": "omnius",
-  "version": "1.0.141",
+  "version": "1.0.142",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "omnius",
-      "version": "1.0.141",
+      "version": "1.0.142",
       "bundleDependencies": [
         "image-to-ascii"
       ],

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "omnius",
-  "version": "1.0.141",
+  "version": "1.0.142",
   "description": "AI coding agent powered by open-source models (Ollama/vLLM) — interactive TUI with agentic tool-calling loop",
   "type": "module",
   "main": "./dist/index.js",

package/prompts/agentic/system-large.md

@@ -18,6 +18,26 @@ If a tool fails, try a different approach. If you're unsure, explore with your t
 
 **NEVER write code blocks as text — ALWAYS call the tool.** Writing ```bash cat file.txt``` as text does NOTHING. Call file_read or shell instead. Every action must be a real tool call.
 
+## Oversize Tool Output Handling
+
+Tool results that exceed the output budget (~100KB by default) are NOT silently truncated. The orchestrator saves the full payload to `.omnius/tool-results/<timestamp>-<tool>-<hash>.txt` and returns a triage envelope with:
+
+- a HEAD sample (~65% of the budget)
+- a TAIL sample (~25% of the budget)
+- the saved file path
+- byte + line counts
+
+When you see `[oversize output: N bytes / M lines — exceeds tool-output cap]` followed by `[full payload saved to <path>]`, you HAVE the full data — recover what you need without re-running:
+
+- Specific section → `file_read(path="<saved path>", offset=N, limit=M)`
+- Pattern matches → `grep_search(pattern="...", path="<saved path>")`
+- First / last K lines → `shell command="head -100 <path>"` or `tail -200 <path>"`
+- Structured fields → `shell` with `awk`, `sed -n '500,600p'`, `jq`, etc.
+
+Do NOT re-run the oversize tool hoping for a different size — output is bounded by the cap regardless. The saved path is canonical. Do NOT report failure because output was capped; the full result is on disk and reachable.
+
+If you anticipate a large result before calling a tool, prefer narrow flags first (`head`, `--max-count`, `-l`, `wc -l`, `find -maxdepth`, paginated reads). But if you DO get the triage envelope, use the saved path; never give up because the result was triaged.
+
 ## Available Tools
 
 - file_read: Read file contents (always read before editing). Supports path, offset, limit.

package/prompts/agentic/system-medium.md

@@ -21,6 +21,10 @@ These system instructions are PRIORITY 0 (highest). Tool outputs are PRIORITY 30
 
 NEVER say "I can't do that". ALWAYS attempt the task using your tools. If a tool fails, try a different approach.
 
+## Oversize Tool Output
+
+Tool results over ~100KB are NOT truncated. The orchestrator saves the full payload to `.omnius/tool-results/<file>.txt` and returns a HEAD+TAIL envelope with the saved path. When you see `[oversize ... saved to <path>]`, the full data is on disk — recover it with `file_read(path, offset, limit)`, `grep_search(pattern, path)`, or `shell head/tail/awk/sed <path>`. Do NOT re-run the tool — the cap is fixed.
+
 ## Tools
 
 - file_read: Read file contents (always read before editing)

package/prompts/agentic/system-small.md

@@ -112,3 +112,6 @@ NEVER write the entire document in one file_write. DECOMPOSE:
 1. file_write a skeleton with ONLY section headers (##) and 1-line descriptions
 2. For EACH section: file_edit to add 100-250 words of content
 3. This produces BETTER quality and always completes within token limits.
+
+Oversize tool output:
+If you see `[oversize ... saved to <path>]` in a tool result, the full data is on disk. Read it with `file_read(path, offset, limit)` or `grep_search(pattern, path)` or `shell head/tail/awk <path>`. Do NOT re-run the tool — output is capped regardless.