You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit acb7317
Browse filesBrowse the repository at this point in the historyBrowse files
**Store project context using remory CLI with --infer false to preserve full detail:**
197
221
222
+
**Use multi-memory chunking strategy:** Store 5-7 focused memories (1,200-1,500 chars each) instead of single large memory. This prevents "Failed to generate embedding" errors from exceeding token limits.
223
+
198
224
```bash
199
-
# Store project overview (DETAILED - preserve everything from README)
200
-
remory add "Project: {name} - {full description from README including all key features}. Stack: {complete technology stack with versions}. Purpose: {main purpose and goals}. Key features: {list main features}" --user-id "$PROJECT_ID" --infer false
201
-
```
202
-
```bash
203
-
# Store architecture insights (DETAILED - preserve all patterns and decisions)
204
-
remory add "Architecture: {detailed architectural patterns from docs}. Design decisions: {all key decisions with rationale}. Components: {component structure and interactions}. Data flow: {how data flows through system}" --user-id "$PROJECT_ID" --infer false
205
-
```
206
-
```bash
207
-
# Store current status (DETAILED - preserve activity context)
208
-
remory add "Status: {X} open issues, {Y} open PRs. Recent commits: {detailed recent activity from git log including commit messages}. CI/CD: {current CI state and any issues}" --user-id "$PROJECT_ID" --infer false
209
-
```
210
-
```bash
211
-
# Store workflow and conventions (DETAILED - preserve COMPLETE workflow information)
212
-
remory add "Project workflow: {commit message format, PR process, review requirements, branch naming, communication style from CONTRIBUTING.md OR AGENTS.md - whichever exists}. Coding standards: {complete coding standards from docs}. Testing requirements: {all testing requirements including coverage targets}. Quality gates: {all quality gates that must pass}. Contribution guidelines: {all contribution rules and conventions}" --user-id "$PROJECT_ID" --infer false
# Memory 2: Current Status (Project activity snapshot, ~1,000 chars max)
229
+
remory add "Status: {X} open issues, {Y} open PRs. Recent commits: {recent activity from git log with commit messages}. CI/CD: {current CI state}. Active work: {current focus areas}." --user-id "$PROJECT_ID" --infer false
230
+
231
+
# Memory 3: Commit Conventions (If found in CONTRIBUTING.md or AGENTS.md, ~1,200-1,300 chars)
232
+
remory add "Commit standards and conventions. Use Conventional Commits format: type(scope): description. Types: feat, fix, docs, style, refactor, test, chore, build, ci, perf. Include GitHub issue reference: 'feat: add auth (#123)'. Always atomic changes. Clear descriptions. Present tense, imperative mood. First line <50 chars. Examples from project docs: {examples from CONTRIBUTING/AGENTS}." --user-id "$PROJECT_ID" --infer false
233
+
234
+
# Memory 4: GitHub Issue Workflow (If found in CONTRIBUTING.md or AGENTS.md, ~1,200-1,300 chars)
235
+
remory add "GitHub issue workflow and quality template. Every development issue requirements: {list checkboxes from docs - TDD, coverage, linting, etc.}. Validate issue content with 'gh issue view'. All work matches issue exactly. Refuse work not listed. Update issue before expanding scope. Complete only when all checkboxes done. {Additional workflow details from docs}." --user-id "$PROJECT_ID" --infer false
236
+
237
+
# Memory 5: PR & Review Process (If found in CONTRIBUTING.md or AGENTS.md, ~1,200-1,300 chars)
238
+
remory add "Pull request and CI verification process. Feature branch workflow: {branch naming conventions from docs}. PR requirements: {title format, description requirements}. Review process: {approval requirements, self-merge policy}. CI verification: {commands used - gh run watch, monitoring requirements}. Merge strategy: {squash/merge/rebase from docs}." --user-id "$PROJECT_ID" --infer false
239
+
240
+
# Memory 6: Quality Gates & Testing (If found in CONTRIBUTING.md or AGENTS.md, ~1,200-1,300 chars)
241
+
remory add "Quality gates and testing requirements. Zero-tolerance policy: {suppression rules from docs}. Coverage requirements: {thresholds - 80%+, per-file vs overall}. Linting: {commands and requirements}. Type checking: {requirements}. Testing approach: {TDD requirements, test patterns, mocking strategies from docs}. Local verification: {what must pass before completion}." --user-id "$PROJECT_ID" --infer false
242
+
243
+
# Memory 7: Communication & Philosophy (If found in CONTRIBUTING.md or AGENTS.md, ~1,200-1,300 chars)
244
+
remory add "Communication style and development philosophy. Tone: {professional, concise, etc. from docs}. Minimalist principles: {LESS IS MORE, challenge necessity, etc. from docs}. Code quality: {standards from docs}. Documentation: {when to create, approval requirements}." --user-id "$PROJECT_ID" --infer false
213
245
```
214
246
215
247
**CRITICAL:** Use `--infer false` to preserve FULL TEXT without LLM extraction/shortening.
216
248
217
-
**What to store (be COMPREHENSIVE):**
218
-
- Project overview: name, complete description, full technology stack with versions, purpose, key features
219
-
-**Workflow (CRITICAL)**: commit message format, PR process, review requirements, branch naming, communication style from CONTRIBUTING.md or AGENTS.md (whichever exists)
220
-
- Architecture: all patterns, all design decisions with rationale, component structure, data flow
221
-
- Current status: open issues, PRs, detailed recent commits, CI/CD state
222
-
- Conventions: complete coding standards, all testing requirements, all quality gates
223
-
- Recent learnings: detailed solutions found, patterns discovered, decisions made with context
224
-
-**Everything important for future sessions** - be thorough, not summary!
249
+
**Store comprehensive context using MULTIPLE focused memories (1,200-1,500 chars each):**
- Each memory: 1,200-1,500 characters (safely under 256-token embedding limit)
264
+
- Semantically complete: Each memory understandable independently
265
+
- Topic-focused: One coherent concept per memory
266
+
- Searchable: Use clear topic names for future retrieval
267
+
- Natural boundaries: Split at logical sections, not mid-paragraph
268
+
269
+
**Why Chunking:**
270
+
Remory's embedding model (sentence-transformers/all-MiniLM-L6-v2) has 256-token default limit (~1,000 chars). Long texts (2,500+ chars) fail with "Failed to generate embedding" errors. Multiple focused memories succeed where single large memory fails.
225
271
226
272
**Why this matters:**
227
-
- Future sessions get FULL context immediately, not extracted facts
228
-
- Prevents repeating research and discovery
229
-
- Builds institutional knowledge across sessions with full detail
230
-
- Enables continuity and consistency
273
+
- ✅ Each memory successfully embeds (under token limits)
274
+
- ✅ Semantically searchable across separate memories
275
+
- ✅ Future agents find relevant concepts easily
276
+
- ✅ Easier to update individual topics
277
+
- ✅ Reduces cognitive load (focused topics vs sprawling docs)
278
+
- ✅ Prevents embedding failures that block session initialization
-**Token-to-character ratio:** Approximately 1 token per 4 characters (English)
137
+
138
+
**Safe Memory Size Guidelines:**
139
+
-**Target:** 1,200-1,500 characters per `remory add` command
140
+
-**Token equivalent:** 300-375 tokens (safely under 256-token default with margin)
141
+
-**Maximum:** Do NOT exceed 1,500 characters in a single memory entry
142
+
-**Consequence of violation:** "Failed to generate embedding" error
143
+
144
+
**Why `--infer false` Doesn't Help:**
145
+
The `--infer false` flag disables LLM-powered consolidation (happens AFTER embedding). Token limits are enforced DURING embedding (BEFORE consolidation). If embedding fails due to length, consolidation never runs.
146
+
147
+
**Chunking Strategy (Required for Long Content):**
148
+
149
+
When storing comprehensive information that exceeds 1,500 characters:
150
+
151
+
1.**Split into focused topic-based memories** instead of one large memory
152
+
2.**Each memory must be semantically complete** (independently understandable)
153
+
3.**Use natural boundaries:** Split at logical sections, not mid-paragraph
154
+
4.**Topic naming:** Use clear, searchable topic names
155
+
156
+
**Example - WRONG (Will Fail):**
157
+
```bash
158
+
# Single memory with 2,500+ characters - FAILS with "Failed to generate embedding"
remory add "Commit standards and conventions. Use Conventional Commits format: type(scope): description. Types: feat, fix, docs, refactor, test. Include issue reference. Examples: 'feat: add auth (#123)'. Present tense, imperative mood. First line <50 chars." --user-id "$(cat .project-id 2>/dev/null || (uuidgen | tee .project-id))" --infer false
166
+
167
+
# Memory 2: PR process (~1,300 chars)
168
+
remory add "Pull request workflow. Feature branch naming: feature/123-description. PR requirements: title format, description, CI green. Review process: mandatory approval, no self-merge. Merge strategy: squash. CI monitoring: gh run watch for real-time." --user-id "$(cat .project-id 2>/dev/null || (uuidgen | tee .project-id))" --infer false
169
+
170
+
# Memory 3: Quality gates (~1,200 chars)
171
+
remory add "Zero-tolerance quality enforcement. Never suppress linting (no # noqa, # type: ignore). Coverage: 80%+ per file, CI enforces. Testing: TDD required, tests before implementation. Local verification: run all tests, all linting, type checking before completion." --user-id "$(cat .project-id 2>/dev/null || (uuidgen | tee .project-id))" --infer false
172
+
```
173
+
174
+
**Benefits of Multi-Memory Approach:**
175
+
- ✅ Each memory successfully embeds (under token limits)
176
+
- ✅ Semantically searchable across separate memories
177
+
- ✅ Easier to update individual topics without affecting others
178
+
- ✅ Future agents can search specific topics and get focused results
179
+
- ✅ Reduces cognitive load (focused topics vs sprawling documents)
0 commit comments