Be able to run the application in web mode.

[tebayoso]

As requested here it might be useful to remove the dependency from an application, and be able to just run the application as a webserver. This poses a couple changes being the imediate one, how tauri is packaged. But they all can be fixed.

Working on it.

[tebabot]

Analysis

This is a feature request to run Opcode as a standalone web server (no Tauri desktop dependency), primarily for mobile/browser access to Claude Code sessions.

Current State (from code inspection)

• Partial implementation already exists:

  • src-tauri/src/web_main.rs + src-tauri/src/web_server.rs (Axum server on port 8080 by default).
  • WebSocket endpoint (/ws/claude) for real-time streaming of Claude execution.
  • REST API endpoints for projects, sessions, config, etc.
  • src/lib/apiAdapter.ts provides Tauri ↔ Web compatibility (REST + DOM events).
  • just web and just web-port PORT targets in the justfile.
  • Detailed design doc at web_server.design.md.

• just web builds the frontend and runs cargo run --bin opcode-web.

Issues / Gaps

The design document explicitly calls out several critical blockers that prevent full parity with the desktop app:

1. Session-scoped events — Backend dispatches generic claude-output events; UI expects claude-output:${sessionId}. Sessions interfere.
2. Process cancellation — /api/sessions/{id}/cancel is a no-op stub; no actual process kill or tracking.
3. stderr handling — Only stdout is streamed; errors from Claude go unseen.
4. Missing events — No claude-cancelled support.

Other notes:

• Bundled Claude binary path (src-tauri/binaries/...) does not exist in the current tree.
• Some REST endpoints still return "not available in web mode" errors (execution is only via WS).
• No authentication / CORS hardening for production exposure.
• No binaries/ directory in the repo (build step required).

Reproduction Assessment

The web server starts and serves the UI, and basic single-session Claude streaming works when a claude binary is in PATH. Multi-session, cancel, and error paths are broken per the design doc.

Proposed Next Steps

1. Fix the four critical items listed in web_server.design.md (Priority 1 + 2).
2. Ensure just web produces a working single-session experience end-to-end.
3. Add a simple health check + better binary discovery.
4. Document how to expose it safely (reverse proxy, auth, etc.).

Is the implementation in this issue the current state of "Working on it", or are there local changes / a branch we should review? Happy to help prioritize the fixes or review a PR.

(Labels: enhancement, web-mode)