「memory」の検索結果

Forget data stored in Cognee memory. Use when the user asks to forget, delete, or remove something from memory (e.g. "forget what we talked about tennis", "delete that from memory"). Finds the documents in the current dataset whose raw content matches what the user wants forgotten and deletes them.

日本語の概要は準備中です。原文の説明を表示しています。

AI knowledge engine - a memory system in 6 lines of code. remember/recall/forget/improve loop, vector + graph search, OpenClaw plugin supported.

日本語の概要は準備中です。原文の説明を表示しています。

Import a memory export from another AI assistant into Claude's memory — conversationally, additively, and with the content treated as data.

日本語の概要は準備中です。原文の説明を表示しています。

Implement persistent memory patterns for AI agents using AgentDB. Includes session memory, long-term storage, pattern learning, and context management. Use when building stateful agents, chat systems, or intelligent assistants.

日本語の概要は準備中です。原文の説明を表示しています。

Maintain the harness memory files (USER.md, MEMORY.md, AGENTS.md) so that long-term knowledge persists across conversations.

日本語の概要は準備中です。原文の説明を表示しています。

Diagnose Kolu client-side performance issues (memory leaks, high GPU, slow interactions) using chrome-devtools MCP + the Debug → Diagnostic info dialog + heap-snapshot analyzers. Triggers on "memory leak", "GPU memory", "tab bloat", "why is kolu slow", "debug performance", "zombie canvas", "WebGL leak", or any

日本語の概要は準備中です。原文の説明を表示しています。

Run a Meta-Harness-style optimization loop NATIVELY — automatically search over the scaffolding around a FIXED base model (memory, retrieval, context construction, prompt templates, summarization, tool-selection logic) by proposing candidate variants, scoring each on a cheap deterministic eval, and keeping a Pareto frontier of quality vs cost — using native Agent / Workflow / loop tools instead of a standalone Python harness. Use this whenever the user wants to optimize, evolve, tune, distill, or search over a harness, scaffold, prompt system, memory or retrieval policy, context-assembly code, or summarizer while keeping the model fixed; whenever they mention Meta-Harness, harness optimization, scaffold evolution, automatic prompt/memory optimization, an evolutionary or Pareto search over candidate implementations, or "make the harness/agent better without retraining"; and whenever the gain must come from the code AROUND the model rather than the model weights. Reproduces the Meta-Harness paper's method natively, with no claude_wrapper.py and no metered solver API.

日本語の概要は準備中です。原文の説明を表示しています。

Expert guide for long-term episodic memory integration (Mem0 v2, Letta/MemGPT, Zep v2), memory tier architecture, pgvector HNSW storage, and unified context management for autonomous AI agents / Panduan ahli untuk integrasi memori episodik jangka panjang (Mem0 v2, Letta/MemGPT, Zep v2), arsitektur tier memori, penyimpanan pgvector HNSW, dan manajemen konteks terpadu untuk agen AI otonom.

日本語の概要は準備中です。原文の説明を表示しています。

Implement persistent memory patterns for AI agents using AgentDB. Includes session memory, long-term storage, pattern learning, and context management. Use when building stateful agents, chat systems, or intelligent assistants.

日本語の概要は準備中です。原文の説明を表示しています。

Use AddressSanitizer to detect memory safety bugs in C/C++ programs. Identifies use-after-free, buffer overflow, memory leaks, and other memory errors.

日本語の概要は準備中です。原文の説明を表示しています。

Persistent Obsidian-based memory for coding agents. Use at session start to orient from a knowledge vault, during work to look up architecture/component/pattern notes, and when discoveries are made to write them back. Activate when the user mentions obsidian memory, obsidian vault, obsidian notes, or /obs commands. Provides commands: init, analyze, recap, project, note, todo, lookup, relate.

日本語の概要は準備中です。原文の説明を表示しています。

Implement persistent memory patterns for AI agents using AgentDB. Includes session memory, long-term storage, pattern learning, and context management. Use when building stateful agents, chat systems, or intelligent assistants.

日本語の概要は準備中です。原文の説明を表示しています。

