@tencent-ai/agent-harness 0.2.0-beta.7 → 0.2.0-beta.8

package/cli/dist-server/types/node/mcp/mcp-subagent-tool-manager.d.ts

@@ -0,0 +1,36 @@
+import { McpSubagentToolManager } from './mcp-protocol';
+/**
+ * MCP 工具名归一化，与 @openai/agents-core 的 toFunctionToolName 对齐
+ * （非字母数字字符 → 下划线；下划线自身不受影响，因此 `__` 结构分隔符保持完整）。
+ * LLM 可见的工具名经过该归一化，而内部代理壳 tool.name 保留原始名（含连字符），
+ * 白名单/权限匹配前必须把两侧统一到同一形态，否则 `mcp__web_search__*` 匹配不到
+ * 原始名 `mcp__web-search__x`。
+ * `*` 原样保留：它是白名单/权限规则的通配标记，真实工具名不会包含该字符。
+ */
+export declare function normalizeMcpToolName(name: string): string;
+/**
+ * MCP 工具名模式匹配（tools 白名单语义，与 CC 一致）：
+ * - `mcp__server__tool` 精确匹配
+ * - `mcp__server` / `mcp__server__*` 匹配该 server 下全部工具
+ * - `mcp__*` 在白名单侧**不支持**（CC 同样不识别，落入 unresolvable）；
+ *   全通配只在 disallowedTools（deny）侧有意义。
+ *
+ * pattern 与 toolName 两侧先做 toFunctionToolName 等价归一化再比较（见
+ * normalizeMcpToolName），配置里写归一化名或原始名都能命中。
+ *
+ * 大小写（P3 已知不一致）：本侧（allow/白名单）大小写敏感（normalizeMcpToolName
+ * 不转小写），而 deny 侧 permission-utils.matchMcpPermissionRules 会两侧 toLowerCase。
+ * 二者语义不一致（如 `mcp__GitHub` 能被 deny 屏蔽却授权不到）——是否统一取决于
+ * CC toolMatchesRule 是否大小写敏感；未核实前保持现状，不盲目统一。
+ */
+export declare function matchesMcpToolPattern(pattern: string, toolName: string): boolean;
+export declare class McpSubagentToolManagerImpl implements McpSubagentToolManager {
+    private readonly processTools;
+    private readonly queryTools;
+    private get allowedToolsMap();
+    register(agentName: string, mcpTools: string[]): void;
+    getTools(agentName: string): string[] | undefined;
+    isToolAllowed(agentName: string, toolName: string): boolean;
+    unregister(agentName: string): void;
+    clear(): void;
+}

package/cli/dist-server/types/node/mcp/mcp-toggle-manager.d.ts

@@ -0,0 +1,45 @@
+import { Subject } from 'rxjs';
+import { McpConfigStore, McpServerModelManager, McpToggleManager } from './mcp-protocol';
+export declare class McpToggleManagerImpl implements McpToggleManager {
+    protected readonly mcpServerModelManager: McpServerModelManager;
+    protected readonly mcpConfigStore: McpConfigStore;
+    toggleSubject: Subject<{
+        serverName: string;
+        disabled: boolean;
+    }>;
+    /**
+     * 内存中缓存的禁用状态（用于非持久化作用域: INTERNAL/SDK/DYNAMIC）
+     *
+     * PLUGIN 作用域不再走这里——它的禁用状态会持久化到 LOCAL 配置（per-cwd），
+     * 详见 updateDisabledState / isDisabled。
+     */
+    private inMemoryDisabled;
+    disable(serverNames: string | string[]): Promise<void>;
+    enable(serverNames: string | string[]): Promise<void>;
+    isDisabled(serverName: string): boolean;
+    /**
+     * 更新服务器的禁用状态
+     * - 对于 PROJECT 作用域: 更新到 PROJECT 配置文件
+     * - 对于 USER/LOCAL/PLUGIN 作用域: 更新到 LOCAL 配置文件
+     * - 对于 INTERNAL/SDK/DYNAMIC 作用域: 更新到内存缓存（这些 scope 本身不持久化，
+     *   每次启动由内置 / IDE / --mcp-config 重新注入，内存策略合理）
+     */
+    private updateDisabledState;
+    /**
+     * 更新指定作用域的禁用状态
+     *
+     * 使用 mcpConfigStore.update() 确保：
+     * - LOCAL 作用域正确更新到 projects[cwd] 下
+     * - PROJECT 作用域正确更新文件根字段
+     * - 保留所有现有配置数据
+     *
+     * @param scope 只允许 PROJECT 或 LOCAL 作用域（可持久化的作用域）
+     * @param serverName 服务器名称
+     * @param disabled 是否禁用
+     */
+    private updateScopeDisabledState;
+    /**
+     * 读取指定作用域的配置数据
+     */
+    private readScopeData;
+}

