Summary

Two different failures when trying to use OneContext on Windows, depending on whether it's run natively or inside WSL2.

Bug 1: Windows (PowerShell) — Crash on launch

Running onecontext in PowerShell crashes immediately with the following traceback:

cli.py:149 in main
 → _launch_dashboard(dev=dev)
cli.py:39 in _launch_dashboard
 → from .dashboard.singleton import acquire_dashboard_lock, dashboard_lock_message
singleton.py:14 in <module>
 → from ..file_lock import FileLock
file_lock.py:3 in <module>
 → import fcntl
ModuleNotFoundError: No module named 'fcntl'

Root cause: realign/file_lock.py unconditionally imports fcntl at line 3 with no platform guard. fcntl is a Unix-only module and does not exist on Windows.

Bug 2: WSL2 (Ubuntu 24.04) — "Failed to create terminal"

The OneContext dashboard launches successfully inside WSL2 and displays contexts. However, when attempting to create/open a session, a red toast notification appears at the bottom-right:

Agent
Failed to create terminal

This is likely a separate issue related to tmux or pty/terminal creation inside the WSL2 environment.

Environment

Steps to Reproduce

Windows

1. Open PowerShell
2. Run onecontext
3. Observe crash with ModuleNotFoundError: No module named 'fcntl'

WSL2

1. Open Ubuntu 24.04 terminal in WSL2
2. Run onecontext — dashboard opens successfully
3. Click "+" on a context or try to create a new session
4. Observe red toast: "Agent — Failed to create terminal"