# Latest

**URL:** https://community.goodmem.ai/latest.md

[Latest](https://community.goodmem.ai/latest.md) · [Categories](https://community.goodmem.ai/categories.md) · [Tags](https://community.goodmem.ai/tags.md)

---

## [Welcome to GoodMem! 👋](https://community.goodmem.ai/t/welcome-to-goodmem/5)

<div class="topic-metadata">

**Author:** [@system](https://community.goodmem.ai/u/system)\
**Replies:** 4\
**Last updated:** [September 1, 2026, 12:32am UTC](https://community.goodmem.ai/t/welcome-to-goodmem/5 "2026-09-01T00:32:47Z")

</div>

thanks for stopping by! you can use this forum for all things related to goodmem. you can ask for support, showcase your work, make feature requests, document issues, or just chat about goodmem. feel free to leave a co…

---

## [GoodMem 1.0.336 brings resilient background ingestion and a major security refresh](https://community.goodmem.ai/t/goodmem-1-0-336-brings-resilient-background-ingestion-and-a-major-security-refresh/189)

<div class="topic-metadata">

**Author:** [@amin](https://community.goodmem.ai/u/amin)\
**Replies:** 0\
**Last updated:** [October 30, 2026, 7:06pm UTC](https://community.goodmem.ai/t/goodmem-1-0-336-brings-resilient-background-ingestion-and-a-major-security-refresh/189 "2026-10-30T19:06:53Z")

</div>

Over the past two weeks, we’ve improved GoodMem’s ingestion reliability, resolved a substantial set of dependency vulnerabilities, and expanded model and SDK support. The latest server release is 1.0.336. Background i…

---

## [OpenTelemetry trace export arrives in GoodMem 1.0.324](https://community.goodmem.ai/t/opentelemetry-trace-export-arrives-in-goodmem-1-0-324/166)

<div class="topic-metadata">

**Author:** [@amin](https://community.goodmem.ai/u/amin)\
**Replies:** 0\
**Last updated:** [October 1, 2026, 6:17pm UTC](https://community.goodmem.ai/t/opentelemetry-trace-export-arrives-in-goodmem-1-0-324/166 "2026-10-01T18:17:14Z")

</div>

GoodMem 1.0.324 is out, and the server now exports OpenTelemetry traces. Each API request becomes a trace, with spans underneath it for the retrieval stages, the provider calls, and any background job attempts the reques…

---

## [Find the retrieval pipeline that works best for your data](https://community.goodmem.ai/t/find-the-retrieval-pipeline-that-works-best-for-your-data/150)

<div class="topic-metadata">

**Author:** [@kanav](https://community.goodmem.ai/u/kanav)\
**Replies:** 3\
**Last updated:** [September 24, 2026, 6:11pm UTC](https://community.goodmem.ai/t/find-the-retrieval-pipeline-that-works-best-for-your-data/150 "2026-09-24T18:11:05Z")

</div>

Hi everyone — we’re introducing Retrieval Pipeline Optimization, a new way to compare retrieval setups directly against your own data. Choosing an embedding model or reranker is rarely one-size-fits-all. A setup that pe…

---

## [Authorization arrives in GoodMem 1.0.307](https://community.goodmem.ai/t/authorization-arrives-in-goodmem-1-0-307/114)

<div class="topic-metadata">

**Author:** [@amin](https://community.goodmem.ai/u/amin)\
**Replies:** 5\
**Last updated:** [August 26, 2026, 2:24am UTC](https://community.goodmem.ai/t/authorization-arrives-in-goodmem-1-0-307/114 "2026-08-26T02:24:07Z")

</div>

GoodMem 1.0.307 is out, and with it the largest change since launch: a real authorization model. Until now an instance was effectively single-operator, one root key with full access to everything. That constraint is gone…

---

## [Self-service GoodMem version upgrades](https://community.goodmem.ai/t/self-service-goodmem-version-upgrades/121)

<div class="topic-metadata">

**Author:** [@Tom](https://community.goodmem.ai/u/Tom)\
**Replies:** 1\
**Last updated:** [August 20, 2026, 5:03pm UTC](https://community.goodmem.ai/t/self-service-goodmem-version-upgrades/121 "2026-08-20T17:03:27Z")

</div>

GoodMem version and self-service upgrade Every GoodMem card shows the build it is running. When a newer build exists, the card offers it — and the upgrade lands only when you choose to take it. These are captures of the…

---

## [Retrieve calls all returned 400 until I fixed my request body (query vs message); anything else like this I should check?](https://community.goodmem.ai/t/retrieve-calls-all-returned-400-until-i-fixed-my-request-body-query-vs-message-anything-else-like-this-i-should-check/116)

<div class="topic-metadata">

**Author:** [@draymond](https://community.goodmem.ai/u/draymond)\
**Replies:** 1\
**Last updated:** [August 19, 2026, 11:38pm UTC](https://community.goodmem.ai/t/retrieve-calls-all-returned-400-until-i-fixed-my-request-body-query-vs-message-anything-else-like-this-i-should-check/116 "2026-08-19T23:38:59Z")

</div>

Sharing this in case it’s useful to someone else, and so someone can tell me if I’m still holding it wrong. I’ve got four agents running on separate VMs, each doing Gmail ingestion into its own GoodMem space and then se…

---

## [Llama.cpp as LLM still requires API key](https://community.goodmem.ai/t/llama-cpp-as-llm-still-requires-api-key/45)

<div class="topic-metadata">

**Author:** [@ruoyunhuang](https://community.goodmem.ai/u/ruoyunhuang)\
**Replies:** 3\
**Last updated:** [June 17, 2026, 5:27pm UTC](https://community.goodmem.ai/t/llama-cpp-as-llm-still-requires-api-key/45 "2026-06-17T17:27:29Z")

</div>

Hey, folks, was trying to use a local llama.cpp endpoint, then it still requires an API key otherwise won’t proceed. Using a dummy api key didn’t work. Likely a bug in the setup page?
