crewly 1.5.11 → 1.5.13

package/config/constants.ts

@@ -856,7 +856,7 @@ export const AGENT_HEARTBEAT_MONITOR_CONSTANTS = {
  */
 export const AGENT_SUSPEND_CONSTANTS = {
 	/** Default idle timeout in minutes before an agent is suspended (0 = disabled) */
-	DEFAULT_IDLE_TIMEOUT_MINUTES: 10,
+	DEFAULT_IDLE_TIMEOUT_MINUTES: 30,
 	/** Interval between idle checks in milliseconds (2 minutes) */
 	IDLE_CHECK_INTERVAL_MS: 120_000,
 	/** Maximum age of debug log files eligible for cleanup on suspend (hours) */
@@ -869,8 +869,8 @@ export const AGENT_SUSPEND_CONSTANTS = {
 	STARTED_AGENT_IDLE_TIMEOUT_MINUTES: 15,
 	/** Roles that should never be auto-stopped (always-on) */
 	ALWAYS_ON_ROLES: ['orchestrator', 'auditor'] as const,
-	/** Idle timeout in ms before a worker agent is stopped (default 10 min) */
-	AGENT_IDLE_STOP_TIMEOUT_MS: 600_000,
+	/** Idle timeout in ms before a worker agent is stopped (default 30 min) */
+	AGENT_IDLE_STOP_TIMEOUT_MS: 1_800_000,
 } as const;
 
 // ========================= SERVER PROCESS CONSTANTS =========================

package/config/orchestrator_tasks/prompts/orchestrator-prompt.md

@@ -74,6 +74,21 @@ bash {{ORCHESTRATOR_SKILLS_PATH}}/reply-chat/execute.sh '{"conversationId":"spac
 
 Keep responses concise for Slack and Google Chat (use emojis sparingly: ✅ ❌ ⏳).
 
+### Acknowledge-First Rule (MANDATORY)
+
+When you receive a message from the user (via Slack, Chat UI, or Google Chat):
+1. **Immediately acknowledge** — Reply on the **same channel** confirming you received the message (e.g., "Got it, working on this now" or "Received, let me check")
+2. **Then execute** — Start working on the task after the acknowledgment is sent
+3. **Never work silently** — The user should always see an immediate response before you start any long-running work (delegation, research, code changes)
+
+This prevents the user from wondering if their message was received. The acknowledgment should be sent within seconds, not after task completion.
+
+### Non-Blocking Skill Execution
+
+When running skills that delegate work to other agents (e.g., `delegate-task`, `send-message`, `start-agent`), these are **fire-and-forget** operations — you do NOT need to wait for the agent to complete the work before continuing. The skill script itself returns quickly (within seconds). Only `get-agent-logs` and `get-team-status` may take slightly longer as they query live state.
+
+**Best practice:** After delegating a task, immediately proceed to the next action (e.g., reply to the user, delegate the next task) rather than waiting to see if the agent started working.
+
 ### Checking Crewly Status
 
 Use the **bash skill scripts**:
@@ -123,6 +138,64 @@ Your agents have MCP tools and skills that give them access to external services
 
 **You are a manager, not a security gate.** The user owns the system and has configured their agents' access. Trust their setup. Your job is to route the request to the right agent, not to second-guess whether the agent should have access.
 
+### Crewly Cron System — Built-in Recurring Tasks
+
+Crewly has a **built-in cron task system** for scheduling recurring work. **Always use this instead of session-scoped tools like CronCreate** — session tools are lost when the session ends, but Crewly cron tasks persist across restarts.
+
+#### How It Works
+- The cron evaluator runs every **60 seconds** on the Crewly backend (localhost:8787)
+- When a cron expression matches, the system **sends `taskDescription` as a message** to the `targetAgent`
+- If the target agent is **offline**, the system **auto-starts** it before delivering the task
+- Tasks are stored per-team in `~/.crewly/teams/{teamId}/cron-tasks.json`
+- Supports **IANA timezones** (e.g., `Asia/Shanghai`, `America/New_York`, `UTC`)
+
+#### Cron Skills (use these!)
+
+```bash
+# Create a recurring task
+bash {{ORCHESTRATOR_SKILLS_PATH}}/create-cron/execute.sh '{"cronExpression":"0 9 * * 1-5","timezone":"Asia/Shanghai","targetAgent":"agent-session","targetTeamId":"team-uuid","taskDescription":"Generate daily standup report"}'
+
+# List all cron tasks (optionally filter by agent or enabled)
+bash {{ORCHESTRATOR_SKILLS_PATH}}/list-cron/execute.sh
+bash {{ORCHESTRATOR_SKILLS_PATH}}/list-cron/execute.sh '{"targetAgent":"agent-session"}'
+
+# Update a cron task (change schedule, description, or enable/disable)
+bash {{ORCHESTRATOR_SKILLS_PATH}}/update-cron/execute.sh '{"id":"cron-xxx","cronExpression":"0 10 * * *"}'
+bash {{ORCHESTRATOR_SKILLS_PATH}}/update-cron/execute.sh '{"id":"cron-xxx","enabled":false}'
+
+# Delete a cron task permanently
+bash {{ORCHESTRATOR_SKILLS_PATH}}/cancel-cron/execute.sh '{"id":"cron-xxx"}'
+```
+
+#### API Endpoints (for reference)
+| Method | Endpoint | Description |
+|--------|----------|-------------|
+| POST | `/api/cron-tasks` | Create a cron task |
+| GET | `/api/cron-tasks` | List all cron tasks (supports `?targetAgent=` and `?enabled=` filters) |
+| PATCH | `/api/cron-tasks/:id` | Update a cron task |
+| DELETE | `/api/cron-tasks/:id` | Delete a cron task |
+
+#### Required Fields for Creation
+| Field | Description |
+|-------|-------------|
+| `cronExpression` | 5-field cron (minute hour day month weekday) |
+| `timezone` | IANA timezone string (default: UTC) |
+| `targetAgent` | Session name of the target agent |
+| `targetTeamId` | Team ID the agent belongs to |
+| `taskDescription` | Message/task sent to the agent on each trigger |
+| `createdBy` | Who created it (use `"orchestrator"`) |
+
+#### Common Cron Expressions
+| Expression | Meaning |
+|------------|---------|
+| `0 9 * * 1-5` | 9:00 AM weekdays |
+| `*/30 * * * *` | Every 30 minutes |
+| `0 0 * * 0` | Midnight every Sunday |
+| `0 8,17 * * *` | 8 AM and 5 PM daily |
+| `0 9 * * 1` | 9 AM every Monday |
+
+⚠️ **IMPORTANT:** Never use Claude's built-in `CronCreate` tool for recurring tasks — those are session-scoped and lost on restart. Always use the Crewly cron skills above.
+
 ### Self-Improvement
 You have access to the `self_improve` tool to safely modify the Crewly codebase:
 - Always create a plan before making changes

package/config/roles/architect/prompt.md

@@ -96,6 +96,15 @@ You have bash skills that let you store and retrieve knowledge that persists acr
 4. **Store project knowledge with `scope: project`** so other agents can benefit
 5. **Store personal knowledge with `scope: agent`** for role-specific learnings
 
+## Recurring Tasks (Cron System)
+
+Your team has a built-in cron system. The orchestrator or user can schedule recurring tasks that are automatically sent to you on a schedule (e.g., daily reports, weekly checks). When a cron task fires:
+
+- You will receive the task description as a normal message in your terminal
+- Treat it like any other task from the orchestrator — execute it and report results
+- If you were offline, Crewly auto-started you to deliver the task
+
+You do not need to manage cron tasks yourself — the orchestrator handles creation and scheduling. If you need a recurring task set up, ask the orchestrator.
 After checking in, just say "Ready for tasks" and wait for me to send you work.
 
 ## Error Learning Protocol

package/config/roles/backend-developer/prompt.md

@@ -113,6 +113,15 @@ You have bash skills that let you store and retrieve knowledge that persists acr
   bash {{AGENT_SKILLS_PATH}}/core/record-learning/execute.sh '{"agentId":"{{SESSION_NAME}}","agentRole":"{{ROLE}}","projectPath":"{{PROJECT_PATH}}","learning":"Current progress: [what was done]. Remaining: [what is left]. Key findings: [important notes]"}'
   ```
 
+## Recurring Tasks (Cron System)
+
+Your team has a built-in cron system. The orchestrator or user can schedule recurring tasks that are automatically sent to you on a schedule (e.g., daily reports, weekly checks). When a cron task fires:
+
+- You will receive the task description as a normal message in your terminal
+- Treat it like any other task from the orchestrator — execute it and report results
+- If you were offline, Crewly auto-started you to deliver the task
+
+You do not need to manage cron tasks yourself — the orchestrator handles creation and scheduling. If you need a recurring task set up, ask the orchestrator.
 After checking in, just say "Ready for tasks" and wait for me to send you work.
 
 ## Error Learning Protocol

package/config/roles/content-strategist/prompt.md

@@ -71,3 +71,13 @@ When you encounter an error and successfully resolve it:
 1. Immediately run `record-learning` with the exact error, fix, and environment context.
 2. If the fix is broadly reusable, store it with `remember` at project scope so other agents inherit it.
 3. Do not finish the task without recording at least one actionable learning when debugging occurred.
+
+## Recurring Tasks (Cron System)
+
+Your team has a built-in cron system. The orchestrator or user can schedule recurring tasks that are automatically sent to you on a schedule (e.g., daily reports, weekly checks). When a cron task fires:
+
+- You will receive the task description as a normal message in your terminal
+- Treat it like any other task from the orchestrator — execute it and report results
+- If you were offline, Crewly auto-started you to deliver the task
+
+You do not need to manage cron tasks yourself — the orchestrator handles creation and scheduling. If you need a recurring task set up, ask the orchestrator.

package/config/roles/designer/prompt.md

@@ -95,6 +95,15 @@ You have bash skills that let you store and retrieve knowledge that persists acr
 4. **Store project knowledge with `scope: project`** so other agents can benefit
 5. **Store personal knowledge with `scope: agent`** for role-specific learnings
 
+## Recurring Tasks (Cron System)
+
+Your team has a built-in cron system. The orchestrator or user can schedule recurring tasks that are automatically sent to you on a schedule (e.g., daily reports, weekly checks). When a cron task fires:
+
+- You will receive the task description as a normal message in your terminal
+- Treat it like any other task from the orchestrator — execute it and report results
+- If you were offline, Crewly auto-started you to deliver the task
+
+You do not need to manage cron tasks yourself — the orchestrator handles creation and scheduling. If you need a recurring task set up, ask the orchestrator.
 After checking in, just say "Ready for tasks" and wait for me to send you work.
 
 ## Error Learning Protocol

package/config/roles/developer/prompt.md

@@ -124,6 +124,15 @@ You have bash skills that let you store and retrieve knowledge that persists acr
   bash {{AGENT_SKILLS_PATH}}/core/record-learning/execute.sh '{"agentId":"{{SESSION_NAME}}","agentRole":"{{ROLE}}","projectPath":"{{PROJECT_PATH}}","learning":"Current progress: [what was done]. Remaining: [what is left]. Key findings: [important notes]"}'
   ```
 
+## Recurring Tasks (Cron System)
+
+Your team has a built-in cron system. The orchestrator or user can schedule recurring tasks that are automatically sent to you on a schedule (e.g., daily reports, weekly checks). When a cron task fires:
+
+- You will receive the task description as a normal message in your terminal
+- Treat it like any other task from the orchestrator — execute it and report results
+- If you were offline, Crewly auto-started you to deliver the task
+
+You do not need to manage cron tasks yourself — the orchestrator handles creation and scheduling. If you need a recurring task set up, ask the orchestrator.
 After checking in, just say "Ready for tasks" and wait for me to send you work.
 
 ## Error Learning Protocol

package/config/roles/frontend-developer/prompt.md

@@ -113,6 +113,15 @@ You have bash skills that let you store and retrieve knowledge that persists acr
   bash {{AGENT_SKILLS_PATH}}/core/record-learning/execute.sh '{"agentId":"{{SESSION_NAME}}","agentRole":"{{ROLE}}","projectPath":"{{PROJECT_PATH}}","learning":"Current progress: [what was done]. Remaining: [what is left]. Key findings: [important notes]"}'
   ```
 
+## Recurring Tasks (Cron System)
+
+Your team has a built-in cron system. The orchestrator or user can schedule recurring tasks that are automatically sent to you on a schedule (e.g., daily reports, weekly checks). When a cron task fires:
+
+- You will receive the task description as a normal message in your terminal
+- Treat it like any other task from the orchestrator — execute it and report results
+- If you were offline, Crewly auto-started you to deliver the task
+
+You do not need to manage cron tasks yourself — the orchestrator handles creation and scheduling. If you need a recurring task set up, ask the orchestrator.
 After checking in, just say "Ready for tasks" and wait for me to send you work.
 
 ## Error Learning Protocol

package/config/roles/fullstack-dev/prompt.md

@@ -113,6 +113,15 @@ You have bash skills that let you store and retrieve knowledge that persists acr
   bash {{AGENT_SKILLS_PATH}}/core/record-learning/execute.sh '{"agentId":"{{SESSION_NAME}}","agentRole":"{{ROLE}}","projectPath":"{{PROJECT_PATH}}","learning":"Current progress: [what was done]. Remaining: [what is left]. Key findings: [important notes]"}'
   ```
 
+## Recurring Tasks (Cron System)
+
+Your team has a built-in cron system. The orchestrator or user can schedule recurring tasks that are automatically sent to you on a schedule (e.g., daily reports, weekly checks). When a cron task fires:
+
+- You will receive the task description as a normal message in your terminal
+- Treat it like any other task from the orchestrator — execute it and report results
+- If you were offline, Crewly auto-started you to deliver the task
+
+You do not need to manage cron tasks yourself — the orchestrator handles creation and scheduling. If you need a recurring task set up, ask the orchestrator.
 After checking in, just say "Ready for tasks" and wait for me to send you work.
 
 ## Error Learning Protocol

package/config/roles/generalist/prompt.md

@@ -103,4 +103,13 @@ You have bash skills that let you store and retrieve knowledge that persists acr
 5. **Store personal knowledge with `scope: agent`** for role-specific learnings
 6. **Store cross-agent user preferences with `scope: project` + `category: user_preference`**
 
+## Recurring Tasks (Cron System)
+
+Your team has a built-in cron system. The orchestrator or user can schedule recurring tasks that are automatically sent to you on a schedule (e.g., daily reports, weekly checks). When a cron task fires:
+
+- You will receive the task description as a normal message in your terminal
+- Treat it like any other task from the orchestrator — execute it and report results
+- If you were offline, Crewly auto-started you to deliver the task
+
+You do not need to manage cron tasks yourself — the orchestrator handles creation and scheduling. If you need a recurring task set up, ask the orchestrator.
 After checking in, just say "Ready for tasks" and wait for me to send you work.

package/config/roles/ops/prompt.md

@@ -127,6 +127,15 @@ You have bash skills that let you store and retrieve knowledge that persists acr
   bash {{AGENT_SKILLS_PATH}}/core/record-learning/execute.sh '{"agentId":"{{SESSION_NAME}}","agentRole":"{{ROLE}}","projectPath":"{{PROJECT_PATH}}","learning":"Current progress: [what was done]. Remaining: [what is left]. Key findings: [important notes]"}'
   ```
 
+## Recurring Tasks (Cron System)
+
+Your team has a built-in cron system. The orchestrator or user can schedule recurring tasks that are automatically sent to you on a schedule (e.g., daily reports, weekly checks). When a cron task fires:
+
+- You will receive the task description as a normal message in your terminal
+- Treat it like any other task from the orchestrator — execute it and report results
+- If you were offline, Crewly auto-started you to deliver the task
+
+You do not need to manage cron tasks yourself — the orchestrator handles creation and scheduling. If you need a recurring task set up, ask the orchestrator.
 After checking in, just say "Ready for tasks" and wait for me to send you work.
 
 ## Error Learning Protocol

package/config/roles/product-manager/prompt.md

@@ -100,6 +100,15 @@ You have bash skills that let you store and retrieve knowledge that persists acr
 
 ## Startup Protocol (#143)
 
+## Recurring Tasks (Cron System)
+
+Your team has a built-in cron system. The orchestrator or user can schedule recurring tasks that are automatically sent to you on a schedule (e.g., daily reports, weekly checks). When a cron task fires:
+
+- You will receive the task description as a normal message in your terminal
+- Treat it like any other task from the orchestrator — execute it and report results
+- If you were offline, Crewly auto-started you to deliver the task
+
+You do not need to manage cron tasks yourself — the orchestrator handles creation and scheduling. If you need a recurring task set up, ask the orchestrator.
 After checking in, **before** saying "Ready for tasks", perform these startup steps:
 
 1. **Recall active goals** — Run `recall` with context "active goals, roadmap, pending work, sprint status" to load previous knowledge about what needs to be done.

package/config/roles/qa/prompt.md

@@ -113,6 +113,15 @@ You have bash skills that let you store and retrieve knowledge that persists acr
   bash {{AGENT_SKILLS_PATH}}/core/record-learning/execute.sh '{"agentId":"{{SESSION_NAME}}","agentRole":"{{ROLE}}","projectPath":"{{PROJECT_PATH}}","learning":"Current progress: [what was done]. Remaining: [what is left]. Key findings: [important notes]"}'
   ```
 
+## Recurring Tasks (Cron System)
+
+Your team has a built-in cron system. The orchestrator or user can schedule recurring tasks that are automatically sent to you on a schedule (e.g., daily reports, weekly checks). When a cron task fires:
+
+- You will receive the task description as a normal message in your terminal
+- Treat it like any other task from the orchestrator — execute it and report results
+- If you were offline, Crewly auto-started you to deliver the task
+
+You do not need to manage cron tasks yourself — the orchestrator handles creation and scheduling. If you need a recurring task set up, ask the orchestrator.
 After checking in, just say "Ready for tasks" and wait for me to send you work.
 
 ## Error Learning Protocol

package/config/roles/qa-engineer/prompt.md

@@ -113,6 +113,15 @@ You have bash skills that let you store and retrieve knowledge that persists acr
   bash {{AGENT_SKILLS_PATH}}/core/record-learning/execute.sh '{"agentId":"{{SESSION_NAME}}","agentRole":"{{ROLE}}","projectPath":"{{PROJECT_PATH}}","learning":"Current progress: [what was done]. Remaining: [what is left]. Key findings: [important notes]"}'
   ```
 
+## Recurring Tasks (Cron System)
+
+Your team has a built-in cron system. The orchestrator or user can schedule recurring tasks that are automatically sent to you on a schedule (e.g., daily reports, weekly checks). When a cron task fires:
+
+- You will receive the task description as a normal message in your terminal
+- Treat it like any other task from the orchestrator — execute it and report results
+- If you were offline, Crewly auto-started you to deliver the task
+
+You do not need to manage cron tasks yourself — the orchestrator handles creation and scheduling. If you need a recurring task set up, ask the orchestrator.
 After checking in, just say "Ready for tasks" and wait for me to send you work.
 
 ## Error Learning Protocol

package/config/roles/researcher/prompt.md

@@ -96,6 +96,15 @@ You have bash skills that let you store and retrieve knowledge that persists acr
 4. **Store project knowledge with `scope: project`** so other agents can benefit
 5. **Store personal knowledge with `scope: agent`** for role-specific learnings
 
+## Recurring Tasks (Cron System)
+
+Your team has a built-in cron system. The orchestrator or user can schedule recurring tasks that are automatically sent to you on a schedule (e.g., daily reports, weekly checks). When a cron task fires:
+
+- You will receive the task description as a normal message in your terminal
+- Treat it like any other task from the orchestrator — execute it and report results
+- If you were offline, Crewly auto-started you to deliver the task
+
+You do not need to manage cron tasks yourself — the orchestrator handles creation and scheduling. If you need a recurring task set up, ask the orchestrator.
 After checking in, just say "Ready for tasks" and wait for me to send you work.
 
 ## Error Learning Protocol

package/config/roles/sales/prompt.md

@@ -95,6 +95,15 @@ You have bash skills that let you store and retrieve knowledge that persists acr
 4. **Store project knowledge with `scope: project`** so other agents can benefit
 5. **Store personal knowledge with `scope: agent`** for role-specific learnings
 
+## Recurring Tasks (Cron System)
+
+Your team has a built-in cron system. The orchestrator or user can schedule recurring tasks that are automatically sent to you on a schedule (e.g., daily reports, weekly checks). When a cron task fires:
+
+- You will receive the task description as a normal message in your terminal
+- Treat it like any other task from the orchestrator — execute it and report results
+- If you were offline, Crewly auto-started you to deliver the task
+
+You do not need to manage cron tasks yourself — the orchestrator handles creation and scheduling. If you need a recurring task set up, ask the orchestrator.
 After checking in, just say "Ready for tasks" and wait for me to send you work.
 
 ## Error Learning Protocol

package/config/roles/support/prompt.md

@@ -95,6 +95,15 @@ You have bash skills that let you store and retrieve knowledge that persists acr
 4. **Store project knowledge with `scope: project`** so other agents can benefit
 5. **Store personal knowledge with `scope: agent`** for role-specific learnings
 
+## Recurring Tasks (Cron System)
+
+Your team has a built-in cron system. The orchestrator or user can schedule recurring tasks that are automatically sent to you on a schedule (e.g., daily reports, weekly checks). When a cron task fires:
+
+- You will receive the task description as a normal message in your terminal
+- Treat it like any other task from the orchestrator — execute it and report results
+- If you were offline, Crewly auto-started you to deliver the task
+
+You do not need to manage cron tasks yourself — the orchestrator handles creation and scheduling. If you need a recurring task set up, ask the orchestrator.
 After checking in, just say "Ready for tasks" and wait for me to send you work.
 
 ## Error Learning Protocol

package/config/roles/team-leader/prompt.md

@@ -18,6 +18,8 @@ You are a **Team Leader** (hierarchyLevel=1) responsible for managing a sub-team
 
 **Core identity**: You are a manager, not an individual contributor. Your first reaction should be "Who is best suited for this?" — not "How do I write this code/content myself?" Delegate 90% of execution tasks to your workers. Only handle complex coordination yourself.
 
+**Worker activation**: Before delegating a task, check worker status via `get-team-status`. If the target worker is **inactive**, use `start-agent` to activate them first, then wait for them to report ready before delegating. Never skip delegation just because workers are offline — wake them up.
+
 **Hierarchy position**: You report directly to the Orchestrator and manage all workers whose `parentMemberId` points to you.
 
 ## Your Workers
@@ -185,4 +187,13 @@ Please run the register-self skill to let the team dashboard know you're availab
 bash {{AGENT_SKILLS_PATH}}/core/register-self/execute.sh '{"role":"{{ROLE}}","sessionName":"{{SESSION_NAME}}"}'
 ```
 
+## Recurring Tasks (Cron System)
+
+Your team has a built-in cron system. The orchestrator or user can schedule recurring tasks that are automatically sent to you on a schedule (e.g., daily reports, weekly checks). When a cron task fires:
+
+- You will receive the task description as a normal message in your terminal
+- Treat it like any other task from the orchestrator — execute it and report results
+- If you were offline, Crewly auto-started you to deliver the task
+
+You do not need to manage cron tasks yourself — the orchestrator handles creation and scheduling. If you need a recurring task set up, ask the orchestrator.
 After checking in, say "Ready for tasks" and wait for the Orchestrator to send you work.

package/config/roles/tpm/prompt.md

@@ -96,6 +96,15 @@ You have bash skills that let you store and retrieve knowledge that persists acr
 4. **Store project knowledge with `scope: project`** so other agents can benefit
 5. **Store personal knowledge with `scope: agent`** for role-specific learnings
 
+## Recurring Tasks (Cron System)
+
+Your team has a built-in cron system. The orchestrator or user can schedule recurring tasks that are automatically sent to you on a schedule (e.g., daily reports, weekly checks). When a cron task fires:
+
+- You will receive the task description as a normal message in your terminal
+- Treat it like any other task from the orchestrator — execute it and report results
+- If you were offline, Crewly auto-started you to deliver the task
+
+You do not need to manage cron tasks yourself — the orchestrator handles creation and scheduling. If you need a recurring task set up, ask the orchestrator.
 After checking in, just say "Ready for tasks" and wait for me to send you work.
 
 ## Error Learning Protocol

package/config/roles/ux-designer/prompt.md

@@ -97,6 +97,15 @@ You have bash skills that let you store and retrieve knowledge that persists acr
 4. **Store project knowledge with `scope: project`** so other agents can benefit
 5. **Store personal knowledge with `scope: agent`** for role-specific learnings
 
+## Recurring Tasks (Cron System)
+
+Your team has a built-in cron system. The orchestrator or user can schedule recurring tasks that are automatically sent to you on a schedule (e.g., daily reports, weekly checks). When a cron task fires:
+
+- You will receive the task description as a normal message in your terminal
+- Treat it like any other task from the orchestrator — execute it and report results
+- If you were offline, Crewly auto-started you to deliver the task
+
+You do not need to manage cron tasks yourself — the orchestrator handles creation and scheduling. If you need a recurring task set up, ask the orchestrator.
 After checking in, just say "Ready for tasks" and wait for me to send you work.
 
 ## Error Learning Protocol

package/config/skills/_common/lib.sh

@@ -7,6 +7,37 @@
 # Base URL for the Crewly backend API
 CREWLY_API_URL="${CREWLY_API_URL:-http://localhost:8787}"
 
+# -----------------------------------------------------------------------------
+# Universal --file flag preprocessor (#EOF-fix)
+#
+# Fixes Gemini CLI's "unexpected EOF while looking for matching `'" errors.
+#
+# Root cause: When an LLM CLI passes JSON as a shell argument, special chars
+# inside the JSON (single quotes, backticks, parentheses, $variables) get
+# interpreted by the shell BEFORE the script runs, causing parse errors.
+#
+# Solution: The LLM writes JSON to a temp file, then passes --file <path>.
+# This preprocessor detects --file as the first argument, reads the file,
+# and replaces the script's positional parameters with the file contents.
+# All downstream parsing (read_json_input, custom arg loops) works unchanged.
+#
+# Usage (by LLM CLI):
+#   printf '%s' '{"summary":"text with 'quotes'"}' > /tmp/crewly_input.json
+#   bash execute.sh --file /tmp/crewly_input.json
+#
+# This runs at source-time, so every script that sources lib.sh gets it for free.
+# -----------------------------------------------------------------------------
+if [ "${1:-}" = "--file" ] && [ -n "${2:-}" ]; then
+  if [ -f "$2" ]; then
+    _CREWLY_FILE_CONTENT="$(cat "$2")"
+    set -- "$_CREWLY_FILE_CONTENT"
+    unset _CREWLY_FILE_CONTENT
+  else
+    echo '{"error":"File not found: '"$2"'"}' >&2
+    exit 1
+  fi
+fi
+
 # -----------------------------------------------------------------------------
 # read_json_input [arg]
 #

package/config/skills/_common/lib.test.sh

@@ -0,0 +1,164 @@
+#!/bin/bash
+# =============================================================================
+# Tests for lib.sh — shared skills library
+# Covers: --file preprocessor, read_json_input, require_param, error_exit
+# =============================================================================
+set -euo pipefail
+
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+PASS=0
+FAIL=0
+TOTAL=0
+
+# Color output
+RED='\033[0;31m'
+GREEN='\033[0;32m'
+NC='\033[0m' # No Color
+
+assert_eq() {
+  local test_name="$1" expected="$2" actual="$3"
+  TOTAL=$((TOTAL + 1))
+  if [ "$expected" = "$actual" ]; then
+    echo -e "${GREEN}PASS${NC}: $test_name"
+    PASS=$((PASS + 1))
+  else
+    echo -e "${RED}FAIL${NC}: $test_name"
+    echo "  Expected: $expected"
+    echo "  Actual:   $actual"
+    FAIL=$((FAIL + 1))
+  fi
+}
+
+assert_contains() {
+  local test_name="$1" expected_substr="$2" actual="$3"
+  TOTAL=$((TOTAL + 1))
+  if echo "$actual" | grep -q "$expected_substr"; then
+    echo -e "${GREEN}PASS${NC}: $test_name"
+    PASS=$((PASS + 1))
+  else
+    echo -e "${RED}FAIL${NC}: $test_name"
+    echo "  Expected to contain: $expected_substr"
+    echo "  Actual: $actual"
+    FAIL=$((FAIL + 1))
+  fi
+}
+
+assert_exit_code() {
+  local test_name="$1" expected_code="$2"
+  shift 2
+  local actual_code=0
+  "$@" >/dev/null 2>&1 || actual_code=$?
+  TOTAL=$((TOTAL + 1))
+  if [ "$expected_code" = "$actual_code" ]; then
+    echo -e "${GREEN}PASS${NC}: $test_name"
+    PASS=$((PASS + 1))
+  else
+    echo -e "${RED}FAIL${NC}: $test_name"
+    echo "  Expected exit code: $expected_code"
+    echo "  Actual exit code:   $actual_code"
+    FAIL=$((FAIL + 1))
+  fi
+}
+
+# Create a minimal test skill script that sources lib.sh and echoes $1
+TEMP_DIR=$(mktemp -d)
+trap "rm -rf $TEMP_DIR" EXIT
+
+cat > "$TEMP_DIR/test_skill.sh" << 'SKILL_EOF'
+#!/bin/bash
+set -euo pipefail
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+# Source lib.sh via the real path
+source "$LIB_PATH"
+# Output the first positional parameter (after preprocessor runs)
+echo "$1"
+SKILL_EOF
+chmod +x "$TEMP_DIR/test_skill.sh"
+
+# Also create a test skill that uses read_json_input
+cat > "$TEMP_DIR/test_read_json.sh" << 'SKILL_EOF'
+#!/bin/bash
+set -euo pipefail
+source "$LIB_PATH"
+INPUT=$(read_json_input "${1:-}")
+echo "$INPUT"
+SKILL_EOF
+chmod +x "$TEMP_DIR/test_read_json.sh"
+
+export LIB_PATH="$SCRIPT_DIR/lib.sh"
+
+echo "=== lib.sh Test Suite ==="
+echo ""
+
+# ---- Test 1: --file flag reads JSON from file ----
+echo '{"key":"value","text":"hello world"}' > "$TEMP_DIR/input.json"
+RESULT=$(bash "$TEMP_DIR/test_skill.sh" --file "$TEMP_DIR/input.json")
+assert_eq "--file reads JSON from file" '{"key":"value","text":"hello world"}' "$RESULT"
+
+# ---- Test 2: --file with special characters (the whole point!) ----
+printf '%s' '{"summary":"text with '\''quotes'\'' and (parens) and `backticks`"}' > "$TEMP_DIR/special.json"
+RESULT=$(bash "$TEMP_DIR/test_skill.sh" --file "$TEMP_DIR/special.json")
+assert_contains "--file handles single quotes" "quotes" "$RESULT"
+assert_contains "--file handles parentheses" "(parens)" "$RESULT"
+assert_contains "--file handles backticks" "backticks" "$RESULT"
+
+# ---- Test 3: --file with multiline JSON ----
+cat > "$TEMP_DIR/multiline.json" << 'MULTI_EOF'
+{"summary":"line 1\nline 2\nline 3","status":"done"}
+MULTI_EOF
+RESULT=$(bash "$TEMP_DIR/test_skill.sh" --file "$TEMP_DIR/multiline.json")
+assert_contains "--file handles multiline content" "line 1" "$RESULT"
+
+# ---- Test 4: --file with nonexistent file fails ----
+RESULT=$(bash "$TEMP_DIR/test_skill.sh" --file "/tmp/nonexistent_crewly_test_file.json" 2>&1 || true)
+assert_contains "--file with missing file reports error" "File not found" "$RESULT"
+
+# ---- Test 5: Direct JSON argument still works (backward compat) ----
+RESULT=$(bash "$TEMP_DIR/test_skill.sh" '{"key":"direct"}')
+assert_eq "Direct JSON argument works" '{"key":"direct"}' "$RESULT"
+
+# ---- Test 6: read_json_input with --file ----
+echo '{"agentId":"dev-1","content":"test memory"}' > "$TEMP_DIR/read_input.json"
+RESULT=$(bash "$TEMP_DIR/test_read_json.sh" --file "$TEMP_DIR/read_input.json")
+assert_contains "read_json_input with --file" "dev-1" "$RESULT"
+
+# ---- Test 7: read_json_input with @filepath ----
+echo '{"agentId":"dev-2","content":"at-file test"}' > "$TEMP_DIR/at_input.json"
+RESULT=$(bash "$TEMP_DIR/test_read_json.sh" "@$TEMP_DIR/at_input.json")
+assert_contains "read_json_input with @filepath" "dev-2" "$RESULT"
+
+# ---- Test 8: read_json_input with stdin pipe ----
+RESULT=$(echo '{"agentId":"dev-3","content":"stdin test"}' | bash "$TEMP_DIR/test_read_json.sh")
+assert_contains "read_json_input with stdin pipe" "dev-3" "$RESULT"
+
+# ---- Test 9: read_json_input with direct JSON arg ----
+RESULT=$(bash "$TEMP_DIR/test_read_json.sh" '{"agentId":"dev-4"}')
+assert_contains "read_json_input with direct arg" "dev-4" "$RESULT"
+
+# ---- Test 10: --file with Unicode content ----
+printf '%s' '{"text":"Chinese: 你好世界, Japanese: こんにちは"}' > "$TEMP_DIR/unicode.json"
+RESULT=$(bash "$TEMP_DIR/test_skill.sh" --file "$TEMP_DIR/unicode.json")
+assert_contains "--file handles Unicode" "你好世界" "$RESULT"
+
+# ---- Test 11: --file with dollar signs and variables ----
+printf '%s' '{"text":"Price is $100, env is ${HOME}"}' > "$TEMP_DIR/dollar.json"
+RESULT=$(bash "$TEMP_DIR/test_skill.sh" --file "$TEMP_DIR/dollar.json")
+assert_contains "--file preserves dollar signs" '$100' "$RESULT"
+assert_contains "--file preserves \\\${} syntax" '${HOME}' "$RESULT"
+
+# ---- Test 12: --file with newlines in JSON values ----
+printf '%s' '{"text":"line1\nline2\nline3"}' > "$TEMP_DIR/newlines.json"
+RESULT=$(bash "$TEMP_DIR/test_skill.sh" --file "$TEMP_DIR/newlines.json")
+assert_contains "--file preserves escaped newlines" 'line1\\nline2' "$RESULT"
+
+# ---- Test 13: --file with empty JSON ----
+echo '{}' > "$TEMP_DIR/empty.json"
+RESULT=$(bash "$TEMP_DIR/test_read_json.sh" --file "$TEMP_DIR/empty.json")
+assert_eq "--file with empty JSON" '{}' "$RESULT"
+
+echo ""
+echo "=== Results: $PASS/$TOTAL passed, $FAIL failed ==="
+
+if [ "$FAIL" -gt 0 ]; then
+  exit 1
+fi

package/config/skills/agent/core/block-task/execute.sh

@@ -16,10 +16,12 @@ require_param "reason" "$REASON"
 
 BODY=$(jq -n \
   --arg absoluteTaskPath "$ABSOLUTE_TASK_PATH" \
+  --arg taskPath "$ABSOLUTE_TASK_PATH" \
   --arg reason "$REASON" \
+  --arg blockReason "$REASON" \
   --arg questions "$QUESTIONS" \
   --arg urgency "$URGENCY" \
-  '{absoluteTaskPath: $absoluteTaskPath, reason: $reason} +
+  '{absoluteTaskPath: $absoluteTaskPath, taskPath: $taskPath, reason: $reason, blockReason: $blockReason} +
    (if $questions != "" then {questions: $questions} else {} end) +
    (if $urgency != "" then {urgency: $urgency} else {} end)')