loopengine 0.1.58 → 0.1.59

package/dist/web/agents-config-page.js

@@ -1308,7 +1308,7 @@ export const agentsConfigPageHtml = `<!doctype html>
         // secret nothing else has a copy of) gets the one confirm() this
         // whole tab uses — every other action here is a plain upsert,
         // nothing else to lose by clicking it again.
-        if (!confirm('Remove ' + varName + '? Any tool/ability relying on it falls back to its own default (if it has one) or starts failing until it\'s set again.')) return;
+        if (!confirm('Remove ' + varName + '? Any tool/ability relying on it falls back to its own default (if it has one) or starts failing until it is set again.')) return;
         btn.disabled = true;
         fetch('/agents/' + encodeURIComponent(name) + '/env/' + encodeURIComponent(varName), { method: 'DELETE' })
           .then(function (r) { return r.json().then(function (j) { return { ok: r.ok, body: j }; }); })

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "loopengine",
-  "version": "0.1.58",
+  "version": "0.1.59",
   "type": "module",
   "description": "Runtime for tool-using AI agents with a transparent ReAct loop.",
   "license": "MIT",

package/dist/core/system-skills/system-skills/composio-large-outputs/SKILL.md

@@ -1,25 +0,0 @@
----
-name: composio-large-outputs
-description: How to retrieve a gateway tool's real output when its result says storedInFile is true instead of returning the data inline.
----
-
-# Gateway tools with a large result
-
-Some gateway tools (Composio-sourced ones in particular) return a small
-pointer object instead of their real output when the actual result is
-too large to return inline:
-
-```
-{
-  "successful": true,
-  "storedInFile": true,
-  "tokenCount": 10234,
-  "outputFilePath": "/tmp/.../SOME_TOOL_OUTPUT_xxxxx.json"
-}
-```
-
-When you see `storedInFile: true` in a tool result, the real data is
-**not** in that object — it's in the file at `outputFilePath`. Call
-`system_read_file` with that exact path to retrieve the actual content
-before answering. Don't guess at an answer, summarize from the pointer
-alone, or claim you don't have the data — read the file first.