local-memory-protocol

Store and retrieve repository-associated context in local JSONL files.

Updated May 17, 2026

Search Tags:#project context #decision tracking #workflow recovery #session summaries #local memory #observations jsonl #codex discipline

Ready to run

npx skills add https://github.com/cheetah-alo/NegritaOS --skill local-memory-protocol

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: local-memory-protocol
Source: https://github.com/cheetah-alo/NegritaOS/tree/main/.codex/skills/memory-protocol
Command: npx skills add https://github.com/cheetah-alo/NegritaOS --skill local-memory-protocol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents loss of crucial project context by defining a consistent, repository-aware discipline for storing and retrieving durable notes, decisions, and session outcomes.

Core Features & Use Cases

Persistent local memory without external services: keeps durable knowledge under ~/.negritaos/memory/ so it survives branch changes, worktrees, and .codex churn.
Project-scoped recall and continuity: routes search through a project index.md, session summaries, observations, and task state for reliable recovery.
Quality-gated saving rules: stores only durable information (decisions, bugfix causes, discoveries, constraints, preferences) as compact JSONL observations.

Quick Start

Use local-memory-protocol when you want to remember or recover prior work for a specific project by updating the project index.md and appending a new observation in ~/.negritaos/memory/projects/<project_id>/observations.jsonl.

Frequently Asked Questions about local-memory-protocol

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I preserve project context across sessions after context loss or compaction?▼

To preserve project context, durable discoveries, decisions, and session outcomes are stored locally as compact JSONL observations under `~/.negritaos/memory/`, ensuring workflow recovery after context loss or compaction.

What is the best way to track project decisions and bugfixes locally without external services?▼

Tracking project decisions locally without external services is achieved by enforcing append-only observation logging and quality-gated saving rules for durable knowledge like bugfix causes and constraints within a local memory directory.

How do I recover prior work and session state for a specific repository?▼

Recovering prior work for a specific repository is done by routing search through a project `index.md` and session summaries, allowing reliable continuity and workflow recovery across branch changes and worktrees.

Does local memory storage work with Codex workflows and branch changes?▼

Yes, local memory storage works with Codex workflows by surviving branch changes, worktrees, and `.codex` churn, applying structured save, close, and recovery rules to maintain session continuity.

What type of project context should be saved as observations in JSONL format?▼

Only durable information such as decisions, bugfix causes, discoveries, constraints, and preferences should be saved as observations in JSONL format, avoiding transient data to maintain a reliable project index.