Daemon Workspace Remember — Sessionless Memory Ingestion

Status: Proposed — implementation in PR #5884 (branch codex/sessionless-daemon-remember), not yet merged.

1. Problem Statement

The daemon's managed-memory system (auto-extraction, dream agent) previously required an active chat session to write memories. This created two problems:

1. Settings UI cannot write memories — the web-shell settings panel needs to save user-provided facts (e.g. "always use TypeScript strict mode") without creating or polluting a visible chat session.
2. Session list pollution — creating a throwaway session just to run a /remember command adds noise to the session list and confuses users who see ghost sessions they never opened.

The solution is a sessionless workspace-level remember endpoint that queues memory-write tasks, executes them via a hidden AgentHeadless fork (no session created), and exposes status via polling.

2. Design Overview

┌──────────────┐  POST /workspace/memory/remember   ┌─────────────────────────┐
│  SDK / UI    │ ─────────────────────────────────►  │  workspace-remember.ts  │
│  client      │                                     │  (WorkspaceRemember-    │
│              │  GET  /workspace/memory/remember/:id │   TaskLane)             │
│              │ ─────────────────────────────────►  │                         │
└──────────────┘                                     └────────────┬────────────┘
                                                                  │ bridge.runWorkspaceMemoryRemember()
                                                     ┌────────────▼────────────┐
                                                     │  HttpAcpBridge          │
                                                     │  extMethod(             │
                                                     │    'qwen/control/       │
                                                     │     workspace/memory/   │
                                                     │     remember')          │
                                                     └────────────┬────────────┘
                                                                  │ ACP stdio (JSON-RPC)
                                                     ┌────────────▼────────────┐
                                                     │  qwen --acp child       │
                                                     │  (QwenAgent.extMethod)  │
                                                     │  → runManagedRemember-  │
                                                     │    ByAgent (forked)     │
                                                     └─────────────────────────┘

Key properties:

• No session required — the bridge ensures the ACP child is spawned but does not create/load/resume any ACP session.
• Serial execution — tasks execute one at a time via a promise-chain lane, preventing concurrent writes to the managed memory filesystem.
• Hidden — the forked agent runs with name: 'managed-auto-memory-remember' and is invisible to the session list.
• Capability-advertised — workspace_memory_remember in the daemon's /capabilities response, with supported modes: ['workspace', 'clean'].

3. API Endpoints

3.1 POST /workspace/memory/remember

Queue a new remember task.

Request:

{
  "content": "The user prefers dark mode in all editors",
  "contextMode": "workspace"
}

Headers:

• Authorization: Bearer <token> (required)
• X-Qwen-Client-Id: <clientId> (optional — scopes task visibility)

Response 202 Accepted:

{
  "taskId": "remember-a1b2c3d4-...",
  "status": "queued",
  "contextMode": "workspace",
  "createdAt": "2026-06-01T12:00:00.000Z",
  "updatedAt": "2026-06-01T12:00:00.000Z"
}

Error responses:

3.2 GET /workspace/memory/remember/:taskId

Poll task status.

Headers:

• Authorization: Bearer <token> (required)
• X-Qwen-Client-Id: <clientId> (optional — must match originator to see task)

Response 200 OK (queued/running):

{
  "taskId": "remember-a1b2c3d4-...",
  "status": "queued",
  "contextMode": "workspace",
  "createdAt": "2026-06-01T12:00:00.000Z",
  "updatedAt": "2026-06-01T12:00:00.000Z",
  "result": null,
  "error": null
}

• status will be "queued" or "running" depending on whether the task has started execution.
• result: only present (non-null) when status === "completed".
• error: only present (non-null) when status === "failed".

Response 200 OK (completed):

{
  "taskId": "remember-a1b2c3d4-...",
  "status": "completed",
  "contextMode": "workspace",
  "createdAt": "2026-06-01T12:00:00.000Z",
  "updatedAt": "2026-06-01T12:00:05.000Z",
  "result": {
    "summary": "Saved dark-mode preference to user memory.",
    "filesTouched": ["~/.qwen/memories/user/user.md"],
    "touchedScopes": ["user"]
  }
}

Response 200 OK (failed):

{
  "taskId": "remember-a1b2c3d4-...",
  "status": "failed",
  "contextMode": "workspace",
  "createdAt": "2026-06-01T12:00:00.000Z",
  "updatedAt": "2026-06-01T12:00:03.000Z",
  "error": {
    "code": "remember_path_escape",
    "message": "Remember agent touched a path outside managed memory."
  }
}

Error responses:

4. Task Lifecycle

            enqueue()
               │
               ▼
  ┌─────────────────────┐
  │       queued         │   (awaiting serial lane slot)
  └──────────┬──────────┘
             │  lane picks up
             ▼
  ┌─────────────────────┐
  │       running        │   (bridge.runWorkspaceMemoryRemember in progress)
  └──────────┬──────────┘
             │
     ┌───────┴────────┐
     ▼                ▼
┌──────────┐    ┌──────────┐
│ completed│    │  failed  │
└──────────┘    └──────────┘

• queued — task is created and waiting in the serial lane.
• running — the bridge call is in flight; the forked agent is executing.
• completed — agent finished successfully; result is populated.
• failed — agent threw or timed out; error is populated.

The lane stores up to 1000 tasks total (terminal tasks evicted FIFO when the cap is reached). At most 16 tasks may be pending (queued + running) at any time.

5. Implementation Details

5.1 Serial Task Lane (WorkspaceRememberTaskLane)

Located in packages/cli/src/serve/workspace-remember.ts. Maintains a Map<taskId, TaskRecord> and a single promise chain (this.tail). Each enqueue() appends a run function that:

1. Sets status to running.
2. Calls bridge.runWorkspaceMemoryRemember({ content, contextMode }).
3. On success: sets status to completed, populates result, publishes memory_changed event.
4. On failure: sets status to failed, populates error with a stable public error code.

The lane guarantees strict serialization — only one remember task executes at a time, preventing concurrent filesystem writes to managed memory.

5.2 Bridge Layer (HttpAcpBridge)

Two methods added to BridgeInterface (packages/acp-bridge/src/bridgeTypes.ts):

• isWorkspaceMemoryRememberAvailable() — calls qwen/control/workspace/memory/remember/availability ext-method on the child. Returns boolean. Used for fast-fail 409 before queuing.
• runWorkspaceMemoryRemember(request) — calls qwen/control/workspace/memory/remember ext-method. Times out at 300 s (WORKSPACE_MEMORY_REMEMBER_TIMEOUT_MS). Does NOT create or load a session.

Both methods call ensureChannel() (spawning the ACP child if needed) and restart the idle timer afterwards if no sessions are active.

5.3 ACP Child Execution (QwenAgent.extMethod)

In packages/cli/src/acp-integration/acpAgent.ts, the handler for workspaceMemoryRemember:

1. Validates content (non-empty string, ≤64 KiB) and contextMode.
2. Checks config.isManagedMemoryAvailable().
3. Calls runManagedRememberByAgent() with a 295 s abort signal (WORKSPACE_MEMORY_REMEMBER_CHILD_TIMEOUT_MS — slightly less than the bridge timeout to ensure the child aborts before the bridge backstop).

5.4 Core Remember Logic (packages/core/src/memory/remember.ts)

runManagedRememberByAgent():

1. Builds a clean memory system prompt from the project's managed memory index.
2. Optionally strips prior user memory (if contextMode === 'clean').
3. Creates a memoryScopedAgentConfig that restricts file I/O to memory directories only.
4. Runs a forked headless agent (runForkedAgent) with:
   • Name: managed-auto-memory-remember
   • Tools: read_file, grep, ls, write_file, edit
   • Max turns: 6
   • Max time: 5 minutes
5. Validates that all touched files are within allowed memory paths (classifyTouchedScopes). Throws remember_path_escape if the agent wrote outside memory directories.
6. Rebuilds memory indexes for any touched scopes.
7. Returns { summary, filesTouched, touchedScopes }.

5.5 Memory-Scoped Agent Config (packages/core/src/memory/memory-scoped-agent-config.ts)

createMemoryScopedAgentConfig() creates a permission-restricted Config wrapper that:

• Write tools (write_file, edit): only allowed within the project auto-memory root or user memory root (~/.qwen/memories).
• Read tools (read_file, grep, ls): when restrictReadsToMemoryPaths is true, only allowed within memory directories.
• Shell: disabled by default; if enabled, only read-only commands allowed.
• Resolves symlinks to prevent path-traversal escapes.

6. Events

memory_changed (scope: managed)

Published on the daemon SSE event stream (GET /session/:id/events) as a memory_changed event with scope: 'managed' when a remember task completes successfully. Clients subscribed to the per-session event stream receive this notification.

Payload:

{
  "type": "memory_changed",
  "data": {
    "scope": "managed",
    "source": "workspace_memory_remember",
    "taskId": "remember-a1b2c3d4-...",
    "touchedScopes": ["user", "project"]
  }
}

The originatorClientId (if provided at POST time) is attached to the event envelope so the event bus can route it to the originating client.

7. Error Handling

Error Codes

Timeout Chain

Agent forked runner:   5 min maxTimeMinutes
Child abort signal:  295 s  (WORKSPACE_MEMORY_REMEMBER_CHILD_TIMEOUT_MS)
Bridge timeout:      300 s  (WORKSPACE_MEMORY_REMEMBER_TIMEOUT_MS)

The child aborts before the bridge times out, ensuring a clean error propagates rather than a transport-level timeout.

8. SDK Integration

TypeScript SDK (@qwen-code/sdk-typescript)

Two new methods on DaemonClient:

// Queue a remember task
const task = await client.rememberWorkspaceMemory(
  'The project uses pnpm workspaces',
  { contextMode: 'workspace' },
);
// task.taskId, task.status === 'queued'

// Poll until terminal
const result = await client.getWorkspaceMemoryRememberTask(task.taskId);
// result.status === 'completed' | 'failed'

UI Event Normalization

The SDK normalizer maps the raw memory_changed SSE event (with scope: 'managed') to a DaemonUiWorkspaceMemoryChangedEvent:

{
  type: 'workspace.memory.changed',
  scope: 'managed',
  source: 'workspace_memory_remember',
  taskId: 'remember-...',
  touchedScopes: ['user', 'project']
}

This extends the existing workspace.memory.changed event type, which previously only carried scope: 'workspace' | 'global' for file-based QWEN.md writes.

9. Design Rationale

Why sessionless?

The /remember slash command in the CLI already works within a session. But the Settings UI and programmatic SDK callers should not need to create a session just to persist a fact. A session implies conversation history, turn tracking, and visibility in the session list — none of which apply to a fire-and-forget memory write.

Why serial execution?

The managed memory system stores facts in markdown files with indexes. Concurrent writes from multiple remember tasks could corrupt indexes or produce merge conflicts. A single-threaded lane is the simplest correct solution.

Why a task queue (not synchronous)?

Memory writes involve an LLM agent deciding where and how to store the fact (choosing between user vs. project scope, picking the right file, formatting). This takes 2–30 seconds. A synchronous HTTP request would either time out or block the client. The async queue + poll pattern keeps the HTTP contract simple and lets clients show progress UI.

Why contextMode?

• "workspace" (default) — the remember agent sees existing memories as context, enabling it to deduplicate or update existing entries.
• "clean" — the agent sees no prior user memory, useful when the caller wants to force a fresh write without dedup logic (e.g. bulk import).

Why restrict reads to memory paths?

The remember agent should only read/write within managed memory directories. This prevents a prompt-injection scenario where crafted content tricks the agent into reading sensitive project files and leaking them into memory entries.