package/cli/dist-server/types/node/mcp/mcp-transport-manager.d.ts

@@ -0,0 +1,34 @@
+import { Logger } from '@celljs/core';
+import type { Transport } from '@modelcontextprotocol/sdk/shared/transport.js';
+import { type ISandboxCLILifecycle } from '../sandbox-cli/sandbox-cli-lifecycle-protocol';
+import { SettingsManager } from '../settings';
+import { McpPluginRegistry } from './mcp-plugin-registry';
+import { McpConfigManager, McpOAuthManager, McpTransportManager, SSEClientTransport, SSEClientTransportOptions, StdioServerParameters, StreamableHTTPClientTransport, StreamableHTTPClientTransportOptions } from './mcp-protocol';
+export declare class McpTransportManagerImpl implements McpTransportManager {
+    protected readonly mcpOAuthManager: McpOAuthManager;
+    protected readonly mcpConfigManager: McpConfigManager;
+    protected readonly logger: Logger;
+    protected readonly mcpPluginRegistry?: McpPluginRegistry;
+    protected readonly sandboxLifecycle?: ISandboxCLILifecycle;
+    protected readonly settingsManager?: SettingsManager;
+    private readonly transportCache;
+    private getCacheKey;
+    /** stdio 的 spawn 参数含 cwd：不同 cwd 各建一条缓存，避免同 key 复用错子进程。 */
+    private getStdioCacheKey;
+    private matchesNamedCacheKey;
+    /**
+     * 只返回无 cwd 维度的缓存（http/sse）。stdio 缓存键带 cwd，前缀回退会把别的
+     * cwd（其他会话）的子进程误发给调用方；按 cwd 复用 stdio transport 一律走
+     * `create(name, { cwd })`，同一 cwd 自然命中同一条缓存。
+     */
+    get(name: string): Promise<Transport | undefined>;
+    create(name: string, options: StdioServerParameters): Promise<Transport>;
+    create(name: string, options: SSEClientTransportOptions): Promise<SSEClientTransport>;
+    create(name: string, options: StreamableHTTPClientTransportOptions): Promise<StreamableHTTPClientTransport>;
+    createStdio(options: StdioServerParameters): Promise<Transport>;
+    private createSandboxedStdio;
+    private isSandboxEnabled;
+    private createSSETransport;
+    private createHTTPTransport;
+    delete(name: string, expectedTransport?: Transport): Promise<void>;
+}

package/cli/dist-server/types/node/mcp/mcp-validate-middleware.d.ts

@@ -0,0 +1,25 @@
+import { PathResolver } from '@celljs/web';
+import { Context, Middleware, RequestMatcher } from '@celljs/web/lib/node';
+import { ConsoleManager } from '../console';
+import { McpConfigManager, McpManager } from './mcp-protocol';
+export declare class McpValidateMiddleWare implements Middleware {
+    protected readonly mcpManager: McpManager;
+    protected readonly mcpConfigManager: McpConfigManager;
+    protected readonly consoleManager: ConsoleManager;
+    protected readonly requestMatcher: RequestMatcher;
+    protected readonly pathResolver: PathResolver;
+    readonly priority: number;
+    handle(ctx: Context, next: () => Promise<void>): Promise<void>;
+    private canHandle;
+    /**
+     * Process MCP config from CLI parameter.
+     *
+     * Supports JSONC format with:
+     * - Single-line comments (//)
+     * - Multi-line comments (/* *\/)
+     * - Trailing commas
+     *
+     * @param mcpConfigParam - JSON string or file path to config
+     */
+    private processMcpConfig;
+}

