[LogosDB] Add memory management commands (/delete, /list)
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 55/100
Research direction
Start with issue #8 and LogosDB v0.2.0, then read tools/cli/cli.cpp for command parsing and handling and SPECS.md for CLI behavior. Trace how logosdb_put() and logosdb_search() are used, including semantic_memory_options and session caching. Done means /delete, /forget, /list, and /stats meet the listed acceptance criteria, including confirmation, pagination, ID storage, and deleted-row handling.
Written by the indexing model from the issue text.
Description
Add CLI commands to manage stored memories using new LogosDB v0.2.0 delete/update APIs.
Proposed Commands
/delete
Delete memories matching a search query.
Example flow:
Found 2 matches:
[1] id=42 "My commute is 30 minutes"
[2] id=43 "My commute takes 30 minutes"
Delete which? (comma-separated IDs, or all): 42,43
Deleted 2 memories.
/forget
Delete by exact ID for scripting purposes.
/list or /memories
Show memory statistics and recent entries with pagination.
/stats
Quick statistics: live memories, deleted, total count.
Implementation Notes
- Store IDs returned from logosdb_put() in session cache
- Use logosdb_search() to find candidates for deletion
- Confirm before bulk deletion
- Update semantic_memory_options to track ID mappings
Acceptance Criteria
- /delete command with confirmation
- /forget direct deletion command
- /list command with pagination
- /stats quick stats command
- Store IDs when teaching (cache or metadata file)
- Handle deleted rows in search (auto-filtered by LogosDB)
Dependencies
- Requires LogosDB v0.2.0 (issue #8)
Related Files
- tools/cli/cli.cpp - command parsing and handling
- SPECS.md - CLI documentation
- Dominant language
- C++
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from jose-compu/funes.cpp
-
stale
Difficulty 5/5 Over a week Newbie friendliness 25/100
jose-compu/funes.cpp#12 ·
-
stale
Difficulty 4/5 3-5 days Newbie friendliness 52/100
jose-compu/funes.cpp#11 ·
-
stale
Difficulty 4/5 3-5 days Newbie friendliness 48/100
jose-compu/funes.cpp#10 ·
-
stale
Difficulty 4/5 3-5 days Newbie friendliness 45/100
jose-compu/funes.cpp#8 ·
-
stale
Difficulty 4/5 3-5 days Newbie friendliness 48/100
jose-compu/funes.cpp#7 ·
All issues in jose-compu/funes.cpp
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
tesseract-ocr/tesseract#4627 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
lxqt/lxqt-panel#2492 ·
-
bug-unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
[models/demos/gemma4 dFlash]: _shard_argmax returns a view of a force-freed tensor when rows == 1Opencommunity
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
tenstorrent/tt-metal#57989 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100