memory

Save and load WDS agent session state in a project-scoped progress directory.

Updated Dec 26, 2025
One-click install
npx skills add https://github.com/tiween/tiween --skill memory-tiween
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: memory
Source: https://github.com/tiween/tiween/tree/main/.agents/skills/memory
Command: npx skills add https://github.com/tiween/tiween --skill memory-tiween

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a robust session state backend for WDS, addressing the need for persistent state management across sessions.

Core Features & Use Cases

  • Persistent State: Saves and loads state data for WDS sessions, ensuring continuity and state retention.
  • Agent Compatibility: Supports multiple WDS agents (saga, freya, mimir).
  • File-Based Storage: Utilizes a progress/ directory for storing state data, scoped to the project and machine-specific.

Quick Start

Save the session state for the 'saga' agent using the memory skill.

Frequently Asked Questions about memory

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

FAQPage Schema
How do I persist WDS agent session state across multiple sessions?

To persist WDS agent session state, you need a file-based state backend that saves and loads progress data. This Skill handles session state retention by operating synchronously within a project-scoped progress directory, ensuring continuity for saga, freya, and mimir agents.

Does this session state backend support the saga, freya, and mimir WDS agents?

Yes, the session state backend supports saga, freya, and mimir WDS agents. It provides compatible state persistence and management capabilities, allowing these specific agents to save and load their session data effectively.

What is the best way to manage state retention for WDS agents locally?

The best way to manage local state retention for WDS agents is using synchronous file-based operations within a project-scoped progress directory. This approach ensures machine-specific state persistence without requiring external databases or complex configurations.

How does file-based session state storage work for WDS?

File-based session state storage for WDS works by synchronously saving and loading state data into a progress directory. This directory is scoped to your current project, ensuring that the session state remains isolated and machine-specific.

Do I need external dependencies to save and load WDS session state?

No, you do not need external dependencies to save and load WDS session state. This Skill relies entirely on local file-based operations within a project-scoped progress directory, requiring no additional libraries or external services.