@heylemon/lemonade 0.1.2 → 0.1.4

package/bin/lemon-slack

@@ -28,7 +28,7 @@ case "$1" in
     ;;
   channels)
     api_call POST "/api/lemonade/tools/execute" \
-        '{"toolName": "SLACK_LIST_ALL_CHANNELS", "parameters": {}}'
+        '{"toolName": "SLACK_LIST_ALL_CHANNELS", "parameters": {"limit": 500, "types": "public_channel,private_channel"}}'
     ;;
   dms)
     api_call POST "/api/lemonade/tools/execute" \
@@ -51,7 +51,7 @@ case "$1" in
   find-channel)
     [[ -z "$2" ]] && echo "Usage: lemon-slack find-channel <name>" && exit 1
     api_call POST "/api/lemonade/tools/execute" \
-        '{"toolName": "SLACK_FIND_CHANNELS", "parameters": {"query": "'"$2"'"}}'
+        '{"toolName": "SLACK_FIND_CHANNELS", "parameters": {"query": "'"$2"'", "types": "public_channel,private_channel"}}'
     ;;
   upload)
     [[ -z "$2" ]] || [[ -z "$3" ]] && echo "Usage: lemon-slack upload <channel_or_user_id> <file_path> [message]" && exit 1

package/dist/agents/system-prompt.js

@@ -415,6 +415,12 @@ export function buildAgentSystemPrompt(params) {
         "ALWAYS use the `cron` tool (action: add/update/remove/list/run/status) for managing cron jobs and reminders.",
         "NEVER use `exec` or shell commands to read/write cron files (e.g. ~/.lemonade/cron/jobs.json) directly — the gateway cron service will not detect the change.",
         "",
+        "### Cancelling / stopping reminders",
+        "When the user asks to stop, cancel, turn off, or remove a reminder or recurring notification — in ANY phrasing — you MUST actually remove the cron job. Do NOT just acknowledge verbally.",
+        "Steps: 1) `cron` action:list → find the matching job(s) by name/text/schedule, 2) `cron` action:remove with the jobId for each match.",
+        "Common phrasings that mean 'remove the cron job': 'stop sending me…', 'I don't need those anymore', 'cancel my reminders', 'turn off notifications', 'no more hourly…', etc.",
+        "If multiple jobs could match, list them and confirm which to remove. If only one matches, remove it immediately.",
+        "",
         "## Lemonade CLI Quick Reference",
         "Lemonade is controlled via subcommands. Do not invent commands.",
         "To manage the Gateway daemon service (start/stop/restart):",

package/dist/agents/tools/cron-tool.js

@@ -122,7 +122,7 @@ ACTIONS:
 - list: List jobs (use includeDisabled:true to include disabled)
 - add: Create job (requires job object, see schema below)
 - update: Modify job (requires jobId + patch object)
-- remove: Delete job (requires jobId)
+- remove: Delete/cancel job (requires jobId). IMPORTANT: When user asks to stop, cancel, or turn off any reminder/notification, you MUST list jobs first, then remove the matching one(s). Do not just acknowledge — actually remove.
 - run: Trigger job immediately (requires jobId)
 - runs: Get job run history (requires jobId)
 - wake: Send wake event (requires text, optional mode)

package/dist/build-info.json

@@ -1,5 +1,5 @@
 {
-  "version": "0.1.2",
-  "commit": "edb23508314733d07cc2a18f0affbb5f72e9931b",
-  "builtAt": "2026-02-20T23:05:14.469Z"
+  "version": "0.1.4",
+  "commit": "880ce819d9b8b545e14bf2e643af833ed51361f2",
+  "builtAt": "2026-02-21T09:49:07.513Z"
 }

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

@@ -1 +1 @@
-3641485d183a81ebf5afc4f93c9146ff5dfc77d261ef3e4c62f92e826641730d
+266bfc5a1d9dd1a9db1ad07062f473788689bdfc7d2e7bff2fafc0f2a0922fb9

package/package.json

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

package/skills/slack/SKILL.md

@@ -37,8 +37,15 @@ Use the `message` tool for Slack operations whenever possible. It talks directly
 ### Send to Channel Workflow
 
 1. Search for the channel: `message { action: "search-channels", channel: "slack", query: "general" }`
-2. Get the channel ID (e.g. `channel:C123ABC`)
-3. Send: `message { action: "send", channel: "slack", target: "channel:C123ABC", message: "Hello!" }`
+2. From the results, find the channel whose name **exactly matches** what the user asked for.
+3. Use that channel's ID (e.g. `channel:C123ABC`).
+4. Send: `message { action: "send", channel: "slack", target: "channel:C123ABC", message: "Hello!" }`
+
+**CRITICAL — Exact channel matching:**
+- NEVER send to a channel that doesn't exactly match the user's request. If the user says "lemon-internal", only use a channel literally named `lemon-internal` — not `techstack`, not `general`, not any other channel.
+- If search returns multiple results, pick the one whose name is an exact match.
+- If NO exact match exists, show the user the closest matches and ask them to clarify. Do NOT pick one yourself.
+- NEVER substitute a different channel because it "seems related" or is the closest fuzzy match.
 
 ## Fallback: lemon-slack CLI
 
@@ -68,6 +75,6 @@ lemon-slack upload "CHANNEL_OR_USER_ID" "/path/to/file.pdf" "Here's the report"
 ## Error Handling
 
 - **"User not found"** → The name may be misspelled. Try `message { action: "search-users", channel: "slack", query: "" }` with empty query to list everyone, then find the closest match. Ask the user if unsure. This is NOT a connection failure.
-- **"Channel not found"** → Try `message { action: "search-channels", channel: "slack", query: "" }` with empty query to list all. Pick the closest match.
+- **"Channel not found"** → Try `message { action: "search-channels", channel: "slack", query: "" }` with empty query to list all. Look for an exact name match. If none, show the user the available channels and ask which one they meant. NEVER send to a different channel than what was requested.
 - **NEVER fall back to browser** if a Slack command returns no results. Retry with different input or ask for clarification.
 - **NEVER open `app.slack.com` in a browser.** Slack is CLI/native only.