nothumanallowed 9.3.14 → 9.3.16

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "nothumanallowed",
-  "version": "9.3.14",
+  "version": "9.3.16",
   "description": "NotHumanAllowed — 38 AI agents + 58 tools + browser automation + web search. Streaming chat, headless Chrome CDP, multi-conversation, export. Gmail, Calendar, Drive, GitHub, Notion, Slack. Zero-dependency CLI.",
   "type": "module",
   "bin": {

package/src/commands/ui.mjs

@@ -1001,7 +1001,7 @@ export async function cmdUI(args) {
           if (toolResults.length > 0) {
             // Second LLM call with real tool results — forces the LLM to use actual data
             const toolContext = toolResults.map(t => `[${t.action} result]: ${t.result.slice(0, 3000)}`).join('\n\n');
-            const followUp = `The user asked: "${body.message}"\n\nI executed these tools and got REAL results:\n\n${toolContext}\n\nNow respond to the user based ONLY on the REAL data above. Do NOT invent or fabricate any information. Present the actual results clearly.`;
+            const followUp = `The user asked: "${body.message}"\n\nI executed these tools and got REAL results:\n\n${toolContext}\n\nNow respond conversationally based ONLY on the REAL data above. Do NOT output any JSON blocks — just natural text.`;
             try {
               fullResponse = await callLLM(config, enrichedSystemPrompt, followUp);
             } catch {
@@ -1256,12 +1256,14 @@ export async function cmdUI(args) {
           let finalResponse = fullResponse;
           if (toolResults.length > 0) {
             const toolContext = toolResults.map(t => `[${t.action} result]: ${t.result.slice(0, 3000)}`).join('\n\n');
-            const followUp = `The user asked: "${msg}"\n\nI executed these tools and got REAL results:\n\n${toolContext}\n\nNow respond to the user based ONLY on the REAL data above. Present the actual results clearly.`;
+            const followUp = `The user asked: "${msg}"\n\nI executed these tools and got REAL results:\n\n${toolContext}\n\nNow respond to the user conversationally based ONLY on the REAL data above. Present the results clearly. Do NOT output any JSON blocks — just natural text.`;
             sendSSE('tool_synthesis', {});
             try {
               finalResponse = await callLLMStream(config, enrichedPrompt, followUp, (chunk) => {
                 sendSSE('token', { content: chunk });
               });
+              // Strip any JSON blocks the LLM might have emitted anyway
+              finalResponse = finalResponse.replace(/```json[\s\S]*?```/g, '').trim();
             } catch {
               finalResponse = toolResults.map(t => `${t.action}: ${t.result}`).join('\n\n');
             }

package/src/constants.mjs

@@ -5,7 +5,7 @@ import { fileURLToPath } from 'url';
 const __filename = fileURLToPath(import.meta.url);
 const __dirname = path.dirname(__filename);
 
-export const VERSION = '9.3.14';
+export const VERSION = '9.3.16';
 export const BASE_URL = 'https://nothumanallowed.com/cli';
 export const API_BASE = 'https://nothumanallowed.com/api/v1';
 

package/src/services/tool-executor.mjs

@@ -74,14 +74,16 @@ export const DESTRUCTIVE_ACTIONS = new Set([
  */
 export const TOOL_DEFINITIONS = `
 You have access to the following tools. When the user's message requires an action,
-output EXACTLY ONE fenced JSON block per action:
+output one or more fenced JSON blocks:
 
 \`\`\`json
 {"action": "<tool_name>", "params": { ... }}
 \`\`\`
 
-You may include conversational text BEFORE or AFTER the JSON block. If no action
-is needed, respond normally without any JSON block.
+You can include multiple JSON blocks in one response for sequential actions.
+You may include conversational text BEFORE, BETWEEN, or AFTER JSON blocks.
+If no action is needed, respond normally without any JSON block.
+CRITICAL: Never output a JSON block as a "suggestion" or "let me try" — every JSON block WILL be executed immediately. Only output a JSON block when you are certain the action should be performed.
 
 TOOLS:
 
@@ -346,6 +348,7 @@ RULES:
 - The user's timezone is {{TIMEZONE}}.
 - CRITICAL: when creating calendar events, always use LOCAL time in format "YYYY-MM-DDTHH:MM:SS" WITHOUT any Z suffix or timezone offset.
 - LANGUAGE: Respond in {{LANGUAGE}}. All conversational text, explanations, and descriptions must be in {{LANGUAGE}}. Tool names and JSON blocks remain in English.
+- BROWSER TIP: When extracting data from a page, prefer browser_js with simple JavaScript over complex CSS selectors. Example: browser_js with code "document.body.innerText.slice(0, 3000)" to get all visible text, then parse it yourself. This is more reliable than guessing CSS selectors.
 `.trim();
 
 // ── Action Parser ────────────────────────────────────────────────────────────