Skip to content

feat: add knowledge.enabled option to disable LTM system#23

Merged
BYK merged 1 commit intomainfrom
feat/knowledge-enabled-option
Mar 2, 2026
Merged

feat: add knowledge.enabled option to disable LTM system#23
BYK merged 1 commit intomainfrom
feat/knowledge-enabled-option

Conversation

@BYK
Copy link
Owner

@BYK BYK commented Mar 2, 2026

Summary

Adds a knowledge.enabled config option (default: true) in .lore.json that disables the entire long-term knowledge subsystem while keeping conversation recall and context management fully active.

This addresses feedback from users who prefer manual context management but still want the conversation search capabilities.

When knowledge.enabled: false:

  • ❌ Curator (knowledge extraction) — skipped
  • ❌ Knowledge injection into system prompt — skipped
  • ❌ AGENTS.md import/export — skipped
  • ❌ Oversized entry pruning — skipped
  • ✅ Temporal storage — active
  • ✅ Distillation — active
  • ✅ Gradient context manager — active
  • ✅ Recall tool (temporal + distillation search) — active
  • ✅ Overflow auto-recovery — active

Config example

{ "knowledge": { "enabled": false } }

Changes

  • src/config.ts — Added knowledge section with enabled boolean
  • src/index.ts — Guarded 6 knowledge code paths with cfg.knowledge.enabled
  • src/reflect.ts — Added knowledgeEnabled parameter, skips ltm.search() when false
  • test/config.test.ts — 4 new tests for schema + load behavior
  • README.md — New Configuration section documenting all .lore.json options

Add a `knowledge.enabled` config option (default: true) in .lore.json
that disables the entire long-term knowledge subsystem while keeping
conversation recall and context management fully active.

When `knowledge.enabled: false`:
- Curator (knowledge extraction) is skipped
- Knowledge injection into system prompt is skipped
- AGENTS.md import/export is skipped
- Oversized entry pruning is skipped
- Recall tool still works for temporal search and distillation search,
  but skips the knowledge DB search

When `knowledge.enabled: true` (default — no behavior change):
- Everything works as before

This addresses feedback from users who prefer manual context management
but still want the conversation search capabilities via the recall tool.

Config example:
  { "knowledge": { "enabled": false } }
@BYK BYK enabled auto-merge (squash) March 2, 2026 11:51
@BYK BYK merged commit 7c6b367 into main Mar 2, 2026
1 check passed
@BYK BYK deleted the feat/knowledge-enabled-option branch March 2, 2026 11:51
@craft-deployer craft-deployer bot mentioned this pull request Mar 2, 2026
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant