swe-wm-update

Queue non-blocking Working Memory updates to WM_{session}_session.md files.

1|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/EarthmanWeb/serena-workflow-engine --skill swe-wm-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: swe-wm-update
Source: https://github.com/EarthmanWeb/serena-workflow-engine/tree/main/skills/swe-wm-update
Command: npx skills add https://github.com/EarthmanWeb/serena-workflow-engine --skill swe-wm-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables non-blocking updates to Working Memory (WM) entries during long-running or multi-step workflows by delegating writes to a background daemon, preventing blocking of the main execution thread.

Core Features & Use Cases

  • Non-blocking WM writes: Queues updates to WM_{session}_session.md and coalesces writes to minimize IO.
  • Validation & guardrails: Validates required fields (session_id, task, feature, state, progress) and enforces anti-pattern protection for risky edits.
  • Operational range: Works across all WF_* states, supports multiple operation types such as full_write, state_update, edit_tracking, and more, and is suitable for per-session memory tracking during SWE runs.

Quick Start

Queue a non-blocking WM update using the daemon to write to .serena/memories/WM_{session}_session.md.

Frequently Asked Questions about swe-wm-update

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update working memory asynchronously without blocking the main workflow?

Queue non-blocking updates to working memory entries via a background daemon, which coalesces writes to minimize IO and prevents blocking of the main execution thread during multi-step workflows.

What is a background daemon for non-blocking memory writes and how does it work?

A background daemon for non-blocking memory writes queues updates to session memory files asynchronously, validates required fields, and coalesces multiple operations to ensure safe persistence without halting execution.

How do I validate working memory fields before writing to a session file?

Validate working memory fields by enforcing required inputs such as session_id, task, feature, state, and progress, which triggers anti-pattern protection for risky edits before queueing the write operation.

Can I use asynchronous memory updates across all workflow states?

Yes, asynchronous memory updates operate across all workflow states and support multiple operation types including full_write, state_update, and edit_tracking for per-session memory tracking.

What is the best way to coalesce working memory writes for IO efficiency?

The best way to coalesce working memory writes is delegating them to a background daemon that queues updates and combines them to minimize IO operations during asynchronous persistence.

Why does my main execution thread block when updating session memory?

Your main execution thread blocks during session memory updates because synchronous writes halt processing; delegating these updates to a background daemon enables non-blocking, asynchronous persistence.