Skip to content

Clean up dead Memorizer and file-based memory tool code #225

@Aaronontheweb

Description

@Aaronontheweb

Goal

Remove dead code from the memory subsystem that was superseded by the SQLite memory redesign.

Context

The SQLite-backed memory system (SqliteStoreMemoryTool, SqliteFindMemoriesTool, etc.) is now the only active memory backend. The Memorizer MCP-backed and file-based memory tools are no longer registered in Program.cs and have no active code paths. MemoryConfig.Provider defaults to "sqlite" and no other provider is wired.

Files to Delete

Memorizer-backed tools (all in src/Netclaw.Actors/Memory/)

  • MemorizerStoreMemoryTool.cs — previously the only subagent consumer (memory-curator), now dead
  • MemorizerFindMemoriesTool.cs
  • MemorizerGetMemoriesTool.cs
  • MemorizerUpdateMemoryTool.cs
  • MemorizerMemoryExtractor.cs

File-based memory tools

  • FileMemoryStore.cs
  • FileFindMemoriesTool.cs
  • FileGetMemoriesTool.cs
  • StoreMemoryTool.cs (file-backed variant)
  • FileUpdateMemoryTool.cs
  • FileMemoryExtractor.cs

Corresponding test files

  • All test files for the above in src/Netclaw.Actors.Tests/

Additional Cleanup

  • Remove the "files" and "memorizer" provider branches from any conditional logic in ToolIndexUpdater or context layers
  • Consider whether MemoryConfig.Provider still needs to be a string, or can be simplified since only "sqlite" is supported
  • Clean up MemoryIndexContextLayer states that reference FileBacked, MemorizerConnected, MemorizerDisconnected

Related

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions