@heylemon/lemonade 0.4.4 → 0.4.7

package/bin/lemon-composio

@@ -36,17 +36,32 @@ case "$1" in
 
   execute)
     # Execute any Composio tool by slug
-    # Usage: lemon-composio execute TOOL_SLUG '{"param": "value"}'
-    [[ -z "$2" ]] && echo "Usage: lemon-composio execute <TOOL_SLUG> [json_parameters]" && exit 1
+    # Usage: lemon-composio execute TOOL_SLUG '{"param": "value"}' [--account=<id>]
+    [[ -z "$2" ]] && echo "Usage: lemon-composio execute <TOOL_SLUG> [json_parameters] [--account=<id>]" && exit 1
 
     tool_slug="$2"
     params="${3:-{\}}"
+    account_id=""
 
-    # Build the request body
-    EXEC_JSON=$(jq -n \
-      --arg toolName "$tool_slug" \
-      --argjson parameters "$params" \
-      '{toolName: $toolName, parameters: $parameters}')
+    for arg in "${@:3}"; do
+      case "$arg" in
+        --account=*) account_id="${arg#*=}" ;;
+      esac
+    done
+
+    # Build the request body (include accountId only when specified)
+    if [[ -n "$account_id" ]]; then
+      EXEC_JSON=$(jq -n \
+        --arg toolName "$tool_slug" \
+        --argjson parameters "$params" \
+        --arg accountId "$account_id" \
+        '{toolName: $toolName, parameters: $parameters, accountId: $accountId}')
+    else
+      EXEC_JSON=$(jq -n \
+        --arg toolName "$tool_slug" \
+        --argjson parameters "$params" \
+        '{toolName: $toolName, parameters: $parameters}')
+    fi
 
     echo "$EXEC_JSON" | curl -s -X POST \
       -H "Authorization: Bearer ${GATEWAY_TOKEN}" \
@@ -72,11 +87,13 @@ Commands:
         lemon-composio search "post to linkedin"
         lemon-composio search "issues" --toolkit=github
 
-  execute <TOOL_SLUG> [json_parameters]
+  execute <TOOL_SLUG> [json_parameters] [--account=<id>]
       Execute a Composio tool by its slug.
+      Use --account to target a specific connected account when
+      multiple accounts exist for the same provider.
       Examples:
         lemon-composio execute JIRA_CREATE_ISSUE '{"summary":"Bug fix","project_key":"PROJ"}'
-        lemon-composio execute LINKEDIN_CREATE_POST '{"text":"Hello world!"}'
+        lemon-composio execute GMAIL_SEND_EMAIL '{"to":"a@b.com"}' --account=int_abc
 
   status
       Show which integrations the user has connected.

package/dist/agents/system-prompt.js

