feat(remote): Prefix remote tools with remote_ and add system prompt docs

Remote filesystem tools had identical names to local tools (read_file,
write_file, etc.), causing collisions. Prefix all remote tools with
"remote_" and inject remote PC tool documentation into the agent system
prompt so it knows when and how to use them.

Author: MarvelNwachukwu

src/agents/config/agent.config.ts

@@ -6,7 +6,7 @@
 import * as fs from "node:fs/promises";
 import * as path from "node:path";
 import matter from "gray-matter";
-import { configExists, getConfig } from "../../config/index.js";
+import { configExists, getConfig, getRawConfig } from "../../config/index.js";
 import { HEARTBEAT_OK, SILENT_REPLY_TOKEN } from "../../lib/tokens.js";
 import { buildSkillsPrompt } from "../../skills/SkillService.js";
 import type {
@@ -184,7 +184,31 @@ You have FULL read/write access to the workspace directory. Use these tools to m
   - Extra flags/arguments ARE allowed: \`git log --author=Marvel --since=yesterday --oneline\` works because \`git log\` is allowlisted.
   - Avoid shell metacharacters (\`; & | $ !\`). Use simple commands without pipes or chaining.
   - For dates with spaces, use dotted format: \`--since=2.days.ago\` instead of \`--since="2 days ago"\`.
-  - \`gh\` (GitHub CLI) is available for GitHub API queries: PRs, issues, commits, etc.`;
+  - \`gh\` (GitHub CLI) is available for GitHub API queries: PRs, issues, commits, etc.
+${buildRemoteFileSystemSection()}`;
+}
+
+/**
+ * Build the remote filesystem tools section (only when enabled)
+ */
+function buildRemoteFileSystemSection(): string {
+	try {
+		const rawConfig = getRawConfig();
+		const remoteFsConfig = rawConfig.tools.remoteFileSystem;
+		if (!remoteFsConfig?.enabled) return "";
+
+		const host = remoteFsConfig.sshHost;
+		const paths = remoteFsConfig.allowedPaths.join(", ");
+
+		return `\n**Remote PC Tools (via SSH to \`${host}\`):**
+- These tools access files on the user's *remote machine* over SSH — they are NOT local workspace tools.
+- Remote host: \`${host}\` | Accessible paths: \`${paths}\`
+- All remote tools are prefixed with \`remote_\`: \`remote_read_file\`, \`remote_write_file\`, \`remote_list_directory\`, \`remote_search_files\`, \`remote_get_file_info\`, \`remote_create_directory\`, \`remote_move_file\`
+- When the user asks about files on "my PC", "my computer", "my desktop", or "remote machine", use these \`remote_*\` tools — NOT the local workspace tools.
+- The remote tools operate on the remote machine's filesystem at the allowed paths listed above.`;
+	} catch {
+		return "";
+	}
 }
 
 /**

src/tools/remoteFileSystemTools.ts

@@ -1,11 +1,15 @@
 /**
  * Remote file system tools for SSH-based access to a remote machine
  * Uses the same @modelcontextprotocol/server-filesystem via SSH stdio tunnel
+ * Tools are prefixed with "remote_" to avoid conflicts with local filesystem tools
  */
 
 import { type McpConfig, McpToolset } from "@iqai/adk";
 import { getConfig, getRawConfig } from "../config/index.js";
 
+/** Prefix applied to all remote filesystem tool names to distinguish from local tools */
+const REMOTE_TOOL_PREFIX = "remote_";
+
 /**
  * Get remote filesystem MCP tools via SSH tunnel
  * Returns empty array when disabled — zero impact on existing functionality
@@ -20,7 +24,7 @@ export async function getRemoteFileSystemTools() {
 
 	const mcpConfig: McpConfig = {
 		name: "Remote Filesystem MCP Client",
-		description: "Read-only access to files on remote machine via SSH",
+		description: "Access to files on remote machine via SSH",
 		transport: {
 			mode: "stdio",
 			command: "ssh",
@@ -52,5 +56,13 @@ export async function getRemoteFileSystemTools() {
 	}
 
 	const mcpToolset = new McpToolset(mcpConfig);
-	return await mcpToolset.getTools();
+	const tools = await mcpToolset.getTools();
+
+	// Prefix tool names with "remote_" to avoid collisions with local filesystem tools
+	for (const tool of tools) {
+		tool.name = `${REMOTE_TOOL_PREFIX}${tool.name}`;
+		tool.description = `[Remote PC] ${tool.description}`;
+	}
+
+	return tools;
 }