docs

Author: ericdallo

README.md

@@ -21,6 +21,7 @@ _Demo using [eca-vscode](https://github.com/editor-code-assistant/eca-vscode)_
   <a href="https://eca.dev/configuration"><strong>configuration</strong></a> •
   <a href="https://eca.dev/models"><strong>models</strong></a> •
   <a href="https://eca.dev/protocol"><strong>protocol</strong></a>
+  <a href="https://eca.dev/troubleshooting"><strong>troubleshooting</strong></a>
 </p>
 <hr>
 
@@ -90,10 +91,6 @@ Editors spawn the server via `eca server` and communicate via stdin/stdout, simi
 
 Check the planned work [here](https://github.com/orgs/editor-code-assistant/projects/1).
 
-## Troubleshooting
-
-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.
-
 ## Contributing
 
 Contributions are very welcome, please open an issue for discussion or a pull request.

docs/troubleshooting.md

@@ -0,0 +1,15 @@
+# Troubleshooting
+
+## Server logs
+
+ECA works with clients (editors) sending and receiving messages to server, a process, you can start server 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, all supported editors have options to set the __server args___ to help with that.
+
+
+## Doctor command
+
+`/doctor` command should log useful information to debug model used, server version, env vars and more.
+
+
+## Ask for help
+
+You can ask for help via chat [here](https://clojurians.slack.com/archives/C093426FPUG)

mkdocs.yml

@@ -12,6 +12,7 @@ nav:
     - Models: models.md
     - Development: development.md
     - Protocol: protocol.md
+    - Troubleshooting: troubleshooting.md
   - Features: features.md
   - Installation: installation.md
   - Models: models.md