From 99152a1116e85502715dea7dd39b418547cd28ae Mon Sep 17 00:00:00 2001 From: Enrique Gonzalez Date: Tue, 4 Mar 2025 08:47:27 -0800 Subject: [PATCH] Update troubleshooting.mdx to include how to debug slowness --- docs/cody/troubleshooting.mdx | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/docs/cody/troubleshooting.mdx b/docs/cody/troubleshooting.mdx index 52f681d80..17e3db460 100644 --- a/docs/cody/troubleshooting.mdx +++ b/docs/cody/troubleshooting.mdx @@ -13,6 +13,19 @@ If you're experiencing issues with Cody not responding in chat, follow these ste - Ensure you have the latest version of the [Cody VS Code extension](https://marketplace.visualstudio.com/items?itemName=sourcegraph.cody-ai). Use the VS Code command `Extensions: Check for Extension Updates` to verify - Check the VS Code error console for relevant error messages. To open it, run the VS Code command `Developer: Toggle Developer Tools` and then look in the `Console` for relevant messages +### Cody responses/completions are slow + +If you're experiencing issues with Cody's responses or completions being too slow: + +- Ensure you have the latest version of the [Cody VS Code extension](https://marketplace.visualstudio.com/items?itemName=sourcegraph.cody-ai). Use the VS Code command `Extensions: Check for Extension Updates` to verify +- Enable verbose logging, restart the extension and reproduce the issue seen again (see below `Access Cody logs` for how to do this +- Send information to the our Support Team at support@sourcegraph.com + +Some additional information that will be valuable: +- Where are you located? Any proxies or firewalls in use? +- Does this happen with multiple providers/models? Which models have you used? + + ### Access Cody logs VS Code logs can be accessed via the **Outputs** view. You will need to set Cody to verbose mode to ensure important information to debug is on the logs. To do so: