Previous value: -"Optional multilingual hypothetical answer or dense semantic expansion written by the calling LLM for this query."New value: +"Optional hypothetical answer or semantic expansion of the query, used to improve matching."

Previous value: -"Optional query intent: 'topic' (default) or 'activity_log'. Trigger: Set 'activity_log' for event feeds within a bounded [since, until) window; set 'topic' for topic retrieval. Model responsibility: 'activity_log' requires explicit bounded 'since' and 'until' timestamps. Consequence: 'activity_log' without bounds fails closed; explicit 'topic' blocks stream bypass."New value: +"Optional query intent: 'topic' (default) or 'activity_log'. Set 'activity_log' for event feeds within a bounded [since, until) window; set 'topic' for topic retrieval. 'activity_log' requires explicit bounded 'since' and 'until' timestamps. 'activity_log' without bounds fails closed; explicit 'topic' blocks stream bypass."

Previous value: -"RFC 3339 timestamp with timezone offset (e.g., '2026-09-01T00:00:00+09:00'). Trigger: Call this whenever the user query mentions any relative or absolute time constraint in any language (e.g., today, yesterday, last week, last month, recently, Aug 1, Aug 10 to Sep 1, since Monday, before Sep 15, in Q3). Model responsibility: You (the calling LLM) know current date and user local time, so you must convert natural language time expressions into absolute timestamps. Consequence: If omitted, the server falls back to heuristic guessing which may misinterpret timezone day boundaries or relative dates."New value: +"RFC 3339 timestamp with timezone offset (e.g., '2026-09-01T00:00:00+09:00'). Set this whenever the user query mentions any relative or absolute time constraint in any language (e.g., today, yesterday, last week, last month, recently, Aug 1, Aug 10 to Sep 1, since Monday, before Sep 15, in Q3). Relative and natural language time expressions are given as absolute timestamps in the user's local time. If omitted, the server falls back to heuristic guessing which may misinterpret timezone day boundaries or relative dates."

Previous value: -"Sort order for returned memories: 'desc' (newest first) or 'asc' (oldest first). Trigger: Pass 'desc' when the user asks for 'latest', 'recent', 'newest first', or recency, or 'asc' for chronological order ('oldest first') in any language. Model responsibility: Explicitly set desired temporal ordering when the user expresses recency intent. If omitted and since/until are omitted, default relevance ranking is used without temporal sorting."New value: +"Sort order for returned memories: 'desc' (newest first) or 'asc' (oldest first). Set 'desc' when the user asks for 'latest', 'recent', 'newest first', or recency, or 'asc' for chronological order ('oldest first') in any language. If omitted and since/until are omitted, default relevance ranking is used without temporal sorting."

Previous value: -"RFC 3339 timestamp with timezone offset (e.g., '2026-09-02T00:00:00+09:00'). When used with since, defines the half-open interval [since, until) with until > since (maximum 90 days span). Trigger: Pass when the user query specifies an end date or bounded window in any language (e.g., yesterday end of day, by Aug 10, Aug 10 to Sep 1). Model responsibility: Convert natural language end bounds into absolute timestamps with timezone offsets. Consequence: If omitted, the window is open-ended on the upper side or derived heuristically."New value: +"RFC 3339 timestamp with timezone offset (e.g., '2026-09-02T00:00:00+09:00'). When used with since, defines the half-open interval [since, until) with until > since (maximum 90 days span). Set this when the user query specifies an end date or bounded window in any language (e.g., yesterday end of day, by Aug 10, Aug 10 to Sep 1). Natural language end bounds are given as absolute timestamps with timezone offsets. If omitted, the window is open-ended on the upper side or derived heuristically."

Added value: +{
+  "default": "%",
+  "description": "Bucket of your own memories to search; % (default) searches all buckets. An explicit bucket is never widened by fallback.",
+  "title": "Bucket",
+  "type": "string"
+}

Previous value: -"Input value for the Recall tool."New value: +"Optional multilingual hypothetical answer or dense semantic expansion written by the calling LLM for this query."

