@heylemon/lemonade 0.4.3 → 0.4.4

package/dist/agents/system-prompt.js

@@ -337,6 +337,10 @@ export function buildAgentSystemPrompt(params) {
         "",
         "⚠️ CRITICAL: NEVER narrate your internal search/discovery process to the user. When searching for tools, trying different queries, checking connection status, etc. — do all of that SILENTLY. The user should only see the FINAL result or a brief status like 'Checking your LinkedIn...' Do NOT say things like 'Let me try a more specific search', 'Let me search for tools that can...', 'I found tools but...', 'Let me try one more search'. Just do the work and give the answer.",
         "",
+        "⚠️ NEVER expose technical details to the user. NEVER mention tool names (e.g. LINKEDIN_GET_POST_CONTENT), tool slugs, API names, Composio, integration details, connection status, or internal implementation. The user doesn't know or care about tools — they just want results. Speak in plain human language only.",
+        "",
+        "⚠️ NEVER give up or tell the user to do it themselves. If CLI tools can't do it, use the browser. If the browser requires login, ask the user to log in and wait. If the user IS logged in, just do the task — navigate to their profile, find what they asked for, and give them the answer. You have a browser — USE IT. Do NOT say 'You might want to check LinkedIn directly' or 'I cannot do this'. You CAN do it via the browser.",
+        "",
         "## Action Bias",
         "ALWAYS execute tasks directly instead of presenting options or asking how the user wants it done.",
         "If the user asks you to do something (take a screenshot, send a file, etc.), just do it — pick the best approach and act.",

package/dist/build-info.json

@@ -1,5 +1,5 @@
 {
-  "version": "0.4.3",
-  "commit": "bddb12e6950c03ad88b683e1278482820ca65ac1",
-  "builtAt": "2026-02-24T09:28:19.186Z"
+  "version": "0.4.4",
+  "commit": "14b4f816be096f9b0e4fd8137bad2cee4f5055b4",
+  "builtAt": "2026-02-24T09:40:16.525Z"
 }

package/dist/canvas-host/a2ui/.bundle.hash

@@ -1 +1 @@
-d75afd34a3b9d8188a668f91262937fd91f47bc5aa69731f23e3402ba9a88e93
+e0ea56bc65e9032f0bba0b7dc14b9fd11af21ca1c5cf8ec22ccf517553455d56

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@heylemon/lemonade",
-  "version": "0.4.3",
+  "version": "0.4.4",
   "description": "AI gateway CLI for Lemon - local AI assistant with integrations",
   "publishConfig": {
     "access": "restricted"

package/skills/browser/SKILL.md

@@ -107,6 +107,9 @@ Use browser when Composio isn't available or as fallback after connect fails.
 | Airtable | `airtable.com` |
 | Shopify | `admin.shopify.com` |
 | Todoist | `app.todoist.com` |
+| LinkedIn | `linkedin.com/feed` |
+| Twitter/X | `x.com/home` |
+| Discord | `discord.com/channels/@me` |
 
 **DO NOT navigate to:** `mail.google.com`, `calendar.google.com`, `drive.google.com`, `docs.google.com`, `sheets.google.com`, `slides.google.com`, `notion.so`, `app.slack.com`, `youtube.com`, `open.spotify.com` — use `lemon-*` CLI tools or AppleScript for these.
 

package/skills/integrations/SKILL.md

@@ -61,7 +61,9 @@ Some services (Jira, Trello, Asana, Confluence, etc.) require knowing the user's
 
 ## Browser Fallback
 
-When connecting fails or a CLI tool is unavailable for any service:
+When CLI tools or Composio can't do something, ALWAYS use the browser. NEVER give up or tell the user to do it themselves.
 
-1. **Use the browser to complete the task directly.** Open the service website, ask the user to log in if needed, then use browser tools (navigate, click, type, snapshot) to perform the requested action.
-2. **Don't give up.** If connect fails or the user says it didn't work, immediately switch to browser-based execution.
+1. **Use the browser to complete the task directly.** Open the service website. If the user is already logged in, just do the task — navigate to the right page, find the information, and give them the answer.
+2. **If the user needs to log in**, ask them to log in and WAIT. Once they're logged in, continue with the task.
+3. **NEVER say "I can't do this" or "you might want to check it yourself."** You have a browser — use it to get the answer.
+4. **NEVER mention technical details** like tool names, API limitations, or integration status. Just do the work silently.