Back to Signal Feed
CodeTracked since May 18, 2026

OpenCode plugin hardened for session-safe memory capture

The burst’s main change is a hardening sweep of the OpenCode plugin’s session lifecycle and event handling so hooks, session IDs, and per-session state are handled correctly, preventing dropped or mis-attributed memory observations in concurrent agent workflows.

OpenCode pluginprompt_submit hooksession.createdsession.deleted

What Happened

  • The burst’s main change is a hardening sweep of the OpenCode plugin’s session lifecycle and event handling so hooks, session IDs, and per-session state are handled correctly, preventing dropped or mis-attributed memory observations in concurrent agent workflows.
  • The burst’s main change is a hardening sweep of the OpenCode plugin’s session lifecycle and event handling so hooks, session IDs, and per-session state are handled correctly, preventing dropped or mis-attributed memory observations in concurrent agent workflows.
  • 1 evidence item attached for review.

What is Different

Before

Scattered source updates, isolated context, and manual follow-up across multiple feeds.

Now

Implemented and stabilized concrete fixes in the OpenCode integration: corrected the hook type mismatch, fixed event-to-session mapping across message/session lifecycle callbacks, switched shared caches/maps to session-scoped behavior, guarded malformed inputs in context pushes, and adjusted injection/cleanup ordering to avoid permanently skipping session initialization or leaking stale state.

Why Track This

Why It Matters

OpenCode users and operators should see more stable memory behavior when multiple agent sessions run at once, because session context and captured tool outputs are less likely to leak across sessions or disappear due to lifecycle misalignment. The remaining watch list is on remaining edge cases in session-id fallback chains and context-fetch retries; if those regress, memory recall timing and recall quality could still become inconsistent in long-running or interrupted conversations.

Impact

OpenCode users and operators should see more stable memory behavior when multiple agent sessions run at once, because session context and captured tool outputs are less likely to leak across sessions or disappear due to lifecycle misalignment. The remaining watch list is on remaining edge cases in session-id fallback chains and context-fetch retries; if those regress, memory recall timing and recall quality could still become inconsistent in long-running or interrupted conversations.

What To Watch Next

  • Watch whether OpenCode plugin becomes a repeated pattern.
  • Track follow-up changes around Agentic RAG.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: session_id_fallback_resolution_regressions_in_message_updated, stashed_files_cross_session_contamination.
Open Topic TimelineOpen Technical EventOpen Original Sourcesession_id_fallback_resolution_regressions_in_message_updated / stashed_files_cross_session_contamination / context_injection_marker_persistence_after_timeout / session_idle_cleanup_for_crash_terminated_sessions

Supporting Evidence

GITHUB COMMIT BURSTHigh Trust

rohitg00/agentmemory commit burst: 10 commits in 7 days

Multiple fixes in this burst correct the OpenCode plugin path (including `prompt_submit` hook matching, session ID resolution, per-session stash/dedup scope, and context-injection timing) after issues like null session IDs, cross-session contamination, and stale state flags were found.