As a prerequisite for the Async Event-Driven Swarm architecture (see #38), we need to decouple SharedTaskStateManager from the vscode.Memento dependency.
Currently, SharedTaskStateManager relies on VS Code's extension context, which breaks the standard of keeping the underlying MCP server as a pure Node.js daemon across different editors and CLI environments (like Claude Code).
Tasks to accomplish:
- Remove
vscode namespace dependencies from src/managers/SharedTaskStateManager.ts.
- Replace
vscode.Memento with a pure Node.js persistent state storage mechanism (e.g., a file-based JSON store in .optimus/state/ or lightweight local DB).
- Ensure backwards compatibility with current adapters.
🤖 Agent System Metadata:
- Local Blackboard:
.optimus/tasks/task_refactor_shared_task_state.md
- Agent Session ID:
GitHub-Copilot-Session
As a prerequisite for the Async Event-Driven Swarm architecture (see #38), we need to decouple
SharedTaskStateManagerfrom thevscode.Mementodependency.Currently,
SharedTaskStateManagerrelies on VS Code's extension context, which breaks the standard of keeping the underlying MCP server as a pure Node.js daemon across different editors and CLI environments (like Claude Code).Tasks to accomplish:
vscodenamespace dependencies fromsrc/managers/SharedTaskStateManager.ts.vscode.Mementowith a pure Node.js persistent state storage mechanism (e.g., a file-based JSON store in.optimus/state/or lightweight local DB).🤖 Agent System Metadata:
.optimus/tasks/task_refactor_shared_task_state.mdGitHub-Copilot-Session