Previous value: -"Input value for the Recall tool."New value: +"Optional temporal axis resolution policy: 'created_at' (Scheme A), 'updated_at' (Scheme B), or 'split_filter_created_order_updated' (Scheme C)."

Removed value: -false

Added value: +{
+  "default": "",
+  "description": "Optional client-supplied agent label for memory attribution.",
+  "title": "Agent Id",
+  "type": "string"
+}

Added value: +{
+  "default": "",
+  "description": "Optional stable, non-secret agent instance ID for per-client attribution.",
+  "title": "Agent Instance Id",
+  "type": "string"
+}

Added value: +{
+  "default": false,
+  "description": "Whether to include retrieval explanation details with search or recall results.",
+  "title": "Explain",
+  "type": "boolean"
+}

Added value: +{
+  "default": "%",
+  "description": "Memory type/category filter or value, such as episodic, identity, procedural, semantic, working, auto, or %.",
+  "title": "Memory Type",
+  "type": "string"
+}

Added value: +{
+  "default": "",
+  "description": "The user's real IANA timezone, such as Asia/Tokyo or America/Los_Angeles. Required for honest calendar periods; never guess UTC.",
+  "title": "Owner Timezone",
+  "type": "string"
+}

Added value: +{
+  "default": "%",
+  "description": "Memory path filter; % matches all paths.",
+  "title": "Path Filter",
+  "type": "string"
+}

Added value: +{
+  "default": false,
+  "description": "Whether to prioritize working/session-state memories in retrieval.",
+  "title": "Prefer Working",
+  "type": "boolean"
+}

Added value: +{
+  "default": "",
+  "description": "Optional ISO 8601 reference time snapshot for deterministic evaluation. Leave blank to use the real clock; setting this does not replace owner_timezone for calendar day boundaries.",
+  "title": "Reference Time",
+  "type": "string"
+}

Added value: +{
+  "default": "",
+  "description": "Input value for the Recall tool.",
+  "title": "Temporal Axis Mode",
+  "type": "string"
+}

Previous value: -"RFC 3339 timestamp with timezone offset (e.g., '2026-09-01T00:00:00+09:00'). Trigger: Call this whenever the user query mentions any relative or absolute time constraint (今天/今日/昨天/昨日/前天/上周/8月1日/8月10日到9月1日/最近...). Model responsibility: You (the calling LLM) know current date and user local time, so you must convert natural language time expressions into absolute timestamps. Consequence: If omitted, the server falls back to heuristic guessing which may misinterpret timezone day boundaries or relative dates."New value: +"RFC 3339 timestamp with timezone offset (e.g., '2026-09-01T00:00:00+09:00'). Trigger: Call this whenever the user query mentions any relative or absolute time constraint in any language (e.g., today, yesterday, last week, last month, recently, Aug 1, Aug 10 to Sep 1, since Monday, before Sep 15, in Q3). Model responsibility: You (the calling LLM) know current date and user local time, so you must convert natural language time expressions into absolute timestamps. Consequence: If omitted, the server falls back to heuristic guessing which may misinterpret timezone day boundaries or relative dates."

Previous value: -"Sort order for returned memories: 'desc' (newest first) or 'asc' (oldest first). Trigger: Pass 'desc' when the user asks for 'latest', 'recent', '从新到旧', or timeline recency, or 'asc' for chronological order. Model responsibility: Explicitly set desired temporal ordering when the user expresses recency intent. If omitted and since/until are omitted, default relevance ranking is used without temporal sorting."New value: +"Sort order for returned memories: 'desc' (newest first) or 'asc' (oldest first). Trigger: Pass 'desc' when the user asks for 'latest', 'recent', 'newest first', or recency, or 'asc' for chronological order ('oldest first') in any language. Model responsibility: Explicitly set desired temporal ordering when the user expresses recency intent. If omitted and since/until are omitted, default relevance ranking is used without temporal sorting."