Set up Claude Tag for oncall for a team, from that team's standing (public) oncall / monitoring channel. Two things: it sets the channel up for monitoring, so alerts and incident posts here (from a person or another Slack bot) get triaged and acted on automatically, and it finds and sets up the connectors, plugins and skills Claude uses for oncall. A workspace can have several such channels; run once in each, by anyone, and every run adds or updates that team's section in the one oncall memory in shared workspace memory. Use on "set up oncall", "init oncall", "configure Claude for on-call". Surveys the agent connectors an admin configured for Claude, proves one with a read-only pull so access is verified, explores tools, Slack, repos and docs to learn how oncall works here, then recommends what's missing and walks the team through setup. The result goes into the indexed oncall memory every channel reuses; the other skills (incident init, investigation, handoff) pick it up automatically.

日本語の概要は準備中です。原文の説明を表示しています。

Semantic search over global agent memory. Use to retrieve previously learned patterns, decisions, gotchas, and workarounds. Prevents stale-context errors across long sessions and multi-agent pipelines.

日本語の概要は準備中です。原文の説明を表示しています。

Entity and relation tracking skill using MCP memory server patterns and local knowledge graph storage. Build persistent knowledge graphs of entities, relationships, and observations across agent sessions. Covers the MCP memory server (@modelcontextprotocol/server-memory), local JSON-based graphs, and entity-relation querying patterns for long-running agents.

日本語の概要は準備中です。原文の説明を表示しています。

Use when you need semantic retrieval from perpetual memory at query time. Parses query intent, searches vector store, ranks by relevance and recency, and injects context. Complements memory-search.cjs with the perpetual_memory LanceDB table.

日本語の概要は準備中です。原文の説明を表示しています。

Reflective Memory. Use when working with memory, reflection, context management, or intent tracking. Provides the reflective memory practice — how and when to use keep tools for capturing insights, tracking commitments, and maintaining awareness.

日本語の概要は準備中です。原文の説明を表示しています。

Generates a structured Project Brief — a comprehensive markdown document that extracts goals, architecture, knowledge file inventory, Custom Instructions summary, Memory contents, current state, ecosystem position, and key decisions from a Claude Project. Briefs serve as uploadable context documents: add one to any other Project for immediate deep awareness of the source Project's purpose, architecture, and progress. Use when user says "create a brief," "brief this project," "extract project context," "generate a project summary for another project," "I need to share this project's context," "prepare this project for cross-project reference," or "document this project." Also use when the user is preparing to work across Projects and needs portable context. Do NOT use for session handoffs, project audits, or Memory optimization (use rootnode-session-handoff, rootnode-project-audit, or rootnode-memory-optimization respectively, if available).

日本語の概要は準備中です。原文の説明を表示しています。

Use when analyzing warp divergence, memory coalescing, shared memory bank conflicts, cache behavior, atomics, or occupancy tradeoffs on NVIDIA and AMD GPUs. Not for tool commands: use cuda-profiling.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a human asks to audit memory, find stale or duplicate memories, or needs tidy's ICM-state audit. Not for writing new memories: use memory-update.

日本語の概要は準備中です。原文の説明を表示しています。

Decide what to PERSIST in your data structures (graph nodes, DB tables, cache layouts) based on the QUERIES you must answer, not the DEFINITIONS that justify the data. Definitions tell you logical identity; storage strategy is independent. Materializing every definitional component leads to O(N×M) blow-ups that masquerade as memory leaks. Use when: (1) designing a new graph-node type, edge type, DB table, or cache layout; (2) about to name a `subgraph` / `comprises` / `members` / `contains` collection on a parent entity; (3) memory growth proportional to (entities × per-entity-elements); (4) "memory leak" debugging that survives multiple targeted patches — the leak may be storage shape, not retention; (5) pre-implementation sketch includes "for each X, store all reached nodes"; (6) research/spec doc says "X = ⟨A, B, C⟩" and you're tempted to make it three storage edges per X.

日本語の概要は準備中です。原文の説明を表示しています。

Turn travel or lifestyle photos into 4:5 memory-diary pages pairing real photography with a watercolor and colored-pencil interpretation of the same moment. Use for editorial memory archives and photo-illustration diaries.

日本語の概要は準備中です。原文の説明を表示しています。

Design AI memory systems with context management. TRIGGERS - Use when user needs help with ai-memory-system related tasks.

日本語の概要は準備中です。原文の説明を表示しています。

Design memory systems for AI agents. TRIGGERS - Use when user needs help with ai-agent-memory related tasks.

日本語の概要は準備中です。原文の説明を表示しています。