Repository navigation
Align combined Supermemory recall bounds and credits authority - #15
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
No actionable comments were generated in the recent review.
 |
| Layer / File(s) | Summary |
|---|---|
Cross-host recall limits docs/agents/shared-context-and-memory.md |
Recall is limited to one session-start call, two scoped calls, and three combined results or 6,000 retained characters. Windows per-call bounds are specified. Cloud responses may exceed these bounds, and configuration does not establish enforcement or acceptance. |
Routine operation approval docs/agents/shared-context-and-memory.md |
Standing approval requires verified scope, privacy filtering, bounded operations and size, deduplication, and no uncertain retries. Supermemory credits are the only spending limit. The Windows ledger does not meter cloud MCP calls. |
Priority:
Estimated code review effort: 1 (Trivial) | ~4 minutes
Possibly related PRs
- BigSimmo/caring-contacts#14: Established the shared Supermemory routes, namespace checks, privacy filtering, credits-only spending rule, and routine-operation approval policy that this PR updates.
Merge Risk: 
97f06
-
This change aligns the memory recall limits and the standing approval wording with the owner's documented credits-only policy. It has no runtime effect, and no merge-blocking risk remains.
Caution
Pre-merge checks failed
Please resolve all errors before merging. Addressing warnings is optional.
- Ignore
| Check name | Status | Explanation | Resolution |
|---|---|---|---|
| Verification Claims |  |
The PR description includes the verification claim “Normal one-file commit: PASS” but does not name the exact command or check. The other listed results name checks such as `repository_rule_targets.co… | Replace the vague claim with the exact command or check and its result, for example: “Ran <exact commit/check command>: passed.” If it was not run, state “Not run: .” |
-
Check name Status Explanation Title check The title clearly and concisely identifies the main changes: aligning Supermemory recall bounds and credits authority. Description check The description directly explains the recall limits, credits authority, generated-source changes, and verification results described in the changeset. Docstring Coverage No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Documentation-only edits and deletions within survi… Linked Issues check Check skipped because no linked issues were found for this pull request. Out of Scope Changes check Check skipped because no linked issues were found for this pull request. Generated And Sensitive Files PASS — The pull request changes only the tracked documentation file docs/agents/shared-context-and-memory.md. The added text contains policy language, namespace names, and cost limits, but no creden…Risky Git Or Deployment Actions PASS — The pull request changes only memory-recall bounds and approval wording. The diff adds no force-push, hard reset, destructive clean, branch deletion, shared-branch rebase, production-data mutat… Supabase Project And Schema Safety PASS: The PR changes only docs/agents/shared-context-and-memory.md. The diff contains no Supabase project reference, environment setting, migration, schema, RLS, policy, or database change. The chan…Runtime And Package Manager Integrity PASS. The pull request changes only docs/agents/shared-context-and-memory.md. It does not change package manifests,package-lock.json,.nvmrc, or CI. The repository still declares Node 24 and np…Api Route Failure Handling PASS. The pull request changes only documentation in docs/agents/shared-context-and-memory.md. The diff changes memory-recall and spending-policy text. It introduces no API route, server action, RAG…Full details: Docstring Coverage
-
Explanation
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)
Full details: Generated And Sensitive Files
-
Explanation
PASS — The pull request changes only the tracked documentation file
docs/agents/shared-context-and-memory.md. The added text contains policy language, namespace names, and cost limits, but no credentials, tokens, API keys, private keys, real.envfiles, logs, caches, build artifacts, browser artifacts, database dumps, or machine-local configuration.
Full details: Risky Git Or Deployment Actions
-
Explanation
PASS — The pull request changes only memory-recall bounds and approval wording. The diff adds no force-push, hard reset, destructive clean, branch deletion, shared-branch rebase, production-data mutation, or deployment instruction. The standing approval applies to bounded Supermemory memory operations, not production deployment or production data changes. Existing guidance still keeps other billable runs behind explicit approval.
Full details: Supabase Project And Schema Safety
-
Explanation
PASS: The PR changes only
docs/agents/shared-context-and-memory.md. The diff contains no Supabase project reference, environment setting, migration, schema, RLS, policy, or database change. The changed text only updates Supermemory recall and credit guidance.
Full details: Runtime And Package Manager Integrity
-
Explanation
PASS. The pull request changes only
docs/agents/shared-context-and-memory.md. It does not change package manifests,package-lock.json,.nvmrc, or CI. The repository still declares Node 24 and npm 11, and CI still usesnpm ciwith.nvmrc. No package-manager switch, lockfile bypass, engine weakening, or force/legacy resolution flag was introduced.
Full details: Api Route Failure Handling
-
Explanation
PASS. The pull request changes only documentation in
docs/agents/shared-context-and-memory.md. The diff changes memory-recall and spending-policy text. It introduces no API route, server action, RAG, search, ingestion, or provider integration code. The API route failure-handling check is therefore not applicable.
-
Full details: Verification Claims
-
Explanation
The PR description includes the verification claim “Normal one-file commit: PASS” but does not name the exact command or check. The other listed results name checks such as
repository_rule_targets.collect_targets,Prettier ... --check, andgit diff --check; this one does not meet the same requirement.Resolution
Replace the vague claim with the exact command or check and its result, for example: “Ran <exact commit/check command>: passed.” If it was not run, state “Not run: <reason>.”
Finishing Touches
-
✨ Simplify code
-
- Commit to this branch
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Comment @coderabbitai help to get the list of available commands.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Change
Startup recall now uses at most two explicit single-namespace calls and retains at most three combined results/6,000 combined characters on both Windows and cloud hosts. Configured Windows per-call bounds remain distinct from that combined retained-context limit. The official cloud MCP may return more because it has no server-side result-count control.
Routine eligible memory operations follow the owner's credits-only authority after explicit project scope and pre-transmission privacy filtering. Other billable services retain the existing per-run approval gate. This corrects the obsolete bounded-dollar-cost prerequisite for routine memory operations.
The existing maintained generator supplies both changed paragraphs from approved source version
2026-10-27.credits-only.10-public-retention. The project scope, content exclusions and single-writer addendum remain byte-identical. This follows merged PR #14 on current main633e2a9ffe30a9bf29bed56f798590fac4f7a862.Verification
97f0633e1428b1c1c13681718fee4d7c3c8c3c5e.repository_rule_targets.collect_targetsverification: PASS, both generated targets equal approved source; project addendum byte-identical.--check docs/agents/shared-context-and-memory.md): PASS.git diff --check: PASS. Normal one-file commit: PASS, with no hook bypass.Not run: application, sending, provider, database, browser or broad release checks locally; this change affects two generated instruction paragraphs. Fresh hosted CI and native host acceptance remain separate. No main merge or deployment is requested by this follow-up.