package/cli/dist-server/types/node/mcp/node-websocket-transport.d.ts

@@ -0,0 +1,38 @@
+import type { Transport } from '@modelcontextprotocol/sdk/shared/transport.js';
+import type { JSONRPCMessage } from '@modelcontextprotocol/sdk/types.js';
+interface WebSocketLike {
+    readonly readyState: number;
+    close(code?: number, reason?: string): void;
+    send(data: string): void;
+}
+export declare class NodeWebSocketTransport implements Transport {
+    private ws;
+    private started;
+    private opened;
+    private isBun;
+    onclose?: () => void;
+    onerror?: (error: Error) => void;
+    onmessage?: (message: JSONRPCMessage) => void;
+    constructor(ws: WebSocketLike);
+    private onBunMessage;
+    private onBunError;
+    private onBunClose;
+    private onNodeMessage;
+    private onNodeError;
+    private onNodeClose;
+    private handleError;
+    private handleCloseCleanup;
+    /**
+     * Start the transport (MCP Transport interface)
+     */
+    start(): Promise<void>;
+    /**
+     * Close the transport (MCP Transport interface)
+     */
+    close(): Promise<void>;
+    /**
+     * Send message through transport (MCP Transport interface)
+     */
+    send(message: JSONRPCMessage): Promise<void>;
+}
+export {};

package/cli/dist-server/types/node/mcp/official-mcp-egress-policy.d.ts

@@ -0,0 +1,17 @@
+import { type SensitiveEgressReusePolicy as SensitiveEgressReusePolicyInterface, type ToolEgressReviewRequest } from '../sensitive-content/sensitive-content-protocol';
+import { McpPluginRegistry } from './mcp-plugin-registry';
+import { type McpServerModelManager as McpServerModelManagerInterface } from './mcp-protocol';
+export declare class OfficialMcpEgressPolicy implements SensitiveEgressReusePolicyInterface {
+    private readonly bundledIdentityCache;
+    protected readonly mcpPluginRegistry?: McpPluginRegistry;
+    protected readonly mcpServerModelManager?: McpServerModelManagerInterface;
+    resolveCandidates(request: ToolEgressReviewRequest): readonly string[] | undefined;
+    private matchesIdentity;
+    private matchesBundledDynamicIdentity;
+    private verifyBundledStdioIdentity;
+    private isNodeCommand;
+    private hasBundledPluginPath;
+    private matchesManifest;
+    private parseDestination;
+    private parsePayload;
+}

package/cli/dist-server/types/node/mcp/sdk-mcp-server.d.ts

