Results for “pe”

Persistent per-project memory for Claude Code. Auto-loads project context on session start, tracks sessions with git activity, and writes to native memory. Commands run deterministic Node.js scripts — behavior is consistent across model versions.

Routes requests into the correct obsidian-mind mode: install, daily session loop, capture, review, maintenance, multi-agent wiring, or semantic search, using a ready-made Obsidian vault template for persistent agent memory.

Creates, reads, deletes, and lists memos on a Memos instance via its API, using a personal access token.

Logs daily development progress per project, fuses entries into a global diary, and syncs to Notion/Obsidian.

Stores, retrieves, and curates persistent facts in a structured memory map, distinguishing between user facts and reference text.

Transforms lessons learned into domain-organized memory instructions that persist across VS Code contexts, with global and workspace scopes.

Maintains a PARA-structured knowledge base on disk for persistent project context, decisions, and architecture records across agent sessions.

Organize research by managing references, notes, and collaboration across Google Drive, Docs, Sheets, and Gmail.

Logs daily development progress per project, fuses entries into a global diary, and syncs to Notion and Obsidian.

Maintains a working memory file for AI agents, tracking active goals, completed tasks, performance metrics, blockers, and key decisions across sessions.

Draft, organize, and distribute content across Google Workspace using Docs, Drive, Gmail, and Chat.

Build and maintain a persistent, interlinked markdown knowledge base that compiles knowledge once and keeps it current, with cross-references and contradiction flags.

Search and retrieve past work from claude-mem's persistent cross-session memory database using a three-layer workflow: search, timeline, and fetch.

Routes user intents to the right operation for a persistent Markdown second brain, enforcing citation and discussion before any write, with read-only MCP tools for queries.

Arquiva briefs, peças e aprendizados de campanhas no Obsidian (pasta local) e no Notion (via MCP), usando links e estrutura de pastas para reuso futuro.

Generate a serial, multi-chapter narrative digest of a project's claude-mem history, producing one digest per ISO week with coherent story flow across chapters.

Establishes a three-layer knowledge distillation architecture for an Obsidian-based wiki, defining categories, projects, page templates, and operational workflows for maintaining a persistent knowledge base.

Maintains a persistent session memory across Claude sessions by loading project state at startup, capturing errors and decisions during work, and writing structured handoff summaries at session end.

Names content by three coordinates: millisecond timestamp, SHA-256 hash, and optional human petname. Verifies content integrity, timestamps events, and maintains a local content store searchable by time, hash, or human words.

Turns any long-running domain (business, relationships, health, career, learning, investing) into a local knowledge project with four layers, source tags, immutable snapshots, and a concept library that learns patterns over time.