Repository navigation
v0.24.0
AgentCrew 0.24.0
This release makes SQLite the default memory backend, adds a safer migration path for existing Chroma data, and improves memory capture, retrieval, and application lifecycle management.
Highlights
- SQLite and FTS5 are now the default memory backend. Existing Chroma memory can be migrated through an interactive startup prompt or with the new
agentcrew-migrate-memorycommand. The Chroma source is preserved during migration. - Chroma is optional. Install it with
uv sync --extra chromadborpip install "agentcrew-ai[chromadb]"if you want to use the Chroma backend. - Memory now tracks accessed-resource provenance. Successful file, webpage, MCP resource, and attachment accesses can be associated with stored memories. Resource capture records locators, not file contents.
- Memory extraction is more robust. It now uses bounded, validated structured output, retries recoverable failures, preserves prior memory details, and provides privacy-conscious diagnostics.
- Added Memopad candidate collection for SQLite. Use
/memopad statsto view local aggregate counts. Memopad items remain untrusted candidates and are not injected into agent context. - Improved memory search workflows. Search supports result limits, kinds, opaque memory IDs, and summary, evidence, and full-record detail. Guidance helps agents ground detailed answers in successfully hydrated records and citations.
Other improvements
- Added
/statsreporting for instantiated LLM service roles and conversation usage. - Added lightweight model selection for memory extraction, tool summaries, and code analysis; refreshed built-in provider catalogs and defaults.
- Improved tool-result summary redaction and reuse of ready summaries as bounded memory evidence.
- Improved A2A, ACP, job, and interactive console async lifecycle handling and resource cleanup.
- Improved MCP OAuth callback handling so unrelated or duplicate requests cannot overwrite the first valid result.
- Expanded code-analysis cache discovery to include nested projects, with bounded results and symlink protections.
Upgrade notes
- Existing Chroma users should review the migration prompt and back up their data before proceeding. Migration uses
uvx, runs in the foreground, and requires stopping memory writers. - The default engine is now SQLite. To keep using Chroma, install the optional extra and set
global_settings.memory_engineto"chromadb"inconfig.json. - Noninteractive startup does not prompt to migrate; it preserves Chroma data and starts with a fresh SQLite store. See CONFIGURATION.md for recovery guidance.