mirror of
https://github.com/thedotmack/claude-mem
synced 2026-04-26 01:25:10 +02:00
2659ec3231
* Refactor CLAUDE.md and related files for December 2025 updates - Updated CLAUDE.md in src/services/worker with new entries for December 2025, including changes to Search.ts, GeminiAgent.ts, SDKAgent.ts, and SessionManager.ts. - Revised CLAUDE.md in src/shared to reflect updates and new entries for December 2025, including paths.ts and worker-utils.ts. - Modified hook-constants.ts to clarify exit codes and their behaviors. - Added comprehensive hooks reference documentation for Claude Code, detailing usage, events, and examples. - Created initial CLAUDE.md files in various directories to track recent activity. * fix: Merge user-message-hook output into context-hook hookSpecificOutput - Add footer message to additionalContext in context-hook.ts - Remove user-message-hook from SessionStart hooks array - Fixes issue where stderr+exit(1) approach was silently discarded Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * Update logs and documentation for recent plugin and worker service changes - Added detailed logs for worker service activities from Dec 10, 2025 to Jan 7, 2026, including initialization patterns, cleanup confirmations, and diagnostic logging. - Updated plugin documentation with recent activities, including plugin synchronization and configuration changes from Dec 3, 2025 to Jan 7, 2026. - Enhanced the context hook and worker service logs to reflect improvements and fixes in the plugin architecture. - Documented the migration and verification processes for the Claude memory system and its integration with the marketplace. * Refactor hooks architecture and remove deprecated user-message-hook - Updated hook configurations in CLAUDE.md and hooks.json to reflect changes in session start behavior. - Removed user-message-hook functionality as it is no longer utilized in Claude Code 2.1.0; context is now injected silently. - Enhanced context-hook to handle session context injection without user-visible messages. - Cleaned up documentation across multiple files to align with the new hook structure and removed references to obsolete hooks. - Adjusted timing and command execution for hooks to improve performance and reliability. * fix: Address PR #610 review issues - Replace USER_MESSAGE_ONLY test with BLOCKING_ERROR test in hook-constants.test.ts - Standardize Claude Code 2.1.0 note wording across all three documentation files - Exclude deprecated user-message-hook.ts from logger-usage-standards test Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * fix: Remove hardcoded fake token counts from context injection Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * Address PR #610 review issues by fixing test files, standardizing documentation notes, and verifying code quality improvements. * fix: Add path validation to CLAUDE.md distribution to prevent invalid directory creation - Add isValidPathForClaudeMd() function to reject invalid paths: - Tilde paths (~) that Node.js doesn't expand - URLs (http://, https://) - Paths with spaces (likely command text or PR references) - Paths with # (GitHub issue/PR references) - Relative paths that escape project boundary - Integrate validation in updateFolderClaudeMdFiles loop - Add 6 unit tests for path validation - Update .gitignore to prevent accidental commit of malformed directories - Clean up existing invalid directories (~/, PR #610..., git diff..., https:) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com> * fix: Implement path validation in CLAUDE.md generation to prevent invalid directory creation - Added `isValidPathForClaudeMd()` function to validate file paths in `src/utils/claude-md-utils.ts`. - Integrated path validation in `updateFolderClaudeMdFiles` to skip invalid paths. - Added 6 new unit tests in `tests/utils/claude-md-utils.test.ts` to cover various rejection cases. - Updated `.gitignore` to prevent tracking of invalid directories. - Cleaned up existing invalid directories in the repository. * feat: Promote critical WARN logs to ERROR level across codebase Comprehensive log-level audit promoting 38+ WARN messages to ERROR for improved debugging and incident response: - Parser: observation type errors, data contamination - SDK/Agents: empty init responses (Gemini, OpenRouter) - Worker/Queue: session recovery, auto-recovery failures - Chroma: sync failures, search failures (now treated as critical) - SQLite: search failures (primary data store) - Session/Generator: failures, missing context - Infrastructure: shutdown, process management failures - File Operations: CLAUDE.md updates, config reads - Branch Management: recovery checkout failures Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com> * fix: Address PR #614 review issues - Remove incorrectly tracked tilde-prefixed files from git - Fix absolute path validation to check projectRoot boundaries - Add test coverage for absolute path validation edge cases Closes review issues: - Issue 1: ~/ prefixed files removed from tracking - Issue 3: Absolute paths now validated against projectRoot - Issue 4: Added 3 new test cases for absolute path scenarios Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * build assets and context --------- Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
9.7 KiB
9.7 KiB
Issue #597: Too Many Bugs - Technical Analysis Report
Date: 2026-01-07 Issue: #597 Author: TullyMonster Labels: bug Status: Open
1. Executive Summary
Issue #597 is a bug report from user TullyMonster containing four screenshots documenting various issues encountered over a two-day period. The report lacks textual description of the specific bugs, relying entirely on visual evidence. The user apologizes for the delay in reporting, stating the bugs significantly hampered their productivity.
Key Limitation: This analysis is constrained by the image-only nature of the report. The four screenshots (with dimensions 2560x1239, 1511x628, 2560x3585, and 1907x1109 pixels) cannot be programmatically analyzed to extract specific error messages or UI states.
Community Confirmation: Another user (ham-zax) commented agreeing with the severity: "yeah atleast make beta testing, it hampers productivity"
2. Problem Analysis
2.1 Contextual Analysis
Based on the timing (January 7, 2026), the user was running claude-mem v9.0.0, which was released on January 5, 2026. This version introduced the "Live Context System with Distributed CLAUDE.md Generation" (PR #556), a significant architectural change.
The same user (TullyMonster) also commented on Issue #596 with "same as you," indicating they experienced the ProcessTransport error that causes all observations to fail silently.
2.2 Related Issues Filed Same Day
| Issue | Title | Relevance |
|---|---|---|
| #596 | ProcessTransport is not ready for writing - Generator aborted | User confirmed experiencing this |
| #598 | Too many messages, polluting conversation history | UX issue with plugin messages |
| #602 | PostToolUse Error: worker-service.cjs failed to start | Worker startup failures on Windows |
2.3 Screenshot Analysis (Inferred)
Based on screenshot dimensions and the pattern of issues being reported on v9.0.0:
| Screenshot | Dimensions | Likely Content |
|---|---|---|
| Image 1 | 2560x1239 | Full-screen terminal/IDE showing errors |
| Image 2 | 1511x628 | Error message dialog or log output |
| Image 3 | 2560x3585 | Very tall - likely scrolling log output or multiple stacked errors |
| Image 4 | 1907x1109 | Terminal or UI showing bug manifestation |
3. Technical Details
3.1 Probable Bug Categories (v9.0.0)
Based on the cluster of issues around this time, the bugs likely fall into these categories:
A. ProcessTransport Failures (High Probability)
error: ProcessTransport is not ready for writing
at write (/Users/.../worker-service.cjs:1119:5337)
at streamInput (/Users/.../worker-service.cjs:1122:1041)
- Every observation fails with "Generator aborted"
- Queue depth accumulates (87+ unprocessed items)
- Worker UI works, but no observations are stored
B. Worker Startup Failures (Moderate Probability)
[ERROR] [HOOK] save-hook failed Worker did not become ready within 15 seconds. (port 37777)
[ERROR] [SYSTEM] Worker failed to start (health check timeout)
[ERROR] [SYSTEM] Failed to start server. Is port 37777 in use?
C. Session/Memory Issues (Moderate Probability)
[ERROR] Cannot store observations: memorySessionId not yet captured
[WARN] Generator exited unexpectedly
D. Conversation Pollution (Possible)
Multiple "Hello memory agent" messages appearing in conversation history, disrupting workflow.
3.2 Environment Assumptions
Based on the user's participation in Issue #596 (macOS focus) and screenshot dimensions:
- OS: Likely macOS (high-resolution display)
- Version: v9.0.0 (released Jan 5, 2026)
- Runtime: Bun 1.3.x
4. Impact Assessment
4.1 User Impact
| Impact Area | Severity | Description |
|---|---|---|
| Productivity | Critical | User spent 2 days dealing with bugs instead of coding |
| Data Loss | High | Observations not being stored (ProcessTransport issue) |
| Workflow Disruption | High | Multiple bugs compounding the problem |
| User Trust | Medium | User apologizes for delay, showing frustration |
4.2 Broader Impact
The community response indicates this is not an isolated incident:
- ham-zax: "yeah atleast make beta testing, it hampers productivity"
- Multiple users on #596: "same as you", "same 3"
This suggests v9.0.0 has significant stability issues affecting multiple users.
5. Root Cause Analysis
5.1 Likely Root Causes
Primary: ProcessTransport Race Condition
The Claude Agent SDK's ProcessTransport class attempts to write to stdin before the spawned process is ready. This is a timing/race condition that manifests inconsistently.
Evidence:
- Clean installs affected
- Both Bun 1.3.4 and 1.3.5 affected
- Prompts ARE recorded correctly, only SDK agent fails
Secondary: Version 9.0.0 Regression
PR #556 introduced significant changes to the Live Context System, which may have:
- Introduced new race conditions
- Affected worker lifecycle management
- Changed timing of critical initialization steps
Tertiary: Platform-Specific Issues
Windows users experiencing additional problems:
wmiccommand not recognized (newer Windows versions)- Port binding conflicts
- PowerShell variable escaping in Git Bash
5.2 Contributing Factors
| Factor | Description |
|---|---|
| Rapid releases | v8.5.10 to v9.0.0 in 2 days |
| Complex architecture | 5 lifecycle hooks, async worker, SDK integration |
| Limited beta testing | Community comment suggests need for beta channel |
| Platform diversity | macOS, Windows, Linux all have different issues |
6. Recommended Solutions
6.1 Immediate Actions (For User)
-
Request Clarification - Post a comment asking:
@TullyMonster Thank you for the detailed screenshots! To help us investigate these issues more effectively, could you please provide: 1. Which specific errors/behaviors are shown in each screenshot? 2. Your environment (OS, claude-mem version, Bun version)? 3. Relevant log entries from ~/.claude-mem/logs/worker-YYYY-MM-DD.log? 4. Steps to reproduce any of these issues? We've identified several related issues (#596, #598, #602) and want to ensure we're addressing your specific problems. -
Verify Version - Confirm user is on v9.0.0
-
Link Related Issues - Cross-reference with:
- #596 (ProcessTransport)
- #598 (message pollution)
- #602 (worker startup)
6.2 Technical Fixes (For Maintainers)
| Priority | Fix | Issue |
|---|---|---|
| P0 | Fix ProcessTransport race condition | #596 |
| P1 | Improve worker startup reliability | #602 |
| P2 | Reduce conversation pollution | #598 |
| P3 | Add better error recovery | General |
6.3 Process Improvements
- Beta Channel - Consider a beta release channel for major versions
- Automated Testing - Expand CI to catch lifecycle issues
- Error Reporting - Add structured error logging that's easier to share
- Bug Report Template - Update template to encourage log submission
7. Priority/Severity Assessment
7.1 Individual Issue Severity
| Aspect | Rating | Justification |
|---|---|---|
| Frequency | High | Multiple users affected |
| Impact | Critical | Complete workflow disruption |
| Urgency | High | Blocking user productivity |
| Complexity | Medium | Root causes identified in related issues |
7.2 Overall Priority
Priority: P1 - High
Rationale:
- User lost 2 days of productivity
- Multiple corroborating reports from community
- v9.0.0 appears to have introduced regressions
- Plugin is actively harming user experience rather than helping
7.3 Recommended Triage
- Consolidate - This issue likely duplicates #596, #602, and/or #598
- Request Details - Ask user to specify which screenshots map to which issues
- Consider Rollback - If issues persist, consider advising users to downgrade to v8.5.10
- Hotfix - Prioritize a v9.0.1 release addressing ProcessTransport issue
8. Appendix
8.1 Related Issues Timeline
| Date | Issue | Event |
|---|---|---|
| Jan 5 | - | v9.0.0 released |
| Jan 6 | #571 | "Cannot store observations" |
| Jan 6 | #573 | "bun does not auto install" |
| Jan 7 01:10 | #588 | API key cost warning |
| Jan 7 10:17 | #596 | ProcessTransport failures |
| Jan 7 13:09 | #597 | This issue |
| Jan 7 14:08 | #598 | Conversation pollution |
| Jan 7 18:13 | #602 | Worker startup failures |
8.2 Screenshot Metadata
| # | Dimensions | Aspect Ratio | Notes |
|---|---|---|---|
| 1 | 2560x1239 | 2.07:1 | Wide monitor screenshot |
| 2 | 1511x628 | 2.41:1 | Cropped dialog/window |
| 3 | 2560x3585 | 0.71:1 | Tall scrolling capture |
| 4 | 1907x1109 | 1.72:1 | Standard window capture |
8.3 Version History
| Version | Date | Notable Changes |
|---|---|---|
| v8.5.10 | Jan 5 | Pre-v9 stable |
| v9.0.0 | Jan 5 | Live Context System (PR #556) |
| v9.0.0+ | Jan 7 | Version mismatch fix (PR #567) |
9. Conclusion
Issue #597 represents user frustration with multiple bugs encountered in claude-mem v9.0.0. While the image-only report makes specific diagnosis difficult, contextual analysis strongly suggests the user experienced:
- ProcessTransport failures causing observation loss (#596)
- Possibly worker startup issues (#602)
- Possibly conversation pollution (#598)
Recommended Next Steps:
- Request additional details from the user
- Link this issue to #596 as likely duplicate/related
- Prioritize v9.0.1 hotfix for ProcessTransport issue
- Consider implementing a beta testing channel for major releases
Report generated: 2026-01-07 Analysis based on: GitHub issue data, related issues, commit history, and contextual inference