Home/ Stark Dev AI/ Memory & Notes

// persistent_memory

Lux remembers
everything.

Cross-session memory and structured notes mean Lux knows your preferences, client context, and project details before you say a word — every single time you open a conversation.

Persistent cross-session memory Notes CRUD from chat Context injection Preference tracking
memory.load → session context
// memory.preference injected
Dustin prefers concise responses with code examples first. Dislikes long preambles. Always use British spelling for formal docs.
Stored: 14 days ago · Updated: 2 days ago
// memory.project
Active project: Buckeye NW Realty — ListingBridges v2 integration. Phase 3 (auto-sync) in progress. Deadline: end of month.
Stored: 6 days ago
// memory.context
Stark Dev AI Plugin: v22.91.7. Current focus: mobile TTS improvements. Known issue: realtime reconnect on iOS Safari.
Stored: 3 days ago · Auto-updated

NOTES_ACTION commands

// from chat
CREATE

Create a new note

"Start a note called 'Sprint 4 Goals' and add the items we just discussed"

APPEND

Add to an existing note

"Add this bug to the ListingBridges known issues note"

OVERWRITE

Replace a note's content

"Rewrite the Buckeye integration notes with the updated scope"

RENAME

Rename a note

"Rename 'Sprint 3' to 'Sprint 3 - Completed'"

// how memory enters every session
01
Session opens — conversation begins
02
memory.load() — fetches stored entries
03
System prompt injection — memories + active notes prepended before first turn
04
Lux responds — already aware of your preferences, projects, and context
05
New memories written — Lux stores relevant context from the session

// capabilities

What persistent memory enables

Memory turns a stateless AI into a collaborator that knows your workflow — no re-explaining, no context dump at the start of every chat.

// cross_session

Cross-session persistence

Memories survive between conversations. Open a new chat three weeks later and Lux already knows your preferred response style, active projects, and running context.

// auto_store

Automatic memory creation

Lux identifies things worth remembering — your timezone, coding preferences, client names — and stores them without being asked. The system prompt grows smarter over time.

// notes_crud

Notes from conversation

Create, append, overwrite, and rename notes entirely through chat. "Add that to the ListingBridges note" is all it takes — no context switching, no copy-paste.

// context_inject

System prompt injection

Memories and active notes are prepended directly to the system prompt before each session. Lux doesn't retrieve them mid-conversation — they're already there when she wakes up.

// selective

Selective recall

You can ask Lux what she remembers, request a specific memory, or tell her to forget something. Full transparency into what's persisted, with conversational controls to manage it.

// toolcall

TOOLCALL-native

Memory reads and writes are TOOLCALL operations — the same architecture as time tracking and CRM. Notes changes fire as NOTES_ACTION commands, logged and reversible.

// persistent_memory

She already knows. That's the point.

No briefing document. No copy-pasting last session's context. Lux picks up exactly where you left off.

// Lux memory connects with

💬 Chat Interface — context injection
🗂️ CRM — client context persistence
📋 Boards — project state memory
🎮 Arcade — pregame carry-forward