Summary

The "Recap Bot" workspace ritual is labeled daily on the dashboard, but support confirmed recaps are generated automatically at session boundaries — there is no /recap command or manual trigger, and a new session should prompt the prior session's recap.

In practice, recaps stalled for ~14 days (last recap 2026-07-05; observed 2026-07-19) while working through the VS Code Copilot MCP integration (https://mcp.contextstream.io/mcp). The session-boundary signal that Desktop Workbench emits does not appear to fire through the VS Code MCP path, so no recap is generated.

Observed behavior

• Dashboard: Recap Bot · workspace ritual · daily · due, last recap 1w ago (actually ~14 days).
• No recap events generated during continuous work via the VS Code Copilot MCP server.
• session toolset exposes no close_session / end_session action; "closing" is implicit (a new init() with a fresh session_id ends the prior session).
• Verification gap (added 2026-07-19): From the VS Code MCP path we cannot confirm whether a recap fired. session(action="smart_search", query="recap") returns a capped list of 10 results shown as "Untitled" with no timestamps, and session(action="delta", since=...) is broken (returns 0 items). So there is no reliable API to enumerate/list recap events or read their dates.

Expected behavior

• Recaps fire reliably at session boundaries regardless of client (Desktop Workbench and VS Code Copilot MCP).
• The dashboard label should reflect the actual trigger model (session-boundary, not daily), or the docs should state this clearly.
• There is a programmatic way to list/retrieve recap events (with timestamps) so clients can verify recaps fired.

Requests

1. Doc correction: clarify in docs/dashboard that recaps are session-boundary triggered, not a daily cron; the daily label is misleading.
2. VS Code MCP gap: ensure the MCP path emits the same session-boundary signal Desktop Workbench does so recaps fire.
3. Feature request — manual trigger: add a manual /recap command or explicit close_session action, since the boundary is currently implicit and easy to miss (especially in long-lived MCP sessions).
4. Feature request — recap retrieval API: expose a tool/action to list recap events with timestamps (e.g. session(action="list_recaps") or a recap event_type filter in smart_search/memory.search). Today smart_search caps recap results at 10 "Untitled" entries with no dates and delta is broken, so recaps cannot be enumerated or verified from the MCP path.

Environment

• Hosted MCP server: v0.5.39
• Local CLI contextstream-mcp: v0.4.81
• Client: VS Code + GitHub Copilot Chat (remote HTTP MCP at https://mcp.contextstream.io/mcp)
• Related: issue Document the MCP server types and where to find each one's release notes #71 (version-line confusion between hosted server and local CLI).