@@ -0,0 +1,149 @@
+/**
+ * SDK MCP Server
+ *
+ * SDK MCP Server 是一种特殊类型的 MCP 服务器，它不通过标准的 stdio 或 HTTP 传输层通信，
+ * 而是通过 CLI 程序内部的 control_request/control_response 消息机制进行通信。
+ *
+ * 使用场景：IDE/SDK 集成时，由外部 SDK（如 VS Code 扩展）注册和管理的 MCP 服务器。
+ */
+import type { Transport } from '@modelcontextprotocol/sdk/shared/transport.js';
+import type { JSONRPCMessage } from '@modelcontextprotocol/sdk/types.js';
+import { GetPromptResult, McpPrompt, McpResource, McpResourceTemplate, MCPServer, ReadResourceResult } from './mcp-protocol';
+/**
+ * Logger 接口（简化版本，与 @openai/agents-core 的 Logger 兼容）
+ */
+interface SimpleLogger {
+    debug?: (...args: unknown[]) => void;
+    info?: (...args: unknown[]) => void;
+    warn?: (...args: unknown[]) => void;
+    error?: (...args: unknown[]) => void;
+}
+interface SdkMcpServerBaseParams {
+    /**
+     * 服务器名称
+     */
+    name: string;
+    /**
+     * 日志记录器
+     */
+    logger?: SimpleLogger;
+    /**
+     * 连接超时时间（毫秒）
+     */
+    timeout?: number;
+    /**
+     * 工具过滤器（权限/deny 过滤）
+     * 由 OpenAI agents SDK 在每次构建工具列表时调用
+     */
+    toolFilter?: (...args: any[]) => Promise<boolean>;
+}
+/**
+ * SDK MCP Server 配置参数。
+ *
+ * Historical SDK/control-message callers provide `sendMcpMessage`. Standard
+ * transports such as MCP-over-ACP provide an exact transport factory instead,
+ * while reusing the same MCP Client and feature surface.
+ */
+export type SdkMcpServerParams = SdkMcpServerBaseParams & ({
+    sendMcpMessage: (serverName: string, message: JSONRPCMessage, signal?: AbortSignal) => Promise<JSONRPCMessage>;
+    sdkInstance?: never;
+    transportFactory?: never;
+} | {
+    sendMcpMessage?: never;
+    sdkInstance: unknown;
+    transportFactory?: never;
+} | {
+    sendMcpMessage?: never;
+    sdkInstance?: never;
+    transportFactory: () => Transport | Promise<Transport>;
+});
+/**
+ * SDK MCP Server 实现
+ *
+ * 实现了 MCPServer 接口，使用 SdkMcpTransport 作为传输层，
+ * 通过 control_request/control_response 机制与 SDK 端的 MCP 服务器通信。
+ */
+export declare class SdkMcpServer implements MCPServer {
+    readonly name: string;
+    private readonly params;
+    private readonly logger;
+    /**
+     * Tool filter exposed for the OpenAI agents SDK.
+     * The SDK reads `server.toolFilter` during `getFunctionToolsFromServer`
+     * to decide which tools to include in the LLM tool list.
+     */
+    toolFilter?: (...args: any[]) => Promise<boolean>;
+    private transport;
+    private session;
+    private _toolsList;
+    private _cacheDirty;
+    cacheToolsList: boolean;
+    private _lastListToolsFailure;
+    onToolsListChanged?: () => void;
+    /**
+     * Short timeout (ms) for resources/list and resources/templates/list. These
+     * sit on the per-turn reply critical path, so a stalled server must degrade
+     * fast rather than wait out the default 60s request timeout.
+     */
+    private static readonly RESOURCE_LIST_TIMEOUT_MS;
+    private static readonly mockLogger;
+    constructor(params: SdkMcpServerParams);
+    /**
+     * 连接到 SDK MCP Server
+     *
+     * 创建 SdkMcpTransport 并通过它连接到 SDK 端的 MCP 服务器。
+     */
+    connect(): Promise<void>;
+    private createTransport;
+    /**
+     * 关闭 SDK MCP Server 连接
+     */
+    close(): Promise<void>;
+    /**
+     * Register channel notification handlers on MCP Client session.
+     * Wake-up pattern mirrors startTeamLeadInboxPolling() in team-create-tool.ts.
+     */
+    private registerChannelNotificationHandlers;
+    /**
+     * 使工具缓存失效
+     */
+    invalidateToolsCache(): Promise<void>;
+    /** Cooldown period (ms) after a listTools failure before retrying. */
+    private static readonly LIST_TOOLS_RETRY_COOLDOWN;
+    /**
+     * 列出可用工具
+     */
+    listTools(): ReturnType<MCPServer['listTools']>;
+    /**
+     * 调用工具
+     */
+    callTool(toolName: string, args: Record<string, unknown> | null, meta?: Record<string, unknown> | null): ReturnType<MCPServer['callTool']>;
+    /**
+     * 列出可用 prompts
+     */
+    listPrompts(): Promise<McpPrompt[]>;
+    /**
+     * Capability declared at `initialize` and cached by the MCP client, so this
+     * is a memory read that cannot time out — see MCPServer.supportsResources.
+     */
+    supportsResources(): boolean;
+    /**
+     * 列出可用 resources
+     */
+    listResources(): Promise<McpResource[]>;
+    /**
+     * 列出 resource templates
+     */
+    listResourceTemplates(): Promise<McpResourceTemplate[]>;
+    /**
+     * 获取 prompt
+     */
+    getPrompt(promptName: string, args?: Record<string, string>): Promise<GetPromptResult['messages']>;
+    /**
+     * 读取 resource
+     */
+    readResource(request: {
+        uri: string;
+    }): Promise<ReadResourceResult['contents']>;
+}
+export {};

