feat: add support for LOCAL_R2 var for local dev

Author: AshishKumar4

definitions/vite-cf-DO-runner/prompts/usage.md

@@ -96,6 +96,7 @@ async addMyData(item: MyType): Promise<MyType[]> {
 
 ## Bindings
 CRITICAL: only `GlobalDurableObject` is available for stateful ops
+**IMPORTANT: You are NOT ALLOWED to edit/add/remove ANY worker bindings OR touch wrangler.jsonc/wrangler.toml. Build your application around what is already provided.**
 
 **YOU CANNOT**:
 - Modify `wrangler.jsonc` 

definitions/vite-cf-DO-v2-runner/prompts/usage.md

@@ -70,6 +70,7 @@ app.post('/api/users', async (c) => {
 
 ## Bindings
 CRITICAL: only `GlobalDurableObject` is available for stateful ops
+**IMPORTANT: You are NOT ALLOWED to edit/add/remove ANY worker bindings OR touch wrangler.jsonc/wrangler.toml. Build your application around what is already provided.**
 
 **YOU CANNOT**:
 - Modify `wrangler.jsonc` 

definitions/vite-cfagents-runner/prompts/selection.md

@@ -8,7 +8,7 @@ This template provides a production-ready AI agent chatbot built with Cloudflare
   * Multi-model AI support (GPT-4o, Gemini 2.0/2.5, Claude Opus 4)
   * Production-ready MCP integration with official TypeScript SDK
   * Real-time conversation management
-  * Real-time streaming chat
+  * Real-time streaming chat with AI Agents
   * Advanced AI Agents capabilities and AI based applications like image generation, chat bots etc
 
 * Do not use it for:
@@ -17,7 +17,7 @@ This template provides a production-ready AI agent chatbot built with Cloudflare
   * Projects requiring complex multi-user chat rooms or real-time streaming
   * Simple question-answer bots without tool requirements
 
-**IMPORTANT NOTE: Only use this template if you NEED AI/LLM capabilities as core of your application**
+**IMPORTANT NOTE: Only use this template if you NEED AI/LLM capabilities as core of your application. If the requirement is for durable objects, there are much better templates like 'vite-cf-DO-runner' or 'vite-cf-DO-v2-runner'**
 
 * Built with:
   * **Cloudflare Agents SDK** for stateful agent management with Durable Objects

definitions/vite-cfagents-runner/prompts/usage.md

@@ -171,8 +171,9 @@ tooltip.tsx
 
 # Available bindings:
 **Only The following bindings are to be used in the project! Do not use any other bindings or remove/replace any of the bindings**
-- `CHAT_AGENT`: A durable object binding for the chat agent
-- `APP_CONTROLLER`: A durable object binding for the app controller
+- `CHAT_AGENT`: A durable object binding for the chat agent, but can be extended and used for other agentic purposes
+- `APP_CONTROLLER`: A durable object binding for the app controller, but can be extended and used for other agentic purposes
+**IMPORTANT: You are NOT ALLOWED to edit/add/remove ANY worker bindings OR touch wrangler.jsonc/wrangler.toml. Build your application around what is already provided.**
 
 # IMPORTANT NOTE: If AI capabilities are required, you must inform the user that although this project has AI capaibilities, there is no way to pass API keys and thus AI inferencing won't work. Users must export the app to their github, then make necessary changes and deploy it themselves to have it work. This is due to security reasons but we are implementing it in a secure way, and this would be available soon.
 Add the above note in an appropriate and visible location in the app - like in the footer or in the chat interface or as a modal

deploy_templates.sh

@@ -95,8 +95,19 @@ echo "⚙️  Verifying Wrangler CLI..."
 wrangler --version
 echo "✅ Wrangler CLI ready"
 
-# Upload files to Cloudflare R2
-echo "🚀 Uploading files to Cloudflare R2..."
+# Determine R2 endpoint based on LOCAL_R2 environment variable
+if [ "${LOCAL_R2:-}" = "true" ]; then
+  echo "🏠 LOCAL_R2=true - using local R2 endpoint"
+  R2_FLAGS="--local"
+  R2_ENDPOINT="local R2"
+else
+  echo "☁️  Using remote Cloudflare R2"
+  R2_FLAGS="--remote"
+  R2_ENDPOINT="Cloudflare R2"
+fi
+
+# Upload files to R2
+echo "🚀 Uploading files to $R2_ENDPOINT..."
 
 # Function to upload a file to R2
 upload_to_r2() {
@@ -105,7 +116,7 @@ upload_to_r2() {
   local description="$3"
 
   echo "Uploading: $description"
-  if wrangler r2 object put "${R2_BUCKET_NAME}/$r2_key" --file="$file_path" --remote; then
+  if wrangler r2 object put "${R2_BUCKET_NAME}/$r2_key" --file="$file_path" $R2_FLAGS; then
     echo "✅ Successfully uploaded $description"
     return 0
   else
@@ -114,31 +125,51 @@ upload_to_r2() {
   fi
 }
 
-# Upload template catalog JSON and all zip files in parallel
-echo "📄📦 Uploading template catalog and zip files in parallel..."
-upload_pids=()
-failed_uploads=()
-
-# Start catalog upload in background
-upload_to_r2 "template_catalog.json" "template_catalog.json" "template_catalog.json" &
-upload_pids+=($!)
-
-# Start zip file uploads in background
-for zip_file in zips/*.zip; do
-  if [ -f "$zip_file" ]; then
-    filename=$(basename "$zip_file")
-    upload_to_r2 "$zip_file" "$filename" "$filename" &
-    upload_pids+=($!)
-  fi
-done
+# Upload template catalog JSON and all zip files
+if [ "${LOCAL_R2:-}" = "true" ]; then
+  echo "📄📦 Uploading template catalog and zip files sequentially (local R2)..."
+  failed_uploads=()
 
-# Wait for all uploads to complete and check for failures
-echo "⏳ Waiting for all uploads to complete..."
-for pid in "${upload_pids[@]}"; do
-  if ! wait "$pid"; then
-    failed_uploads+=("Upload process $pid failed")
+  # Upload catalog first
+  if ! upload_to_r2 "template_catalog.json" "template_catalog.json" "template_catalog.json"; then
+    failed_uploads+=("template_catalog.json upload failed")
   fi
-done
+
+  # Upload zip files sequentially
+  for zip_file in zips/*.zip; do
+    if [ -f "$zip_file" ]; then
+      filename=$(basename "$zip_file")
+      if ! upload_to_r2 "$zip_file" "$filename" "$filename"; then
+        failed_uploads+=("$filename upload failed")
+      fi
+    fi
+  done
+else
+  echo "📄📦 Uploading template catalog and zip files in parallel..."
+  upload_pids=()
+  failed_uploads=()
+
+  # Start catalog upload in background
+  upload_to_r2 "template_catalog.json" "template_catalog.json" "template_catalog.json" &
+  upload_pids+=($!)
+
+  # Start zip file uploads in background
+  for zip_file in zips/*.zip; do
+    if [ -f "$zip_file" ]; then
+      filename=$(basename "$zip_file")
+      upload_to_r2 "$zip_file" "$filename" "$filename" &
+      upload_pids+=($!)
+    fi
+  done
+
+  # Wait for all uploads to complete and check for failures
+  echo "⏳ Waiting for all uploads to complete..."
+  for pid in "${upload_pids[@]}"; do
+    if ! wait "$pid"; then
+      failed_uploads+=("Upload process $pid failed")
+    fi
+  done
+fi
 
 # Check if any uploads failed
 if [ ${#failed_uploads[@]} -gt 0 ]; then
@@ -149,7 +180,7 @@ if [ ${#failed_uploads[@]} -gt 0 ]; then
   exit 1
 fi
 
-echo "🎉 All files uploaded successfully to R2 bucket: ${R2_BUCKET_NAME}"
+echo "🎉 All files uploaded successfully to $R2_ENDPOINT bucket: ${R2_BUCKET_NAME}"
 
 # Skip verification as wrangler doesn't have a list command
 echo "✅ All uploads completed successfully"
@@ -177,8 +208,13 @@ if [ -n "${GITHUB_STEP_SUMMARY:-}" ]; then
 
   echo "" >> $GITHUB_STEP_SUMMARY
   echo "### 🌐 Access URLs" >> $GITHUB_STEP_SUMMARY
-  echo "- **Catalog**: \`https://${R2_BUCKET_NAME}.r2.dev/template_catalog.json\`" >> $GITHUB_STEP_SUMMARY
-  echo "- **Templates**: \`https://${R2_BUCKET_NAME}.r2.dev/[template-name].zip\`" >> $GITHUB_STEP_SUMMARY
+  if [ "${LOCAL_R2:-}" = "true" ]; then
+    echo "- **Target**: Local R2 (${R2_BUCKET_NAME})" >> $GITHUB_STEP_SUMMARY
+    echo "- **Note**: Files uploaded to local R2 development environment" >> $GITHUB_STEP_SUMMARY
+  else
+    echo "- **Catalog**: \`https://${R2_BUCKET_NAME}.r2.dev/template_catalog.json\`" >> $GITHUB_STEP_SUMMARY
+    echo "- **Templates**: \`https://${R2_BUCKET_NAME}.r2.dev/[template-name].zip\`" >> $GITHUB_STEP_SUMMARY
+  fi
   echo "" >> $GITHUB_STEP_SUMMARY
   echo "🕐 **Deployed at**: $(date -u +%Y-%m-%d\ %H:%M:%S\ UTC)" >> $GITHUB_STEP_SUMMARY
 fi