diff --git a/.agent/workflows/deploy_to_production.md b/.agent/workflows/deploy_to_production.md
index b7c38d6..b415ade 100644
--- a/.agent/workflows/deploy_to_production.md
+++ b/.agent/workflows/deploy_to_production.md
@@ -33,10 +33,13 @@
 Sync the latest `agent-node` code to the production folder. We use `scp` as `rsync` is typically not available on Windows.
 
 ```bash
-# Sync source code and protos
-scp -r agent-node/src/ axiey@192.168.68.7:C:/CortexAgent/src/
+# Sync agent-node source AND mesh-sdk (both must be synced together)
+sshpass -p 'Y@ngy@ngX1e2019' scp -o StrictHostKeyChecking=no -r agent-node/src/ axiey@192.168.68.7:C:/CortexAgent/src/
+sshpass -p 'Y@ngy@ngX1e2019' scp -o StrictHostKeyChecking=no -r mesh-sdk/mesh_core/ axiey@192.168.68.7:C:/CortexAgent/src/mesh_core/
 ```
 
+> **Important**: `mesh_core` is a separate package from `agent_node`. Always sync both together — syncing only `agent-node/src/` leaves the old `mesh_core` on disk and will silently run stale SDK code.
+
 ### 2. Restarting the Agent
 The agent runs as a Scheduled Task named `CortexAgent`. To activate changes, you MUST restart the task. **Use PowerShell** for reliable command chaining over SSH.