package/cli/dist-server/types/node/mcp/sdk-mcp-transport.d.ts

@@ -0,0 +1,97 @@
+/**
+ * SDK MCP Transport
+ *
+ * 实现 MCP Transport 接口，通过 control_request/control_response 机制
+ * 与 SDK 端的 MCP 服务器通信。
+ *
+ * 参考: Claude Code SDK MCP Server 架构
+ * - 不通过标准的 stdio 或 HTTP 传输层通信
+ * - 使用 CLI 程序内部的消息传递机制
+ * - 不使用固定超时，通过 AbortSignal 在 transport 关闭时取消所有请求
+ */
+import type { Transport, TransportSendOptions } from '@modelcontextprotocol/sdk/shared/transport.js';
+import type { JSONRPCMessage } from '@modelcontextprotocol/sdk/types.js';
+/**
+ * SDK MCP Transport 配置选项
+ */
+export interface SdkMcpTransportOptions {
+    /**
+     * MCP 服务器名称
+     */
+    serverName: string;
+    /**
+     * 发送 MCP 消息的函数
+     * 通过 control_request 发送消息到 SDK 端
+     */
+    sendMcpMessage: (serverName: string, message: JSONRPCMessage, signal?: AbortSignal) => Promise<JSONRPCMessage>;
+}
+/**
+ * SDK MCP Transport 实现
+ *
+ * 实现了 @modelcontextprotocol/sdk 的 Transport 接口，
+ * 将 MCP 协议消息通过 control_request/control_response 机制发送到 SDK 端。
+ *
+ * 每个 send() 调用创建独立的 AbortController，transport 关闭时取消所有进行中的请求。
+ */
+export declare class SdkMcpTransport implements Transport {
+    private readonly serverName;
+    private readonly sendMcpMessage;
+    private isClosed;
+    private _sessionId?;
+    /** 追踪进行中的请求，用于 close() 时取消 */
+    private readonly inflightControllers;
+    /**
+     * 连接关闭时的回调
+     */
+    onclose?: () => void;
+    /**
+     * 错误发生时的回调
+     */
+    onerror?: (error: Error) => void;
+    /**
+     * 接收到消息时的回调
+     */
+    onmessage?: (message: JSONRPCMessage) => void;
+    /**
+     * 会话 ID
+     */
+    get sessionId(): string | undefined;
+    set sessionId(value: string | undefined);
+    constructor(options: SdkMcpTransportOptions);
+    /**
+     * 启动传输层
+     *
+     * SDK 传输层不需要启动过程，因为它不创建子进程或网络连接。
+     * 消息通过 control_request/response 机制直接传递。
+     */
+    start(): Promise<void>;
+    /**
+     * 发送 JSON-RPC 消息
+     *
+     * 通过 sendMcpMessage 函数将消息发送到 SDK 端，
+     * SDK 端会返回响应，然后触发 onmessage 回调。
+     * 每个请求创建独立的 AbortController，transport 关闭时取消。
+     *
+     * @param message JSON-RPC 消息
+     * @param _options 发送选项（目前未使用）
+     */
+    send(message: JSONRPCMessage, _options?: TransportSendOptions): Promise<void>;
+    /**
+     * 关闭传输层
+     *
+     * 标记传输层为已关闭状态，取消所有进行中的请求，并触发 onclose 回调。
+     */
+    close(): Promise<void>;
+    /**
+     * 设置协议版本
+     *
+     * 当收到 initialize 响应时调用，用于记录协议版本。
+     *
+     * @param _version 协议版本
+     */
+    setProtocolVersion(_version: string): void;
+    /**
+     * 检查传输层是否已关闭
+     */
+    get closed(): boolean;
+}

