Repository navigation
docs(env): name the Agent SDK route and correct the fallback and cap comments - #1675
Merged
Merged
Conversation
…comments - The header and section 1 name AGENTMEMORY_ALLOW_AGENT_SDK=true as the second way session content can reach an LLM. - FALLBACK_PROVIDERS is ignored when zero-LLM is active, which includes the Agent SDK case the old wording got wrong. - MAX_OBS_PER_SESSION is a hard per-session cap; later observations are refused, and only capture-worker refusals are parked as dead letters.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
Caution Review failedThe pull request is closed.
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. |
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
rohitg00
added a commit
that referenced
this pull request
Nov 4, 2026
rohitg00
added a commit
that referenced
this pull request
Nov 4, 2026
* chore: prepare 0.9.32 Bump the version to 0.9.32 across the package, plugin manifests, integrations, the MCP shim and its runtime pin, the export version union and supported import versions. Add the 0.9.32 CHANGELOG section and README highlights, and sync documented counts with docs:sync. * docs(changelog): add the fixes merged after the 0.9.32 draft Adds #1665, #1605, #1362 and #1675 to the 0.9.32 Fixed section and merges main so the release branch carries them. * docs(agents): count the REST endpoint added by #1605
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Applies the three
.env.examplecomment fixes that review threads asked for..env.exampleships in the npm package, so these land before 0.9.32.AGENTMEMORY_ALLOW_AGENT_SDK=trueas the second way session content can reach an LLM. The old text said onlyAGENTMEMORY_LLM_PROVIDERorEMBEDDING_PROVIDERcould.FALLBACK_PROVIDERS(from fix(plugin): address the directory review on data capture, providers and listing #1664's review): ignored when zero-LLM is active. The old wording, "ignored when no provider is chosen", was wrong when the Agent SDK fallback is on.MAX_OBS_PER_SESSION(from docs(env): correct the MAX_OBS_PER_SESSION comment #1503's review): a hard per-session cap. Later observations are refused, and only capture-worker refusals are parked as dead letters. This covers what docs(env): correct the MAX_OBS_PER_SESSION comment #1503 set out to fix.Comment-only change; no code or defaults change.