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 4d75d04
Browse filesBrowse the repository at this point in the historyBrowse files
**Store project context using remory CLI with --infer false to preserve full detail:**
221
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.
222
+
**Use multi-memory chunking strategy:** Store 5-7 focused memories (800-1,000 chars each) instead of single large memory. This prevents "Failed to generate embedding" errors from exceeding token limits.
# Memory 2: Current Status (Project activity snapshot, ~1,000 chars max)
228
+
# Memory 2: Current Status (Project activity snapshot, ~800-900 chars max)
229
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
230
231
-
# Memory 3: Commit Conventions (If found in CONTRIBUTING.md or AGENTS.md, ~1,200-1,300 chars)
231
+
# Memory 3: Commit Conventions (If found in CONTRIBUTING.md or AGENTS.md, ~800-900 chars)
232
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
233
234
-
# Memory 4: GitHub Issue Workflow (If found in CONTRIBUTING.md or AGENTS.md, ~1,200-1,300 chars)
234
+
# Memory 4: GitHub Issue Workflow (If found in CONTRIBUTING.md or AGENTS.md, ~800-900 chars)
235
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
236
237
-
# Memory 5: PR & Review Process (If found in CONTRIBUTING.md or AGENTS.md, ~1,200-1,300 chars)
237
+
# Memory 5: PR & Review Process (If found in CONTRIBUTING.md or AGENTS.md, ~800-900 chars)
238
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
239
240
-
# Memory 6: Quality Gates & Testing (If found in CONTRIBUTING.md or AGENTS.md, ~1,200-1,300 chars)
240
+
# Memory 6: Quality Gates & Testing (If found in CONTRIBUTING.md or AGENTS.md, ~800-900 chars)
241
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
242
243
-
# Memory 7: Communication & Philosophy (If found in CONTRIBUTING.md or AGENTS.md, ~1,200-1,300 chars)
243
+
# Memory 7: Communication & Philosophy (If found in CONTRIBUTING.md or AGENTS.md, ~800-900 chars)
244
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
245
245
```
246
246
247
247
**CRITICAL:** Use `--infer false` to preserve FULL TEXT without LLM extraction/shortening.
248
248
249
-
**Store comprehensive context using MULTIPLE focused memories (1,200-1,500 chars each):**
249
+
**Store comprehensive context using MULTIPLE focused memories (800-1,000 chars each):**
- Each memory: 1,200-1,500 characters (safely under 256-token embedding limit)
263
+
- Each memory: 800-1,000 characters (safely under 256-token embedding limit with margin)
264
264
- Semantically complete: Each memory understandable independently
265
265
- Topic-focused: One coherent concept per memory
266
266
- Searchable: Use clear topic names for future retrieval
267
267
- Natural boundaries: Split at logical sections, not mid-paragraph
268
268
269
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.
270
+
Remory's embedding model (sentence-transformers/all-MiniLM-L6-v2) enforces 256-token default limit (200-250 tokens safe with margin = 800-1,000 chars). Long texts (2,500+ chars = 600+ tokens) fail with "Failed to generate embedding" errors. Multiple focused memories succeed where single large memory fails.
271
271
272
272
**Why this matters:**
273
273
- ✅ Each memory successfully embeds (under token limits)
@@ -333,7 +333,7 @@ CRITICAL RULES
333
333
- Search memory FIRST with specific semantic queries
334
334
- Store ALL gathered context with `--infer false` to preserve full detail
335
335
- Use detailed, comprehensive descriptions (not summaries)
336
-
- Split large memories into focused chunks (1,200-1,500 chars each)
336
+
- Split large memories into focused chunks (800-1,000 chars each)
337
337
- Verify each memory is semantically complete and independently searchable
Copy file name to clipboardExpand all lines: instructions/memory-and-remory.md
+16-16Lines changed: 16 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -102,7 +102,7 @@ remory list --user-id "$(cat .project-id 2>/dev/null || (uuidgen | tee .project-
102
102
- Integration patterns with other components
103
103
104
104
**Length Considerations:**
105
-
If your memory content exceeds 1,500 characters, split into multiple focused memories:
105
+
If your memory content exceeds 1,000 characters, split into multiple focused memories:
106
106
- One memory for architecture decisions
107
107
- One memory for solutions to specific problem types
108
108
- One memory for testing/linting configuration
@@ -136,17 +136,17 @@ The `--infer false` flag disables auto-consolidation. When enabled, Remory's LLM
136
136
-**Token-to-character ratio:** Approximately 1 token per 4 characters (English)
137
137
138
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
139
+
-**Target:**800-1,000 characters per `remory add` command
140
+
-**Token equivalent:**200-250 tokens (safely under 256-token limit with margin)
141
+
-**Maximum:** Do NOT exceed 1,000 characters in a single memory entry
142
142
-**Consequence of violation:** "Failed to generate embedding" error
143
143
144
144
**Why `--infer false` Doesn't Help:**
145
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
146
147
147
**Chunking Strategy (Required for Long Content):**
148
148
149
-
When storing comprehensive information that exceeds 1,500 characters:
149
+
When storing comprehensive information that exceeds 1,000 characters:
150
150
151
151
1.**Split into focused topic-based memories** instead of one large memory
152
152
2.**Each memory must be semantically complete** (independently understandable)
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
166
167
-
# Memory 2: PR process (~1,300 chars)
167
+
# Memory 2: PR process (~800-900 chars)
168
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
169
170
-
# Memory 3: Quality gates (~1,200 chars)
170
+
# Memory 3: Quality gates (~800-900 chars)
171
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
0 commit comments