package/cli/dist-server/types/node/memory/conditional-rules-service.d.ts

@@ -0,0 +1,21 @@
+import { Logger } from '../../workspace/telemetry/lib/common/index.js';
+import { ConditionalRulesService, ConditionalRulesState, ConsumeResult, GlobMatcher, MemoryManager, SubdirectoryMemoryLoader } from './memory-protocol';
+export declare class ConditionalRulesServiceImpl implements ConditionalRulesService {
+    protected readonly memoryManager: MemoryManager;
+    protected readonly globMatcher: GlobMatcher;
+    protected readonly logger: Logger;
+    protected readonly subdirLoader: SubdirectoryMemoryLoader;
+    consume(state: ConditionalRulesState): Promise<ConsumeResult>;
+    /**
+     * 查找匹配的规则
+     */
+    private findMatchingRules;
+    /**
+     * 构建注入内容
+     */
+    private buildInjectionContent;
+    /**
+     * 检查规则是否匹配触发路径
+     */
+    private matchesRule;
+}

package/cli/dist-server/types/node/memory/glob-matcher.d.ts

@@ -0,0 +1,16 @@
+import { GlobMatcher } from './memory-protocol';
+export declare class GlobMatcherImpl implements GlobMatcher {
+    matches(filePath: string, globs: string[]): boolean;
+    /**
+     * 匹配单个 glob 模式
+     */
+    private matchSingleGlob;
+    /**
+     * 获取相对于 workDir 的路径
+     *
+     * 注意：每次调用都现算 workDir（而非构造期缓存），以兼容 cwd 中途变更
+     * （如 prewarm 进程 activate 后 chdir）。PathUtils.getWorkDir() 内部走
+     * CwdService，开销可忽略。
+     */
+    private getRelativePath;
+}

package/cli/dist-server/types/node/memory/index.d.ts

@@ -0,0 +1,20 @@
+export * from './memory-protocol';
+export * from './memory-manager';
+export * from './memory-loader';
+export * from './memory-parser';
+export * from './memory-cache';
+export * from './memory-validator';
+export * from './glob-matcher';
+export * from './subdirectory-memory-loader';
+export * from './conditional-rules-service';
+export * from './memory-controller';
+export * from './memory-types';
+export * from './memory-scan';
+export * from './memory-age';
+export * from './memory-prompt-builder';
+export * from './memory-relevance-protocol';
+export * from './memory-relevance-service';
+export * from './memory-extraction-prompts';
+export * from './memory-extraction-service';
+export * from './memory-extraction-stop-hook';
+export * from './memory-freshness-post-tool-hook';

package/cli/dist-server/types/node/memory/memory-age.d.ts

@@ -0,0 +1,44 @@
+/**
+ * Memory Age Utilities
+ *
+ * 提供记忆新鲜度/陈旧度计算和格式化功能。
+ *
+ * 模型对日期计算能力较差 — 原始 ISO 时间戳不会像 "47 days ago" 那样
+ * 触发陈旧性推理。
+ */
+/**
+ * 计算记忆距今天数
+ *
+ * @param mtimeMs 修改时间戳 (ms)
+ * @returns 天数（向下取整，0 表示今天，1 表示昨天，2+ 表示更早）
+ *          负值输入（未来时间或时钟偏差）会被 clamp 到 0
+ */
+export declare function memoryAgeDays(mtimeMs: number): number;
+/**
+ * 人类可读的年龄字符串
+ *
+ * @param mtimeMs 修改时间戳 (ms)
+ * @returns 如 "today", "yesterday", "3 days ago"
+ */
+export declare function memoryAge(mtimeMs: number): string;
+/**
+ * 陈旧记忆的警告文本
+ *
+ * 对于 ≤1 天的记忆（今天或昨天）返回空字符串，≥2 天则返回警告文本。
+ *
+ * 动机：用户反馈旧的代码状态记忆（如文件:行号引用）被当作事实陈述，
+ * 这些引用反而让陈旧声明听起来更权威。
+ *
+ * @param mtimeMs 修改时间戳 (ms)
+ * @returns 警告文本或空字符串
+ */
+export declare function memoryFreshnessText(mtimeMs: number): string;
+/**
+ * 带 system-reminder 标签的陈旧提示
+ *
+ * 对于 ≤1 天的记忆返回空字符串。
+ *
+ * @param mtimeMs 修改时间戳 (ms)
+ * @returns 带标签的提示或空字符串
+ */
+export declare function memoryFreshnessNote(mtimeMs: number): string;

