From 0547ca197031933ad4a8800f3adf7a019c0d97e5 Mon Sep 17 00:00:00 2001
From: jarek <jkrochmalski@gmail.com>
Date: Mon, 17 Aug 2026 09:50:35 +0200
Subject: [PATCH] adopting a stack over the API rejects a compose path not on
 Dockhand's filesystem

---
 src/lib/server/stack-scanner.ts | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/src/lib/server/stack-scanner.ts b/src/lib/server/stack-scanner.ts
index d4c4c38..4e78e88 100644
--- a/src/lib/server/stack-scanner.ts
+++ b/src/lib/server/stack-scanner.ts
@@ -228,6 +228,17 @@ export async function adoptStack(
 		return { success: false, error: 'Already adopted' };
 	}
 
+	// The compose file must live on Dockhand's own filesystem - it is the source of truth
+	// Dockhand reads on view/edit and pushes to the remote on deploy. The GUI file browser
+	// can only pick a local path, but a direct API call can pass any string, including a
+	// remote agent's STACKS_DIR path that Dockhand can't read (#1375). Reject it here.
+	if (stack.composePath && !existsSync(stack.composePath)) {
+		return {
+			success: false,
+			error: `Compose file not found on Dockhand's filesystem: ${stack.composePath}. Adopt a path local to Dockhand, not a remote agent path.`
+		};
+	}
+
 	// If the compose file has a top-level `name:` property, prefer it over the passed name.
 	// This ensures Docker's project name (from the label) matches Dockhand's stack name.
 	let stackNameSource = stack.name;