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
Copy file name to clipboardExpand all lines: README.md
+2-4Lines changed: 2 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,17 +53,15 @@ Install the plugin for your editor and ECA server will be downloaded and started
53
53
54
54
## How it works
55
55
56
-
Editors spawn the server via `eca server` and communicate via stdin/stdout. Logs are printed to stderr, use `--verbose` to log client<->server communication or `--log-level debug` to log more info like LLM responses.
57
-
58
-
Supported editors already download latest server on start and require no extra configuration
56
+
Editors spawn the server via `eca server` and communicate via stdin/stdout, similar to LSPs. Supported editors already download latest server on start and require no extra configuration.
59
57
60
58
## Roadmap
61
59
62
60
Check the planned work [here](https://github.com/orgs/editor-code-assistant/projects/1/views/1).
63
61
64
62
## Troubleshooting
65
63
66
-
You can start eca with `--log-level debug` which should log helpful information in stderr buffer like what is being sent to LLMs.
64
+
You can start eca with `--log-level debug`or `--verbose`which should log helpful information to stderr buffer like what is being sent to LLMs or what ECA is responding to editors.
0 commit comments