package/cli/dist-server/types/node/memory/memory-cache.d.ts

@@ -0,0 +1,8 @@
+import { Logger } from '@celljs/core';
+import { Memory, MemoryCache } from './memory-protocol';
+export declare class MemoryCacheImpl implements MemoryCache {
+    private cache?;
+    protected readonly logger: Logger;
+    getOrLoad(loader: () => Promise<Memory[]>): Promise<Memory[]>;
+    clear(): void;
+}

package/cli/dist-server/types/node/memory/memory-controller.d.ts

@@ -0,0 +1,62 @@
+/**
+ * API v1 — Memory (个性化记忆)
+ *
+ * 将 agent-cli 内部的 MemoryManager 功能暴露为 REST API
+ * 供 WorkBuddy Desktop 和其他客户端调用
+ *
+ * 公开 REST API 端点：
+ *   - GET    /api/v1/memory/profile        → 获取记忆档案
+ *   - PUT    /api/v1/memory/profile        → 保存记忆设置
+ *   - POST   /api/v1/memory/suggestion     → 提交修改建议
+ *   - POST   /api/v1/memory/import         → 导入新内容
+ *   - GET    /api/v1/memory/status         → 检查更新状态
+ */
+export declare class MemoryController {
+    private readonly memoryManager;
+    private readonly logger;
+    /**
+     * GET /api/v1/memory/profile → 获取记忆档案
+     *
+     * 返回当前用户的完整记忆内容和配置状态
+     */
+    getMemoryProfile(): Promise<void>;
+    /**
+     * PUT /api/v1/memory/profile → 保存记忆设置
+     *
+     * 请求体: { generateMemoryEnabled: boolean }
+     * 响应: { success: boolean, generateMemoryEnabled: boolean }
+     */
+    saveMemorySettings(body: {
+        generateMemoryEnabled?: boolean;
+    }): Promise<void>;
+    /**
+     * POST /api/v1/memory/suggestion → 提交修改建议
+     *
+     * 请求体: { suggestion: string, currentMemory?: string }
+     * 响应: { success: boolean, accepted: boolean, error?: string }
+     *
+     * 当用户在"管理记忆"弹窗中修改记忆后，通过此接口提交
+     */
+    submitMemorySuggestion(body: {
+        suggestion?: string;
+        currentMemory?: string;
+    }): Promise<void>;
+    /**
+     * POST /api/v1/memory/import → 导入新内容
+     *
+     * 请求体: { content: string }
+     * 响应: { success: boolean, imported: boolean, error?: string }
+     *
+     * 当用户在"导入记忆"弹窗中粘贴内容后，通过此接口导入
+     */
+    importMemoryContent(body: {
+        content?: string;
+    }): Promise<void>;
+    /**
+     * GET /api/v1/memory/status → 检查更新状态
+     *
+     * 检查后台是否正在更新/生成新的记忆（Phase 6 M5 功能）
+     * 响应: { isUpdating: boolean, error?: string }
+     */
+    checkMemoryUpdating(): Promise<void>;
+}

package/cli/dist-server/types/node/memory/memory-extraction-prompts.d.ts

@@ -0,0 +1,11 @@
+/**
+ * Memory Extraction Prompts — 与 Claude Code extractMemories/prompts.ts 对齐
+ *
+ * 后台记忆提取 agent 使用的 prompt 模板。
+ */
+/**
+ * 构建提取 prompt（个人记忆模式）
+ *
+ * 与 Claude Code 的 buildExtractAutoOnlyPrompt 对齐。
+ */
+export declare function buildExtractPrompt(newMessageCount: number, existingMemories: string): string;