Releases: Noshkoto/Noshy
Releases · Noshkoto/Noshy
Release list
v0.4.0
Full Changelog: v0.3.0...v0.4.0
v0.3.0
v0.2.3
v0.2.2
v0.2.1
v0.2.0
What's Changed
- feat: memoir recall, TTL expiry, delete/feedback tools, threaded HTTP by @Noshkoto in #2
- feat: semantic memoir search, auto-decay, real consolidation, web dashboard by @Noshkoto in #3
- feat: @noshy.remember decorator, LLM importance, streaming extraction, project isolation by @Noshkoto in #4
- feat: cluster consolidation, HTTP auth, CLI polish, Docker, integration tests by @Noshkoto in #5
- feat: PyPI release flow, polished dashboard, streaming MCP tool by @Noshkoto in #6
Full Changelog: v0.1.1...v0.2.0
v0.1.1 — Bugfix Pass
What's new
Critical fixes from the first contributor PR:
Bugs squashed:
- LLM importance scoring was silently dropped — a one-letter typo (
importancesvsimportance) meant every memory got stored at default importance regardless of what the LLM scored it - sqlite-vec vector extension was never actually loaded — called
vec_version()beforeload_extension(), so semantic search was always falling back to slow cosine similarity - recall_semantic SQL was generating invalid queries from a string-replace hack, producing broken JOINs
- Semantic recall mode was passing empty bytes instead of embedding the user's query
Reliability:
import_icmnow handles missing optional columns gracefully — no more crashes on legacy ICM databases- All timestamps are timezone-aware now (replaced deprecated
datetime.utcnow()) - HTTP API returns proper 400/404/500 status codes with Content-Length
- MCP stdio server handles notifications and shutdown protocol correctly
- New
/healthendpoint for monitoring
Cleanup:
- All residual 'aion' references removed from README and install paths
- install.sh fixed to use correct tarball path
How to update
If you cloned the repo:
cd ~/.noshy/src && git pullIf you used the install script:
curl -fsSL https://raw.githubusercontent.com/Noshkoto/Noshy/main/install.sh | shThen restart your MCP client or Hermes gateway.
First release with community contributions. The typo fix alone is worth the update — your importance scores actually work now.