Skip to content

conch/evaluate desktop support windows linux - #246

Draft
Amitgb14 wants to merge 6 commits into
masterfrom
conch/evaluate-desktop-support-windows-linux
Draft

Amitgb14 wants to merge 6 commits into
masterfrom
conch/evaluate-desktop-support-windows-linux

Conversation

@Amitgb14

Copy link
Copy Markdown
Owner
  • Docs: compare conch with herdr, T3 Code and Orca
  • Docs: replace the comparison table with a Why conch page
  • Docs: diagrams a page can draw — feature cards, the autopilot loop, a task's flow, agent states
  • Docs: refresh the introduction and Why conch with the desktop and pictures
  • Docs: keep the guide pages short — a feature, how to use it, a picture
  • Docs: take Conch Cloud out of the navigation and say it is not enabled
  • Test that the website hides Conch Cloud
  • Open links in Windows' browser when conch runs under WSL
  • Evaluate desktop support on Windows and Linux
  • Evaluation: center it on Conch.app, the desktop app
  • Installation page: split the Windows paragraph under the guide limit

Amitgb14 and others added 6 commits November 15, 2026 14:32
Both the TUI and the commands opened a link with xdg-open off a Mac.
Under WSL that is usually installed with no browser behind it, so a link
conch opened (a PR, the settings page, a sandbox) did nothing. The choice
now lives once in internal/desktop: wslview where wslu is installed, else
Windows' URL handler through rundll32, else xdg-open as before. WSL is
told by WSL_DISTRO_NAME or a kernel release naming Microsoft.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
docs/plans/desktop-windows-linux.md says where conch stands: Linux has
the TUI and conch app but no native window (ConchKit is near portable,
ConchApp is AppKit); Windows does not build, and what blocks it is the
pane and reload core (ptys, exec, process groups, peer pids), so the
recommendation is WSL 2 made first-class rather than a native port.
The installation page now says so, and two end-to-end rows cover what
fakes cannot: links under real WSL, and conch app on GNOME and KDE.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The question was Conch.app on Windows and Linux, not the conch binary.
The plan now says what the app is made of (ConchKit near portable,
ConchApp AppKit and SwiftUI throughout), why the pane terminal decides
it (libghostty embeds only on macOS), which toolkits could carry a
second front end, and that a Windows app can drive conch inside WSL
through the stdio transport the app already uses for machines
(wsl.exe conch bridge / attach) rather than waiting on a Windows port.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
TestDocsGuidesAreShort keeps each paragraph under 60 words; the Linux
and Windows note was 72.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
origin/master took 9.178–9.182 for the mobile workbench rows, so the
WSL and conch app rows moved on in the rebase.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Replaces the evaluation with the plan it led to: a native app per OS
(Swift on the Mac, GTK 4 + VTE on Linux, WinUI 3 on Windows) that only
draws; conch desktop, a Go bridge in the conch binary over stdio that
owns machines, the tree, layout, notifications and how to attach; and
the servers unchanged. Windows starts with the bridge and server in
WSL 2 and may get a native ConPTY server later, without hot reload.
Messages, packaging, testing, phases, risks and the decisions still
open are written down, with what Herdr and T3 Code do for comparison.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Amitgb14
Amitgb14 force-pushed the conch/evaluate-desktop-support-windows-linux branch from c360908 to 884a428 Compare November 15, 2026 22:41

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant