You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit b732ea7
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: README.md
+23-85Lines changed: 23 additions & 85 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,66 +18,24 @@ Hosted at **[web.eca.dev](https://web.eca.dev)** and deployed automatically via
18
18
3. The frontend connects to the ECA process via REST (commands) and SSE (live updates).
19
19
4. Both the editor and the web UI can send prompts, approve tool calls, and control chat — first response wins.
20
20
21
-
## Project structure
21
+
The web app is a thin shell around the **shared webview UI** (`eca-webview/` git submodule) — the same chat UI used in VS Code and IntelliJ. A bridge layer (`src/bridge/`) fakes the editor environment by:
│ └── src/ # Chat UI, Redux store, components — shared with VS Code / IntelliJ
38
-
├── public/
39
-
│ ├── 404.html # GitHub Pages SPA redirect
40
-
│ └── CNAME # web.eca.dev
41
-
└── .github/
42
-
└── workflows/
43
-
└── deploy.yml # Build + deploy to GitHub Pages
44
-
```
45
-
46
-
The `eca-webview/` directory is a **git submodule** containing the shared webview UI used by the VS Code extension, IntelliJ plugin, and this web app. The Vite alias `@webview` points to `eca-webview/src`.
47
-
48
-
## Run locally with Docker
49
-
50
-
The fastest way to run eca-web on your machine — no Node.js required:
23
+
-**Inbound:** SSE events from the server are dispatched as `window.postMessage` calls, matching the message types the editor extensions use.
24
+
-**Outbound:** The webview's `webviewSend()` calls are intercepted via `window.__ecaWebTransport` and mapped to REST API calls.
51
25
52
-
```bash
53
-
docker run -p 8080:80 ghcr.io/editor-code-assistant/eca-web
54
-
```
55
-
56
-
Then open [http://localhost:8080](http://localhost:8080).
26
+
This means the chat UI, Redux store, and all components work identically across editors — only the transport layer differs.
|`<version>`| Semantic version (e.g. `1.0.0`, `1.0`) when tagged |
30
+
All requests use `Authorization: Bearer <token>` headers — no cookies. SSE is consumed via `fetch()` + `ReadableStream` (not `EventSource`) to support custom auth headers.
|`enabled`|`false`| Enable the embedded HTTP server |
127
-
|`host`| auto-detected LAN IP | Host in the logged URL (LAN IP, domain, tunnel) |
128
-
|`port`| random free port | Port the HTTP server listens on |
129
-
|`password`| auto-generated token | Auth token; auto-generated and logged if unset |
130
-
131
-
## Architecture
132
-
133
-
The web app is a thin shell around the **shared webview UI** (`eca-webview`). The bridge layer (`src/bridge/`) translates between two protocols:
134
-
135
-
-**Inbound** (server → browser): SSE events are parsed and dispatched as `window.postMessage` calls, matching the same message types the VS Code / IntelliJ extensions use.
136
-
-**Outbound** (browser → server): The webview's `webviewSend()` calls are intercepted via `window.__ecaWebTransport` and mapped to REST API calls.
137
-
138
-
This means the chat UI, Redux store, and all components work identically across VS Code, IntelliJ, and the web — only the transport layer differs.
139
-
140
-
### Authentication
141
-
142
-
All requests use `Authorization: Bearer <token>` headers. No cookies — avoids `Secure`/`SameSite` issues with non-localhost connections. SSE is consumed via `fetch()` + `ReadableStream` (not `EventSource`) to support custom headers.
80
+
Go to [web.eca.dev](https://web.eca.dev), enter the host IP and password, and hit **Discover & Connect** — it scans ports 7777–7787 and connects to any running ECA sessions automatically.
0 commit comments