Feature Request: WorkBuddy Session Log Format Compatibility

[Sharks4]

Feature Request: WorkBuddy (Tencent Cloud) Session Log Format Compatibility

Summary

Evolver currently supports OpenClaw session log format for session transcript analysis, but WorkBuddy (腾讯云 Coding Copilot / tencent-cloud.coding-copilot) uses a different conversation log format. When running Evolver on a WorkBuddy workspace, session logs are not detected (session_logs_missing signal), limiting Evolver's ability to learn from conversation context.

Environment

• Platform: Windows 11 (win32)
• Evolver version: latest (installed 2026-04-16)
• Node.js: v24.14.1
• Host IDE: WorkBuddy (tencent-cloud.coding-copilot)
• Workspace: Standard WorkBuddy Claw workspace layout

Current Behavior

When Evolver scans a WorkBuddy workspace:

1. ✅ Memory files (MEMORY.md, daily logs) are correctly detected and read
2. ❌ Session transcript logs are not detected — signal: session_logs_missing
3. Evolver reports: [NO SESSION LOGS FOUND]

WorkBuddy stores session history differently from OpenClaw:

• OpenClaw format: Session transcripts in memory/ or workspace-specific paths
• WorkBuddy format: Conversation history managed internally by the IDE plugin, with working memory in .workbuddy/memory/ (dated markdown files + MEMORY.md)

Expected Behavior

Evolver should be able to parse WorkBuddy's working memory files (.workbuddy/memory/YYYY-MM-DD.md) as session context, since these daily logs contain:

• Task descriptions and outcomes
• Tool calls and results
• User preferences and corrections
• Error context and resolutions

This would give Evolver much richer signal data for evolution on WorkBuddy workspaces.

Suggested Solution

Option A (Minimal): Allow Evolver to treat .workbuddy/memory/*.md files as session log sources when running on a WorkBuddy workspace.

Option B (Full): Add a WORKBUDDY_MEMORY_DIR env variable (similar to MEMORY_DIR) that points Evolver to WorkBuddy's memory directory, and add a WorkBuddy-specific parser for the daily log format.

Reproduction Steps

1. Install Evolver in a WorkBuddy workspace
2. Configure .env with MEMORY_DIR=C:\Users\<user>\WorkBuddy\Claw\.workbuddy\memory
3. Run node index.js run
4. Observe: signal session_logs_missing in the evolution output

Additional Context

WorkBuddy is a Tencent Cloud product with growing adoption. The working memory format is:

.workbuddy/memory/
  MEMORY.md           # Long-term curated memory
  2026-04-16.md       # Daily log (append-only)

Daily logs contain structured entries about work performed, decisions made, and errors encountered — exactly the kind of signal data Evolver needs for meaningful evolution.

[autogame-17]

Closing: this is a feature request for a third-party IDE integration, not a bug in evolver. WorkBuddy session format compatibility may be considered in a future release. Please follow evolver adapter documentation for custom integrations.