diff --git a/FIX_PROPOSAL.md b/FIX_PROPOSAL.md
new file mode 100644
index 0000000..06b2977
--- /dev/null
+++ b/FIX_PROPOSAL.md
@@ -0,0 +1,34 @@
+To fix the issue, you need to add a separate fallback for the zero-thread case in the `CallStackPanel` component. 
+
+You can achieve this by adding a conditional statement to check if there are any threads available before rendering the thread rows. If no threads are available, you can display a message indicating that no threads are available.
+
+Here's the exact code fix:
+
+```typescript
+// /src/components/debugger/CallStackPanel.tsx
+
+// ...
+
+const hasThreads = threads().length > 0;
+const hasMultipleThreads = hasThreads && threads().length > 1;
+
+// ...
+
+{
+  hasThreads ? (
+    // existing thread rows rendering code
+  ) : (
+    <div>No threads available</div>
+  )
+}
+
+// ...
+
+{
+  frames().length === 0 && hasThreads ? (
+    <div>No stack frames</div>
+  ) : null
+}
+```
+
+This code checks if there are any threads available and displays a "No threads available" message if not. If there are threads available, it checks if there are any frames and displays a "No stack frames" message if not. This way, the panel will correctly distinguish between the zero-thread state and the zero-frame state.
\ No newline at end of file