Skip to main content
If you encounter issues with Chatledger, follow these steps to diagnose and resolve them.

​
Common Issues

This usually happens if the Antigravity LSP server is not responding or if there are no active conversations in the current workspace.
  1. Ensure Antigravity IDE’s LSP server is running.
  2. Check the output channel: Chatledger: View Logs.
  3. Verify you have active conversations in the current workspace.
If the .chatledger folder doesn’t appear: 1. Check if chatledger.exportDirectory is set to a valid path. 2. Ensure you have write permissions to the workspace root. 3. Try running Chatledger: Export Now manually to see if an error is thrown.
Chatledger only exports conversations associated with the current workspace.
  1. Conversations must be “bound” to the workspace you have open. 2. Orphaned conversations (created before a folder was opened) might be skipped. 3. The extension uses hash-based change detection. If a conversation hasn’t changed since the last export, it won’t be re-exported.
The extension communicates with localhost.
  • Ensure no firewall is blocking local connections.
  • The extension handles self-signed certificates automatically, so TLS warnings in logs are usually benign unless they block the connection entirely.

​
Debugging

To get more detailed information about what the extension is doing:
  1. Open the Output panel in VS Code (Ctrl+Shift+U).
  2. Select Chatledger from the dropdown menu.
  3. Look for error messages or status updates.
If you report an issue on GitHub, please include the relevant logs from the Output panel.