Previous value: -"RFC 3339 timestamp with timezone offset (e.g., '2026-09-02T00:00:00+09:00'). When used with since, defines the half-open interval [since, until) with until > since (maximum 90 days span). Trigger: Pass when the user query specifies an end date or bounded window (e.g., 昨天 end of day, 截至8月10日, 8月10日到9月1日). Model responsibility: Convert natural language end bounds into absolute timestamps with timezone offsets. Consequence: If omitted, the window is open-ended on the upper side or derived heuristically."New value: +"RFC 3339 timestamp with timezone offset (e.g., '2026-09-02T00:00:00+09:00'). When used with since, defines the half-open interval [since, until) with until > since (maximum 90 days span). Trigger: Pass when the user query specifies an end date or bounded window in any language (e.g., yesterday end of day, by Aug 10, Aug 10 to Sep 1). Model responsibility: Convert natural language end bounds into absolute timestamps with timezone offsets. Consequence: If omitted, the window is open-ended on the upper side or derived heuristically."

Added value: +{
+  "default": "",
+  "description": "Input value for the Recall tool.",
+  "title": "Hypothetical Answer",
+  "type": "string"
+}

Added value: +{
+  "default": "",
+  "description": "Optional query intent: 'topic' (default) or 'activity_log'. Trigger: Set 'activity_log' for event feeds within a bounded [since, until) window; set 'topic' for topic retrieval. Model responsibility: 'activity_log' requires explicit bounded 'since' and 'until' timestamps. Consequence: 'activity_log' without bounds fails closed; explicit 'topic' blocks stream bypass.",
+  "title": "Query Mode",
+  "type": "string"
+}

Added value: +{
+  "default": "",
+  "description": "RFC 3339 timestamp with timezone offset (e.g., '2026-09-01T00:00:00+09:00'). Trigger: Call this whenever the user query mentions any relative or absolute time constraint (今天/今日/昨天/昨日/前天/上周/8月1日/8月10日到9月1日/最近...). Model responsibility: You (the calling LLM) know current date and user local time, so you must convert natural language time expressions into absolute timestamps. Consequence: If omitted, the server falls back to heuristic guessing which may misinterpret timezone day boundaries or relative dates.",
+  "title": "Since",
+  "type": "string"
+}

Added value: +{
+  "default": "",
+  "description": "Sort order for returned memories: 'desc' (newest first) or 'asc' (oldest first). Trigger: Pass 'desc' when the user asks for 'latest', 'recent', '从新到旧', or timeline recency, or 'asc' for chronological order. Model responsibility: Explicitly set desired temporal ordering when the user expresses recency intent. If omitted and since/until are omitted, default relevance ranking is used without temporal sorting.",
+  "title": "Time Order",
+  "type": "string"
+}

Added value: +{
+  "default": "",
+  "description": "RFC 3339 timestamp with timezone offset (e.g., '2026-09-02T00:00:00+09:00'). When used with since, defines the half-open interval [since, until) with until > since (maximum 90 days span). Trigger: Pass when the user query specifies an end date or bounded window (e.g., 昨天 end of day, 截至8月10日, 8月10日到9月1日). Model responsibility: Convert natural language end bounds into absolute timestamps with timezone offsets. Consequence: If omitted, the window is open-ended on the upper side or derived heuristically.",
+  "title": "Until",
+  "type": "string"
+}

Added value: +false

Removed value: -{
-  "default": "",
-  "description": "Optional client-supplied agent label for memory attribution.",
-  "title": "Agent Id",
-  "type": "string"
-}

Removed value: -{
-  "default": "",
-  "description": "Optional stable, non-secret agent instance ID for per-client attribution.",
-  "title": "Agent Instance Id",
-  "type": "string"
-}

Removed value: -{
-  "default": false,
-  "description": "Whether to include retrieval explanation details with search or recall results.",
-  "title": "Explain",
-  "type": "boolean"
-}

Removed value: -{
-  "default": "%",
-  "description": "Memory type/category filter or value, such as episodic, identity, procedural, semantic, working, auto, or %.",
-  "title": "Memory Type",
-  "type": "string"
-}

Removed value: -{
-  "default": "%",
-  "description": "Memory path filter; % matches all paths.",
-  "title": "Path Filter",
-  "type": "string"
-}

Removed value: -{
-  "default": false,
-  "description": "Whether to prioritize working/session-state memories in retrieval.",
-  "title": "Prefer Working",
-  "type": "boolean"
-}