From 6f7544c8b3b47f03861dc42f72a865c807be2472 Mon Sep 17 00:00:00 2001
From: Hikari <hikari@nhcarrigan.com>
Date: Sun, 8 Feb 2026 12:50:18 -0800
Subject: [PATCH] fix: use backend command to read memory files for WSL
 compatibility
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

The frontend was using Tauri's `readTextFile` plugin which enforces
scope restrictions and doesn't work with WSL paths on Windows.

Changed to use our `read_file_content` backend command which:
- Already handles WSL paths correctly on Windows
- Works with absolute paths on all platforms
- Bypasses Tauri's filesystem scope restrictions
- Matches the pattern used throughout the app for file operations

This fixes the "forbidden path" error when trying to read memory
files on Windows whilst maintaining functionality on Linux/Mac.

✨ This fix was created by Hikari~ 🌸
---
 src/lib/components/MemoryBrowserPanel.svelte | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/lib/components/MemoryBrowserPanel.svelte b/src/lib/components/MemoryBrowserPanel.svelte
index d500325..aa62a37 100644
--- a/src/lib/components/MemoryBrowserPanel.svelte
+++ b/src/lib/components/MemoryBrowserPanel.svelte
@@ -1,7 +1,6 @@
 <script lang="ts">
   import { onMount } from "svelte";
   import { invoke } from "@tauri-apps/api/core";
-  import { readTextFile } from "@tauri-apps/plugin-fs";
   import Markdown from "./Markdown.svelte";
 
   let memoryFiles: string[] = $state([]);
@@ -33,7 +32,8 @@
     isLoading = true;
     error = null;
     try {
-      const content = await readTextFile(filePath);
+      // Use our backend command instead of Tauri plugin to handle WSL paths
+      const content = await invoke<string>("read_file_content", { path: filePath });
       fileContent = content;
       selectedFile = filePath;
     } catch (e) {