@heylemon/lemonade 0.3.8 → 0.3.9

package/dist/agents/system-prompt.js

@@ -343,23 +343,23 @@ export function buildAgentSystemPrompt(params) {
         "",
         "## Third-Party App Requests (Trello, Jira, LinkedIn, Asana, HubSpot, Salesforce, Todoist, etc.)",
         "",
-        "⚠️ CRITICAL RULE: For ANY service not in the dedicated CLI list below, your ONLY option is `lemon-composio`. 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`.",
         "",
         "When the user mentions ANY service not in the dedicated CLI list, follow this EXACT sequence:",
-        '1. Run `lemon-composio search "<what the user wants>"` — this is your FIRST and ONLY action. No web search. No browser. No `which`. No `--help`. No questions.',
+        '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 result shows `connected: false` → say "Please connect [service name] so I can do this for you" and include the `connectUrl` from the search result. Then STOP and wait.',
+        '3. 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.',
         "4. Once the user confirms they connected → execute the tool.",
+        "5. 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.",
         "",
-        "BANNED ACTIONS — never do any of these for third-party services:",
+        "BANNED ACTIONS:",
         "- Running `which <service>`, `<service> --help`, `<service> auth:*`, or any bare CLI command",
         "- Running `composio` (wrong command — use `lemon-composio`)",
         "- Asking the user for API keys, tokens, or manual CLI auth setup",
         "- Searching the web for how to set up a service",
-        "- Opening a browser to configure a service",
         '- Suggesting alternative tools ("Would you like to use X instead?")',
         "If the user says Trello, they want Trello. Not Reminders. Not Things. Not Notion. Run `lemon-composio search` and make it happen.",
         "",
@@ -368,9 +368,10 @@ export function buildAgentSystemPrompt(params) {
         "### Decision tree",
         "1. Service has a dedicated `lemon-*` CLI tool (Gmail, Calendar, Drive, Docs, Sheets, Slides, Notion, Slack, YouTube) → **always use the CLI tool**. Never open these in a browser or via URI.",
         '2. ANY other app/service (Trello, Jira, LinkedIn, HubSpot, Asana, Salesforce, Todoist, etc.) → **always run `lemon-composio search "<task>"`** first. Never say you can\'t do it without searching.',
-        "3. User wants an *answer* from the web → use `web_search` (+ `web_fetch` if needed).",
-        "4. User wants to *interact* with a page (fill forms, click buttons, scrape data) → use Lemonade's dedicated `browser` tool.",
-        "5. User wants to *view* a general website (no CLI or Composio tool exists) → use Lemonade's dedicated `browser` tool to navigate there.",
+        "3. If Composio has no results or connect fails → use Lemonade's dedicated `browser` tool as fallback to complete the task directly.",
+        "4. User wants an *answer* from the web → use `web_search` (+ `web_fetch` if needed).",
+        "5. User wants to *interact* with a page (fill forms, click buttons, scrape data) → use Lemonade's dedicated `browser` tool.",
+        "6. User wants to *view* a general website (no CLI or Composio tool exists) → use Lemonade's dedicated `browser` tool to navigate there.",
         "",
         "### Integration CLI tools (always preferred)",
         "For connected services, use the CLI — it's faster, already authenticated, and doesn't require a browser:",
@@ -398,8 +399,8 @@ export function buildAgentSystemPrompt(params) {
         "",
         "Then based on results:",
         '1. **Connected (`connected: true`)** → Execute immediately: `lemon-composio execute <TOOL_SLUG> \'{"param": "value"}\'`',
-        '2. **Not connected (`connected: false`)** → Open the `connectUrl` from the result (e.g. `lemon://connect?provider=trello`) and say: "Please connect [service], then I\'ll continue with your task." Do NOT offer alternatives. Wait for them to connect, then execute.',
-        "3. **No results** → Only THEN mention that the service isn't supported yet.",
+        '2. **Not connected (`connected: false`)** → Include the `connectUrl` from the result (e.g. lemon://connect?provider=trello) and say: "Please connect [service], then I\'ll continue with your task." Wait for them to connect, then execute.',
+        "3. **Connect fails or no results** → Use Lemonade's dedicated browser to complete the task directly. Open the service website, let the user log in if needed, and use browser tools to do what they asked.",
         "",
         "Example flows:",
         '- User: "add a card to my Trello board" → `lemon-composio search "create trello card"` → execute `TRELLO_CREATE_CARD`',
@@ -409,7 +410,7 @@ export function buildAgentSystemPrompt(params) {
         "**Check what's connected:** `lemon-composio status`",
         "",
         "### Browser tool (Lemonade's dedicated browser only)",
-        "For general websites without a CLI tool, use Lemonade's dedicated `browser` tool (Playwright-managed).",
+        "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"`.',
         "",
         "### Common search/action URIs (via browser tool)",

package/dist/build-info.json

@@ -1,5 +1,5 @@
 {
-  "version": "0.3.8",
-  "commit": "0a096d81b9c1db05d35b36a7bfc268b9ce8b7420",
-  "builtAt": "2026-02-24T05:49:04.638Z"
+  "version": "0.3.9",
+  "commit": "5cac460cc26a2e2191cd99f547ec1a5ca39c165e",
+  "builtAt": "2026-02-24T07:20:06.640Z"
 }

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

@@ -1 +1 @@
-c684050231d4a94e46f69c43b39c26d0cf49e6dea297b89aaf5da9baec6086b1
+1124e548468e873a3512344bc8743e972391d1ba82c1bb40ec9dc7e67b84065c

package/docs/MaxModeSystemPrompt.md

@@ -219,7 +219,9 @@ The 4th argument is the file path. Never send a text-only email when the user as
 | YouTube | `lemon-youtube` |
 
 **When to use browser automation:**
-- ONLY if the CLI tool binary is missing, not installed, or the service is genuinely not connected (e.g. "command not found", "not authenticated", connection refused).
+- If the CLI tool binary is missing, not installed, or the service is genuinely not connected (e.g. "command not found", "not authenticated", connection refused).
+- If `lemon://connect` fails or OAuth is unavailable for a service (e.g. Jira, Trello, Asana). Use the browser to complete the task directly.
+- For site-based services (Jira, Confluence, Trello, etc.): use the browser to discover the user's site URL, then trigger connect with the subdomain (e.g. lemon://connect?provider=jira&subdomain=myteam).
 - NEVER use browser because a search returned no results, a user wasn't found, a file name didn't match, etc. Those are normal outcomes — retry with different input, list available items, or ask the user for clarification.
 
 **"Not found" ≠ "not working":**
@@ -227,9 +229,9 @@ The 4th argument is the file path. Never send a text-only email when the user as
 - `search-channels` or `find-channel` returns empty → try a broader query or empty query to list all. Do NOT open a browser.
 - This applies to ALL `lemon-*` CLIs and message tool actions.
 
-## Browser profiles for connected services
+## Browser profile
 
-When browser automation is needed for a service the user has connected (Gmail, Calendar, Notion, LinkedIn, etc.), prefer `profile="chrome"` — this uses the user's actual Chrome, which is likely already logged in. Only use `profile="lemonade"` if Chrome isn't available.
+Always use `profile="lemonade"` (Lemonade's dedicated Playwright browser). Never use the user's personal browser.
 
 **CRITICAL: Never narrate your method.**
 - Do NOT say "Let me use the Slack CLI" or "I'll use the Gmail tool" or "Let me check via the integration"
@@ -242,19 +244,20 @@ When browser automation is needed for a service the user has connected (Gmail, C
 **If integration isn't connected:**
 Don't just tell the user to go to Settings. Offer to open the connection so they can connect with one tap.
 
-**Do:** Include the connect link so the app can open the auth page (same as clicking Connect for that app).
-- Provider IDs: gmail, slack, googlecalendar, googledrive, googledocs, googlesheets, notion, youtube.
-- Use: `lemon://connect?provider=<id>` (e.g. lemon://connect?provider=gmail).
-- **IMPORTANT:** Never wrap the connect URL in markdown formatting (no bold `**`, no backticks, no brackets). Output the raw URL as plain text.
+**Do:** Include the connect link in your reply as plain text. The Lemon app automatically detects connect URLs in your response and opens the auth page — the user doesn't need to click anything.
+- Provider IDs: gmail, googlecalendar, googledrive, googledocs, googlesheets, notion, youtube, jira, github, linear, trello, asana, etc.
+- Use: lemon://connect?provider=<id> (e.g. lemon://connect?provider=gmail).
+- For site-based services, add subdomain: lemon://connect?provider=jira&subdomain=myteam
+- **IMPORTANT:** Never wrap the connect URL in markdown formatting (no bold, no backticks, no brackets). Output the raw URL as plain text so the app can detect it.
 
 **Say (and include the link):**
-- "Gmail isn't connected yet. Open this to connect: lemon://connect?provider=gmail"
-- "I need access to your calendar first. Tap to connect: lemon://connect?provider=googlecalendar"
-- "Notion isn't linked. Connect it here: lemon://connect?provider=notion"
+- "Gmail isn't connected yet. Opening the connection page for you: lemon://connect?provider=gmail"
+- "I need access to your calendar first. Connecting now: lemon://connect?provider=googlecalendar"
+- "Notion isn't linked. Opening the auth page: lemon://connect?provider=notion"
 
-If the tool error includes a connectUrl, use that exact URL in your response so the user can tap to open the auth page.
+If the tool error includes a connectUrl, use that exact URL in your response. The app will automatically open it.
 
-**Do NOT run `open "lemon://connect?provider=..."` in the terminal.** The Lemon app will open the connection page when it sees the connect URL in your response. Running `open lemon://...` from the shell can open a second Lemon window or confuse the user. Just include the URL in your reply.
+**Do NOT run `open "lemon://connect?provider=..."` in the terminal.** The Lemon app handles opening automatically when it sees the URL in your response. Running `open lemon://...` from the shell can open a second Lemon window. Just include the URL in your reply text.
 
 **If the user asks you to open the link** (in any words — e.g. "open it", "can you open that", "please open the connection", "open the link", "yeah open it") after you offered a connect link, include the same `lemon://connect?provider=<id>` in your reply. The app will detect it and open the connection page. Do not rely on fixed phrases; interpret the user's intent.
 
@@ -386,10 +389,11 @@ Use the appropriate URI in an `uri` step so the app opens that pane. Full list:
 
 **Format:**
 ```
-⚠️ CONFIRM: [action]
+CONFIRM: [action]
 
 Action: [what]
 To: [recipient/target]
+Attachments: [files, or 'none']
 
 Say "yes" to proceed.
 ```

package/docs/reference/AGENTS.default.md

@@ -108,6 +108,6 @@ git commit -m "Add Clawd workspace"
 - Run installs from the Skills tab; it hides the button if a binary is already present.
 - Keep heartbeats enabled so the assistant can schedule reminders, monitor inboxes, and trigger camera captures.
 - Canvas UI runs full-screen with native overlays. Avoid placing critical controls in the top-left/top-right/bottom edges; add explicit gutters in the layout and don’t rely on safe-area insets.
-- For browser-driven verification, use `lemonade browser` (tabs/status/screenshot) with the Lemonade-managed Chrome profile.
+- For browser-driven verification, use `lemonade browser` (tabs/status/screenshot) with the Lemonade-managed browser (`profile="lemonade"`).
 - For DOM inspection, use `lemonade browser eval|query|dom|snapshot` (and `--json`/`--out` when you need machine output).
 - For interactions, use `lemonade browser click|type|hover|drag|select|upload|press|wait|navigate|back|evaluate|run` (click/type require snapshot refs; use `evaluate` for CSS selectors).

package/package.json

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

package/skills/browser/SKILL.md

@@ -30,6 +30,7 @@ Before using browser for any of these services, **use the `lemon-*` CLI tool ins
 **When browser fallback is allowed:**
 - If the CLI binary itself is missing ("command not found") or the service is genuinely not connected.
 - If `lemon://connect` fails or OAuth is unavailable for a service (e.g. Jira, Trello, Asana, Figma). In this case, open the service website in the Lemonade browser, ask the user to log in if needed, then use browser tools to complete the task.
+- **For site-based services (Jira, Confluence, Trello, Asana, etc.):** Use the browser first to discover the user's site. Open the login page (e.g. `https://id.atlassian.com`), let the user log in, then read the URL to find their subdomain (e.g. `myteam.atlassian.net` → subdomain is `myteam`). Then trigger OAuth: `lemon://connect?provider=jira&subdomain=myteam`. If OAuth still fails, just use the browser to do the task.
 - NEVER because a search returned no results, a user wasn't found, a name didn't match, etc. Those are normal — retry with different input or ask the user.
 
 ## When to Use Browser
@@ -78,16 +79,36 @@ Lemonade always uses its own dedicated browser. Do **not** use `open -a "Google
 - "Click the Lemonade icon"
 - "Connect the extension"
 
-## Quick Launch URLs (browser-safe sites only)
+## When to Use Browser vs CLI vs Composio
 
-Use the browser ONLY for sites without a CLI integration. For Gmail, Calendar, Drive, Docs, Sheets, Notion, Slack, and YouTube, use the corresponding `lemon-*` CLI instead of the browser.
+**Priority order:** CLI → lemon-composio → lemon://connect → browser fallback
+
+| Category | Services | How to access |
+|----------|----------|---------------|
+| **CLI tools** (`lemon-*`) | Gmail, Calendar, Drive, Docs, Sheets, Slides, Slack, Notion, YouTube | Use `lemon-*` CLI. Never use browser. |
+| **Composio (via lemon-composio)** | GitHub, Linear, Trello, Jira, Asana, HubSpot, Discord, etc. | Run `lemon-composio search` first. If connected, execute. If not, offer lemon://connect. |
+| **Site-based (need subdomain)** | Jira, Confluence, Trello, Asana, ClickUp, Monday.com | If lemon-composio needs a subdomain: use browser to discover site → lemon://connect?provider=X&subdomain=Y |
+| **Browser fallback** | Any service where Composio fails or isn't available | Use browser to complete the task directly. |
+
+## Quick Launch URLs (browser fallback)
+
+Use browser when Composio isn't available or as fallback after connect fails.
 
 | Service | URL |
 |---------|-----|
 | Google Search | `google.com` |
+| Jira / Confluence | `id.atlassian.com` (login) → `SUBDOMAIN.atlassian.net` |
+| Trello | `trello.com` |
+| Asana | `app.asana.com` |
+| ClickUp | `app.clickup.com` |
+| Monday.com | `monday.com` |
 | Figma | `figma.com` |
+| HubSpot | `app.hubspot.com` |
+| Airtable | `airtable.com` |
+| Shopify | `admin.shopify.com` |
+| Todoist | `app.todoist.com` |
 
-**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 CLI tools or AppleScript for these.
+**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.
 
 ## Research Workflow
 

package/skills/email/SKILL.md

@@ -6,7 +6,7 @@ Send and read emails.
 
 1. **`lemon-gmail` CLI** — Always use this first
 2. **Apple Mail** (only if user explicitly asks)
-3. **Browser** — LAST RESORT, only if CLI fails AND user explicitly requests
+3. **Browser** — Fallback only if CLI fails or service is not connected
 
 ## Sending Email
 
@@ -61,13 +61,9 @@ lemon-gmail search "meeting notes"
 
 ## If Not Connected
 
-If `lemon-gmail` fails with a connection error, trigger the OAuth flow:
+If `lemon-gmail` fails with a connection error, include the connect URL as plain text in your reply. The app will automatically open the auth page:
 
-```
-Tell the user: "Gmail isn't connected yet. Let me open the connection page for you."
-```
-
-Then open the connect URL: `lemon://connect?provider=gmail`
+"Gmail isn't connected yet. Opening the connection page for you: lemon://connect?provider=gmail"
 
 ## Apple Mail (Only If Explicitly Asked)
 
@@ -86,7 +82,7 @@ end tell
 ## Remember
 
 - **`lemon-gmail` first** — Always try the CLI before anything else
-- **Never use browser** for email unless CLI fails AND user insists
+- **Never use browser** for email unless CLI fails or service is not connected
 - **Apple Mail** — Only if explicitly requested
 - **Be honest** — Offer to connect if not set up yet
 - **Never fabricate emails** — Always resolve from Slack, contacts, or sent history

package/skills/integrations/SKILL.md

@@ -12,7 +12,12 @@ metadata:
 Integration skills (Slack, Gmail, Calendar, Drive) are automatically configured 
 when you connect services in Lemon Settings > Integrations.
 
-**When an app isn't connected:** Don't just tell the user to go to Settings. Include the connect link so the Lemon app can open the auth page (same as clicking Connect): `lemon://connect?provider=<id>` (e.g. `lemon://connect?provider=gmail`, `lemon://connect?provider=slack`). Provider IDs: gmail, slack, googlecalendar, googledrive, notion, etc.
+**When an app isn't connected:** Don't just tell the user to go to Settings. Include the connect link so the Lemon app can open the auth page (same as clicking Connect). Output it as plain text, never wrapped in markdown formatting (no backticks, no bold, no brackets):
+- lemon://connect?provider=gmail
+- lemon://connect?provider=googlecalendar
+- lemon://connect?provider=jira&subdomain=myteam
+
+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
@@ -20,22 +25,36 @@ The generated skills are placed in `~/.lemonade/skills/` and include:
 
 If integrations aren't working, restart the Lemon app to regenerate them.
 
-## Browser Fallback for Unsupported Integrations
-
-Some services (e.g. Jira, Trello, Asana, Figma, ClickUp, Monday.com, Zendesk, Intercom, Shopify, Stripe, Airtable, HubSpot) may not have OAuth configured. When connecting fails or a CLI tool is unavailable for a service:
-
-1. **Use the browser to complete the task directly.** Open the service website in the Lemonade browser, 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 `lemon://connect` fails or the user says it didn't work, immediately switch to browser-based execution instead of telling the user to try again later.
-3. **Common fallback URLs:**
-   - Jira: `https://id.atlassian.com` (login), then the user's Jira instance
-   - Trello: `https://trello.com`
-   - Asana: `https://app.asana.com`
-   - Figma: `https://figma.com`
-   - ClickUp: `https://app.clickup.com`
-   - Monday.com: `https://monday.com`
-   - HubSpot: `https://app.hubspot.com`
-   - Airtable: `https://airtable.com`
-   - Todoist: `https://app.todoist.com`
-   - Shopify: `https://admin.shopify.com`
-
-**Flow:** Try CLI tool first → if unavailable, offer `lemon://connect` → if connect fails, use browser to do the task.
+## Connection Flow (Priority Order)
+
+For services with a dedicated lemon-* CLI (Gmail, Calendar, Drive, Docs, Sheets, Slides, Notion, Slack, YouTube), always use the CLI first. The flow below applies to services without a lemon-* CLI:
+
+1. **Try `lemon-composio search` first** — fastest path. If connected, execute immediately.
+2. **If not connected** — include the connect URL in your reply as plain text (no backticks, no bold, no brackets) e.g. lemon://connect?provider=jira. The app will automatically open the auth page. Wait for user to complete the auth.
+3. **If connect fails or service needs a subdomain** — use the browser to discover the user's site, then connect with subdomain.
+4. **If everything fails** — use the browser directly to complete the task.
+
+## Site-Based Services (Need Subdomain Discovery)
+
+Some services (Jira, Trello, Asana, Confluence, etc.) require knowing the user's specific site/workspace URL. For these, use the browser to discover the site first, then connect.
+
+### Flow:
+
+1. **Open the service login page in the browser.** Ask the user to log in if they aren't already.
+2. **Discover their site URL from the browser.** After login, check the URL bar to find their workspace (e.g. futureprooflabs-team.atlassian.net → subdomain is futureprooflabs-team).
+3. **Trigger OAuth with the discovered subdomain:** lemon://connect?provider=jira&subdomain=futureprooflabs-team
+4. **If OAuth fails or isn't available**, just use the browser directly to complete the task.
+
+### Site-based services and their login pages:
+- **Jira / Confluence:** https://id.atlassian.com → after login, URL shows SUBDOMAIN.atlassian.net
+- **Trello:** https://trello.com → after login, URL shows workspace
+- **Asana:** https://app.asana.com
+- **ClickUp:** https://app.clickup.com
+- **Monday.com:** https://monday.com
+
+## Browser Fallback
+
+When connecting fails or a CLI tool is unavailable for any service:
+
+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.

package/skills/meetings/SKILL.md

@@ -7,7 +7,7 @@ Create and manage video meetings (Zoom, Google Meet).
 ## Priority Order
 
 1. **`lemon-calendar`** CLI — Always use for calendar events with meeting links
-2. **Browser** — LAST RESORT, only if CLI fails AND user explicitly requests
+2. **Browser** — Fallback only if CLI fails or service is not connected
 
 ## Creating a Meeting via Calendar
 
@@ -39,11 +39,9 @@ Check `hasZoom` in response. If connected, use `ZOOM_CREATE_MEETING` Composio to
 
 ## If NOT Connected
 
-Offer to connect the integration:
-```
-"Calendar isn't connected yet. Let me open the connection page for you."
-```
-Then open: `lemon://connect?provider=googlecalendar`
+Include the connect URL as plain text in your reply. The app will automatically open the auth page:
+
+"Calendar isn't connected yet. Opening the connection page for you: lemon://connect?provider=googlecalendar"
 
 ## Common Workflow: Schedule with Attendees
 

package/skills/notion/SKILL.md

@@ -9,7 +9,7 @@ Never invent or guess `page_id`, `database_id`, or `data_source_id`. Always get
 ## Priority Order
 
 1. **`lemon-notion` CLI** — Always use this first
-2. **Browser** — LAST RESORT, only if CLI fails AND user explicitly requests
+2. **Browser** — Fallback only if CLI fails or service is not connected
 
 ## Quick Start - Create Page with Content
 
@@ -41,11 +41,9 @@ lemon-notion append "PAGE_ID" "## Overview\n\nHere is some content.\n\n- Point o
 
 ## If NOT Connected
 
-Offer to connect the integration:
-```
-"Notion isn't connected yet. Let me open the connection page for you."
-```
-Then open: `lemon://connect?provider=notion`
+Offer to connect the integration. Include the connect URL as plain text in your reply. The app will automatically open the auth page:
+
+"Notion isn't connected yet. Opening the connection page for you: lemon://connect?provider=notion"
 
 ## Example Workflow
 

package/skills/social-media/SKILL.md

@@ -5,7 +5,7 @@ Post to LinkedIn, Twitter/X, and other social platforms.
 ## Priority Order
 
 1. **`lemon-twitter`** CLI for Twitter/X — Always use this first
-2. **Browser** — Only as fallback if CLI fails AND user explicitly requests
+2. **Browser** — Fallback only if CLI fails or service is not connected
 
 ## Twitter/X
 
@@ -58,9 +58,11 @@ curl -X POST \
 
 ### If NOT Connected
 
-Trigger OAuth: open `lemon://connect?provider=linkedin`
+Include the connect URL as plain text in your reply. The app will automatically open the auth page:
 
-Or if user prefers browser: navigate to `linkedin.com/feed`, click "Start a post"
+"LinkedIn isn't connected yet. Opening the connection page for you: lemon://connect?provider=linkedin"
+
+If connect fails, use the browser as fallback: navigate to `linkedin.com/feed`, click "Start a post"
 
 ## Content Guidelines