Project
Goals, tasks, decisions, risks, milestones, notes, sources, and evidence.
.memory
One file,That capturesmeaning over time
.memory is a portable, SQLite-backed format for context that needs to survive beyond one chat. That needs to store multiple types of media and information. Stored timeline
Local preview. Not security-certified.Your context and memories are complex
Long-lived work outgrows scattered notes, JSON exports, and sidecar files. A .memory file keeps a coherent body of context in one local container, with sensitive payloads encrypted using local key material.
- 01Local-firstNo cloud account required
- 02PortableA documented, self-contained container
- 03AuditableProvenance, history, and verification
Open the file.Explore the memories.
The Memory Reader projects a .memory file into browsable memories, timelines, graphs, relationships, attachments, linked files, search, health, and vault views.
What a .memory file carriesProfile / context / media / stewardship
01Profile
Project, character, agent, story world, or collection
02Context
Typed objects, relationships, provenance, and timeline
03Media
Encrypted attachments, references, and version history
04Stewardship
Audit, lifecycle, retention, and maintenance metadata
Many file types. One structured .memory.
A .memory file organizes text, images, video, voice clips, references, timelines, relationships, preferences, and history inside one portable container. Use it to capture a complete character, a shareable orchestrator, or the preferences that make Kwib feel like yours—without scattering the context across folders and apps.
One format,
endless purposes
Each profile gives its domain a clear vocabulary while retaining the same portable container, integrity model, and local-first workflow.
Character
Identity, voice, backstory, relationships, beliefs, arcs, timeline, and canon.
Agent
Persona, goals, boundaries, tools, permissions, reflections, lessons, and rules.
Story world
Locations, scenes, events, continuity, contradictions, branches, and relationship maps.
Collection
Links between complete Memory files without merging them into one giant container.
Build the orchestrator, character.
Keep the story lore.
A .memory file carries the creative system behind the output, not just the last prompt. Keep canon, media, decisions, and change together as the work grows.
A character with a past
Carry identity, backstory, voice clips, relationships, beliefs, contradictions, and character arcs. Record how they grow, change, and evolve over time.
A story with all its media
Keep scenes, locations, timelines, canon decisions, story images, video, voice performances, and source material connected to the world they belong to.
An orchestrator you can share
Package its persona, goals, tools, permissions, workflows, lessons, and operating rules in a portable file that can move between people and trusted local apps.