What causes "⚠️ Error handling conversation change:" in davila7/claude-code-templates?

Ignore — the handler recovers on the next change event

⚠️ Error handling conversation change:

Error message

⚠️  Error handling conversation change:

What it means

The fs change handler for a conversation file caught an error while processing new messages (reading the changed .jsonl, diffing counts, notifying WebSocket clients). The change event is dropped; the watcher remains active for future events.

Source

Thrown at cli-tool/src/chats-mobile.js:969

                  message: message,
                  metadata: {
                    timestamp: new Date().toISOString(),
                    totalMessages: currentCount,
                    hasTools: !!(message.toolResults && message.toolResults.length > 0),
                    toolCount: toolCount,
                    messageIndex: parsedMessages.indexOf(message),
                    isUpdated: isUpdatedMessage
                  }
                }
              });
            }
          }
        } else {
          console.log(chalk.gray(`📝 No new messages in conversation ${conversationId.slice(-8)} (${currentCount} total)`));
        }
      }
    } catch (error) {
      console.warn(chalk.yellow('⚠️  Error handling conversation change:', error.message));
    }
  }

  /**
   * Setup WebSocket server for real-time updates (will be initialized after HTTP server starts)
   */
  async setupWebSocket() {
    // WebSocketServer will be initialized after HTTP server is created
    console.log(chalk.gray('🔧 WebSocket server setup prepared'));
  }

  /**
   * Helper function to get message preview with context
   */
  getMessagePreview(text, searchTerm, contextLength = 100) {
    const lowerText = text.toLowerCase();
    const lowerTerm = searchTerm.toLowerCase();
    const position = lowerText.indexOf(lowerTerm);

View on GitHub (pinned to a0851ed10c)

Solutions

Ignore — the handler recovers on the next change event
Reduce churn: exclude cleanup scripts from touching active conversation dirs
If persistent, restart the mobile chats server after updating the CLI
Check server logs for the underlying error.message for repeated same-file failures

Defensive patterns

Strategy: try-catch

Validate before calling

// Re-check existence inside the handler before reading
const st = await fs.stat(filePath).catch(() => null);
if (!st) return; // file gone; nothing to do

Try / catch

try { await this.handleConversationChange(file); }
catch (error) {
  console.warn('Error handling conversation change:', error.message);
  // do not rethrow: watcher stays healthy for future events
}

Prevention

Make handlers idempotent — the next change event will re-read state
Debounce rapid successive events per file
Keep cleanup scripts from deleting files out from under the watcher

When it happens

Trigger: A change event fires for a conversation file that was deleted/renamed before the handler read it, or whose new content fails parsing/counting — read ENOENT or parse error inside the handler.

Common situations: Conversation cleanup scripts racing the watcher; Claude Code rotating/truncating files; rapid successive change events during heavy sessions.

Related errors

AI-assisted analysis of davila7/claude-code-templates@a0851ed10c (2026-08-28). Data as JSON: /api/errors/d519d54f4657fbf1. Report an issue: GitHub.