How over-coder/stash works
High-Level Architecture Overview
a) Frontend Layer (Next.js)
• Components from /app directory
• Components like SessionCard, ActionRing, and NavbarSearch
b) Middleware Layer (Tauri/Rust)
• In the middle
• Src-tauri/main.rs as the bridge
• Command handling and IPC
c) Backend Layer (Python)
• At the bottom
• Main.py and scripts (dumpconfig.py, getwindows.py, restorewin.py)
• Interaction with Windows OS
Component Relationships
a) User Interface Flow:
• Frontend components:
• NavbarSearch → SessionCard
• ActionRing → Session management actions
• Conditional components → Configuration layout
b) Data Flow:
• Frontend → Tauri Commands
• Tauri → Python Backend
• Python Backend → Windows OS
• Windows OS → Python Scripts
• Results back through the chain
Specific Components
Frontend Section:
┌─ Next.js UI Layer ─────────────┐
• Components │
• SessionCard │
• ActionRing │
• NavbarSearch │
• Conditional Logic │
• Configuration Layout │
• ┘
Middleware Section:
┌─ Tauri/Rust Layer ────────────┐
• Command Handlers │
• IPC Bridge │
• Python Sidecar Manager │
• ┘
Backend Section:
┌─ Python Backend ──────────────┐
• Window Management │
• Config Management │
• Session Restoration │
• ┘
Important Details to Highlight
• The "Jugaad" tech stack nature
• Python executable as a sidecar
• Window state management flow
• Session storage and restoration paths