bug feature-request conversation-tracking

[walktank]

title: [Bug] Conversation Tracking Feature Not Working

Cursor Bug Report: Conversation Tracking Not Working

Environment

• OS: Windows 10.0.22631
• Workspace Path: D:/av
• Shell: C:\Program Files\PowerShell\7\pwsh.exe

Issue Description

The conversation tracking feature is not working despite proper configuration in .cursor/settings.json. No conversation logs are being generated.

Configuration

{
    "conversation_tracking": {
      "enabled": true,
      "output_dir": "D:/av/cursor_talks",
      "log_level": "debug",  
      "rules": {
        "file_specific_logs": {
          "enabled": true,
          "format": {
            "timestamp": true,
            "timestamp_format": "%Y-%m-%d %H:%M:%S",
            "speaker_prefix": true
          }
        }
      },
      "triggers": {
        "on_file_focus": true,
        "on_file_mention": true
      }
    }
}

Expected Behavior

1. Create output directory if it doesn't exist
2. Generate conversation logs when:
   • File is focused
   • File is mentioned in conversation
3. Save logs according to configured format

Actual Behavior

1. Output directory is not created
2. No conversation logs are generated
3. No error messages or warnings are shown
4. Feature appears completely non-functional

Steps to Reproduce

1. Create .cursor/settings.json with conversation tracking enabled
2. Set valid output directory and configuration
3. Focus on different files or mention files in conversation
4. Check output directory for logs

Additional Notes

• Configuration file is valid JSON
• All required settings are present
• No error messages in console
• Feature appears to be completely inactive rather than partially working

Impact

Unable to track and document conversations about code, which impacts:

1. Code review documentation
2. Development history tracking
3. Team collaboration
4. Project documentation

Suggested Investigation Areas

1. Configuration file loading logic
2. Event handling implementation
3. File system permissions
4. Logging implementation

Workarounds Attempted

1. Using relative path for output_dir
2. Different directory names
3. Different permission levels
4. Different file patterns