@@ -117,7 +117,7 @@ function buildConfirmationSection(isMinimal) {
         "",
         "Format:",
         "```",
-        "⚠️ CONFIRM: [brief action description]",
+        "CONFIRM: [brief action description]",
         "",
         "Action: [what will happen]",
         "To: [recipient/target]",
@@ -335,21 +335,22 @@ export function buildAgentSystemPrompt(params) {
         "Keep narration brief and value-dense; avoid repeating obvious steps.",
         "Use plain human language for narration unless in a technical context.",
         "",
-        "⚠️ 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.",
+        "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.",
+        "CRITICAL: 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.",
+        "CRITICAL: 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.",
         "Never reply with a list of approaches/options when a single tool call would suffice.",
+        "CRITICAL: NEVER stop after announcing what you're going to do. Do NOT say 'I'll check your LinkedIn' and then stop. Say it AND immediately do it in the same response — search, open browser, navigate, find the answer, and return it. The user should never have to ask twice. One request = one complete answer.",
         "For screenshots of native macOS windows: use Peekaboo (`peekaboo image`) via exec if the skill is available.",
         "",
         "## Third-Party App Requests (Trello, Jira, LinkedIn, Asana, HubSpot, Salesforce, Todoist, etc.)",
         "",
-        "⚠️ CRITICAL RULE: For ANY service not in the dedicated CLI list below, try `lemon-composio` FIRST. There are NO other CLIs. Running `trello`, `jira`, `composio`, `asana`, `hubspot`, or any bare command will FAIL. The ONLY command that works is `lemon-composio search` and `lemon-composio execute`. Do NOT run `which trello`, `trello --help`, `composio`, or try to discover CLIs. They do not exist.",
+        "CRITICAL RULE: For ANY service not in the dedicated CLI list below, try `lemon-composio` FIRST. There are NO other CLIs. Running `trello`, `jira`, `composio`, `asana`, `hubspot`, or any bare command will FAIL. The ONLY command that works is `lemon-composio search` and `lemon-composio execute`. Do NOT run `which trello`, `trello --help`, `composio`, or try to discover CLIs. They do not exist.",
         "",
         "Dedicated `lemon-*` CLIs (the COMPLETE list): lemon-gmail, lemon-calendar, lemon-drive, lemon-docs, lemon-sheets, lemon-slides, lemon-notion, lemon-slack, lemon-youtube, lemon-twitter, lemon-composio.",
         "ANYTHING not in this list → use `lemon-composio search`.",
@@ -366,17 +367,7 @@ export function buildAgentSystemPrompt(params) {
         "3. Do NOT disconnect without explicit user confirmation.",
         "",
         "### Task requests (do something WITH a service)",
-        "When the user mentions ANY service not in the dedicated CLI list, follow this EXACT sequence. Do ALL searching SILENTLY — the user should never see your search process:",
-        '1. Run `lemon-composio search "<what the user wants>"` — this is your FIRST action. No web search. No `which`. No `--help`. No questions.',
-        "2. If result shows `connected: true` → execute the tool immediately with `lemon-composio execute`.",
-        "3. If the search returns results but none match the exact action, try broader/different search terms SILENTLY. Do NOT tell the user you're retrying searches.",
-        "4. If the service IS connected but the specific action truly doesn't exist, open the browser to do it. Tell the user briefly: \"Let me do this in the browser — I'll have better control there.\" Do NOT mention Composio, tools, searches, integrations, or any technical details.",
-        '5. If result shows `connected: false` → include the `connectUrl` from the search result as plain text (no backticks, no bold, no brackets) e.g. lemon://connect?provider=jira. The app will automatically open the auth page. Say "Connecting [service name] for you: lemon://connect?provider=X" Then STOP and wait for them to complete the auth.',
-        "6. Once the user confirms they connected → execute the tool.",
-        "7. If `lemon-composio` has no results OR `lemon://connect` fails → use the browser as fallback. Open the service website, let the user log in, and complete the task via browser tools.",
-        "",
-        "### Already-connected services",
-        "If `lemon-composio search` shows a service as `connected: true`, do NOT try to connect it again. Do NOT output lemon://connect for an already-connected service. Just use the available tools directly.",
+        "When the user mentions ANY service not in the dedicated CLI list, use `lemon-composio` — see the 'Dynamic tool discovery' section below for the full flow. Do ALL searching SILENTLY — the user should never see your search process.",
         "",
         "### Account & Login Policy",
         "NEVER create accounts or sign up for services on behalf of the user. If a service requires login or account creation in the browser:",
@@ -432,10 +423,10 @@ export function buildAgentSystemPrompt(params) {
         "",
         "The response includes `connectedProviders` (all services the user has connected) and `serviceConnected` (whether the searched service is connected). Use these to determine connection status — even if no tools matched the query, `serviceConnected: true` means the user IS connected. Do NOT try to re-connect.",
         "",
-        "Then based on results:",
-        '1. **Tools found + connected** → Execute immediately: `lemon-composio execute <TOOL_SLUG> \'{"param": "value"}\'`. If the first search doesn\'t find the right tool, try different search terms (broader terms, service name only, etc.) before giving up.',
-        "2. **No tools found but `serviceConnected: true`** → The user IS connected but this specific action isn't available as a tool. Try a broader search first (e.g. just the service name). If still nothing, tell the user: \"Let me do this in the browser — I'll have better control there.\" Then use the browser. Do NOT try to connect again.",
-        "3. **Not connected (`serviceConnected: false`)** → Include the `connectUrl` from the result as plain text: lemon://connect?provider=X. NEVER output a connect URL if `serviceConnected` is true or if the provider appears in `connectedProviders`.",
+        "Do ALL searching SILENTLY — never narrate retries or internal search process. Then based on results:",
+        "1. **Tools found + connected** → Execute immediately with `lemon-composio execute`. If the first search doesn't find the right tool, try broader/different search terms SILENTLY before giving up.",
+        "2. **No tools found but `serviceConnected: true`** → The user IS connected but this specific action isn't available as a tool. Try a broader search first (e.g. just the service name). If still nothing, tell the user: \"Let me do this in the browser — I'll have better control there.\" Then use the browser. Do NOT try to connect again. NEVER output a connect URL for an already-connected service.",
+        '3. **Not connected (`serviceConnected: false`)** → Include the `connectUrl` from the result as plain text (no backticks, no bold, no brackets): lemon://connect?provider=X. Say "Connecting [service name] for you: lemon://connect?provider=X" Then STOP and wait for them to complete the auth. Once the user confirms, execute the tool.',
         '4. **Connect fails or no results at all** → Tell the user: "Let me do this in the browser — I\'ll have better control there." Then use the browser directly.',
         "",
         "Example flows:",
@@ -445,6 +436,15 @@ export function buildAgentSystemPrompt(params) {
         "",
         "**Check what's connected:** `lemon-composio status`",
         "",
+        "### Multi-account support",
+        "Search results and status now include `connectedAccounts` — an array of all connected accounts with `provider`, `email`, and `accountId`.",
+        "Each tool in search results also has an `accounts` array showing which accounts can run that tool.",
+        "When the user has multiple accounts for the same provider (e.g. two Gmail accounts), pick the right one based on context:",
+        '- If the user says "work email" or "personal calendar", match by the account email.',
+        '- If unclear which account to use, ask once: "You have multiple Gmail accounts connected (work@company.com, personal@gmail.com). Which one should I use?"',
+        "- Pass the chosen account to execute: `lemon-composio execute TOOL_SLUG '{...}' --account=<accountId>`",
+        "- If only one account exists for the provider, you don't need `--account` — it will be used automatically.",
+        "",
         "### Browser tool (Lemonade's dedicated browser only)",
         "For general websites without a CLI tool, or as fallback when Composio fails, use Lemonade's dedicated `browser` tool (Playwright-managed).",
         '**Never open URLs in the user\'s personal browser.** Do not use `exec open "URL"`, `open -a "Google Chrome"`, or AppleScript to launch URLs. All web browsing goes through the `browser` tool with `profile="lemonade"`.',
@@ -693,7 +693,7 @@ export function buildAgentSystemPrompt(params) {
     }
     // Skip silent replies for subagent/none modes
     if (!isMinimal) {
-        lines.push("## Silent Replies", `When you have nothing to say, respond with ONLY: ${SILENT_REPLY_TOKEN}`, "", "⚠️ Rules:", "- It must be your ENTIRE message — nothing else", `- Never append it to an actual response (never include "${SILENT_REPLY_TOKEN}" in real replies)`, "- Never wrap it in markdown or code blocks", "", `❌ Wrong: "Here's help... ${SILENT_REPLY_TOKEN}"`, `❌ Wrong: "${SILENT_REPLY_TOKEN}"`, `✅ Right: ${SILENT_REPLY_TOKEN}`, "");
+        lines.push("## Silent Replies", `When you have nothing to say, respond with ONLY: ${SILENT_REPLY_TOKEN}`, "", "Rules:", "- It must be your ENTIRE message — nothing else", `- Never append it to an actual response (never include "${SILENT_REPLY_TOKEN}" in real replies)`, "- Never wrap it in markdown or code blocks", "", `❌ Wrong: "Here's help... ${SILENT_REPLY_TOKEN}"`, `❌ Wrong: "${SILENT_REPLY_TOKEN}"`, `✅ Right: ${SILENT_REPLY_TOKEN}`, "");
     }
     // Skip heartbeats for subagent/none modes
     if (!isMinimal) {

package/dist/build-info.json

@@ -1,5 +1,5 @@
 {
-  "version": "0.4.4",
-  "commit": "14b4f816be096f9b0e4fd8137bad2cee4f5055b4",
-  "builtAt": "2026-02-24T09:40:16.525Z"
+  "version": "0.4.7",
+  "commit": "65ee54b903b6ee3cec348f46541ef82ccbcb229c",
+  "builtAt": "2026-02-24T11:18:11.706Z"
 }

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

@@ -1 +1 @@
-e0ea56bc65e9032f0bba0b7dc14b9fd11af21ca1c5cf8ec22ccf517553455d56
+be64d0d57f69ca463e3b2ef7886f231d8d7b8e3ec39975cb49e8ce91204fc307

package/package.json

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

package/skills/gmail/SKILL.md

@@ -31,18 +31,9 @@ The recap covers:
 
 To create it, use the `cron` tool with `action=add`. Check `cron action=list` first to avoid duplicates.
 
-## Resolving Recipients (CRITICAL — never fabricate emails)
+## Resolving Recipients
 
-When the user says "send to Masood" or "email John from my team" and does NOT provide an email address:
-
-1. **Slack directory first** (fastest): Use the `message` tool with `action: "search-users"`, `channel: "slack"`, `query: "masood"`. This returns `name`, `handle`, and **`email`**. If found, use that email.
-2. **Gmail contacts**: Run `lemon-gmail find-contact "masood"` to search Google Contacts.
-3. **Sent email history**: Run `lemon-gmail sent-to "masood"` to find emails you've previously sent to someone with that name.
-4. **Ask the user**: If all lookups return nothing, ask: "I couldn't find Masood's email address. Could you provide it?"
-
-**NEVER fabricate an email address** like `masood@example.com` or guess a domain. Always resolve from real data or ask.
-
-**ALWAYS confirm** before sending: "I found Masood Ali (masood.ali@company.com). Should I send the email to this address?"
+**NEVER fabricate email addresses.** See the email skill for the full resolution flow (Slack → Gmail contacts → sent history → ask user). Always confirm the resolved email before sending.
 
 ## Sending with Attachments
 

package/skills/integrations/SKILL.md

@@ -1,10 +1,10 @@
 ---
 name: integrations
-description: Lemon integrations are configured at ~/.lemonade/skills/
+description: Manage and connect Lemon integrations
 metadata:
   lemonade:
     emoji: "🔗"
-    note: "Dynamic skills are auto-generated in ~/.lemonade/skills/"
+    note: "Dynamic skills are auto-generated when services are connected"
 ---
 
 # Lemon Integrations
@@ -25,11 +25,7 @@ when you connect services in Lemon Settings > Integrations.
 
 Provider IDs: gmail, slack, googlecalendar, googledrive, notion, youtube, jira, github, linear, trello, asana, etc.
 
-The generated skills are placed in `~/.lemonade/skills/` and include:
-- Full CLI paths for your machine
-- Proper authentication tokens
-
-If integrations aren't working, restart the Lemon app to regenerate them.
+Integration skills are auto-generated when you connect services. If integrations aren't working, restart the Lemon app to regenerate them.
 
 ## Connection Flow (Priority Order)
 
@@ -59,6 +55,16 @@ Some services (Jira, Trello, Asana, Confluence, etc.) require knowing the user's
 - **ClickUp:** https://app.clickup.com
 - **Monday.com:** https://monday.com
 
+## Multi-Account Support
+
+Users can connect multiple accounts for the same provider (e.g. two Gmail accounts, two Slack workspaces). When executing tools:
+
+- **Search results** include a `connectedAccounts` array with each account's `provider`, `email`, and `accountId`. Each tool also lists which `accounts` can run it.
+- **If only one account** exists for the provider, it's used automatically — no need to specify.
+- **If multiple accounts** exist, pick the right one based on context (e.g. "send from my work email" → match by email). If unclear, ask the user once.
+- **To target a specific account:** `lemon-composio execute TOOL_SLUG '{"params"}' --account=<accountId>`
+- **Status** (`lemon-composio status`) also returns `connectedAccounts` so you can see all accounts at a glance.
+
 ## Browser Fallback
 
 When CLI tools or Composio can't do something, ALWAYS use the browser. NEVER give up or tell the user to do it themselves.

package/skills/meetings/SKILL.md

@@ -28,14 +28,15 @@ lemon-calendar list
 
 Zoom does not have a `lemon-*` CLI. If the user specifically needs Zoom (not Google Meet), use the Composio integration if connected.
 
-### Check if Connected
+### Using Zoom via Composio
 
 ```bash
-curl -H "Authorization: Bearer $GATEWAY_TOKEN" \
-  https://voice-wisal.voice-f05.workers.dev/api/lemonade/tools/status
+lemon-composio search "create zoom meeting"
 ```
 
-Check `hasZoom` in response. If connected, use `ZOOM_CREATE_MEETING` Composio tool. If not, trigger OAuth: `lemon://connect?provider=zoom`
+If tools are found and connected, execute immediately. If Zoom is not connected, output the connect URL as plain text:
+
+lemon://connect?provider=zoom
 
 ## If NOT Connected
 
@@ -52,6 +53,6 @@ Include the connect URL as plain text in your reply. The app will automatically
 ## Remember
 
 - **`lemon-calendar` first** — For Google Calendar + Meet
-- **Never open browser** for calendar or meeting scheduling unless CLI fails
+- **`lemon-composio`** — For Zoom and other meeting services without a dedicated CLI
+- **Browser as last resort** — Only if CLI and Composio both fail
 - **Always include timezone** — Essential for meetings
-- **Be honest** — Offer to connect if not set up

package/skills/social-media/SKILL.md

@@ -4,8 +4,9 @@ Post to LinkedIn, Twitter/X, and other social platforms.
 
 ## Priority Order
 
-1. **`lemon-twitter`** CLI for Twitter/X — Always use this first
-2. **Browser** — Fallback only if CLI fails or service is not connected
+1. **`lemon-twitter`** CLI for Twitter/X
+2. **`lemon-composio`** for LinkedIn and other social platforms
+3. **Browser** — Fallback only if CLI/Composio fails or service is not connected
 
 ## Twitter/X
 
@@ -29,40 +30,26 @@ lemon-twitter search "query"
 
 ## LinkedIn
 
-LinkedIn does not currently have a `lemon-*` CLI. Use the Composio integration if connected, otherwise use browser as fallback.
+LinkedIn does not have a dedicated `lemon-*` CLI. Use `lemon-composio` to search and execute LinkedIn tools.
 
-### Check if Connected
+### Posting, checking activity, etc.
 
 ```bash
-curl -H "Authorization: Bearer $GATEWAY_TOKEN" \
-  https://voice-wisal.voice-f05.workers.dev/api/lemonade/tools/status
+lemon-composio search "create linkedin post"
+lemon-composio search "linkedin activity"
 ```
 
-Check `hasLinkedIn` in response.
+If tools are found and connected, execute immediately. If the specific action isn't available as a tool, use the browser as fallback.
 
-### If Connected (hasLinkedIn: true)
+### If Not Connected
 
-```bash
-curl -X POST \
-  -H "Authorization: Bearer $GATEWAY_TOKEN" \
-  -H "Content-Type: application/json" \
-  -d '{
-    "toolName": "LINKEDIN_CREATE_POST",
-    "parameters": {
-      "text": "Your post content here",
-      "visibility": "PUBLIC"
-    }
-  }' \
-  https://voice-wisal.voice-f05.workers.dev/api/lemonade/tools/execute
-```
-
-### If NOT Connected
+Output the connect URL as plain text:
 
-Include the connect URL as plain text in your reply. The app will automatically open the auth page:
+lemon://connect?provider=linkedin
 
-"LinkedIn isn't connected yet. Opening the connection page for you: lemon://connect?provider=linkedin"
+### If Connect Fails
 
-If connect fails, use the browser as fallback: navigate to `linkedin.com/feed`, click "Start a post"
+Use the browser as fallback — navigate to linkedin.com and complete the task directly.
 
 ## Content Guidelines
 
@@ -78,7 +65,7 @@ If connect fails, use the browser as fallback: navigate to `linkedin.com/feed`,
 - Hashtags and mentions common
 - Good for: quick updates, engagement
 
-## ⚠️ ALWAYS Confirm Before Posting
+## ALWAYS Confirm Before Posting
 
 **Never post without user approval.**