Skip to content

docs(cipher): store skill — /api/memory routes landed, 401 not 404 - #2204

Merged
POWERFULMOVES merged 1 commit into
mainfrom
docs/cipher-store-status
Jul 24, 2026
Merged

docs(cipher): store skill — /api/memory routes landed, 401 not 404#2204
POWERFULMOVES merged 1 commit into
mainfrom
docs/cipher-store-status

Conversation

@POWERFULMOVES

Copy link
Copy Markdown
Owner

Operator-flagged stale note, live-verified: Pmoves-cipher PR #5 (2026-07-14 wave — Qdrant embedding sidecar, BM25 sparse + dense RRF hybrid search, Ollama fallback, A2A discovery) implemented the /api/memory CRUD routes. Live :8105 probe returns 401 (auth required), not 404. The skill's 2026-04-01 known-issue block told agents the routes don't exist and to always fall back — now it points them at the API key requirement instead.

Remaining tracked separately: monorepo gitlink promotion for Pmoves-cipher is non-FF (hardened branch was rebased upstream — no common ancestor with pin cb3d3bed); needs a deliberate diverged-history promotion verifying the overlay survived.

🤖 Generated with Claude Code

The 2026-04-01 known-issue note claimed Pmoves-cipher lacks /api/memory
routes. Operator flagged it stale and live verification agrees: fork
PR #5 (2026-07-14 wave, with the Qdrant embedding sidecar, BM25+dense
RRF hybrid search, and Ollama fallback) implemented the CRUD routes;
the live API returns 401 (auth required), not 404. Note updated to
point callers at the API key instead of assuming the routes are absent.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@POWERFULMOVES, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 14 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: eabd15dc-725b-438e-bba7-9a7e2a9d941c

📥 Commits

Reviewing files that changed from the base of the PR and between 713be63 and b22fd5f.

📒 Files selected for processing (1)
  • .claude/commands/cipher/store.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/cipher-store-status

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@github-actions github-actions Bot added the docs Documentation label Jul 24, 2026
@POWERFULMOVES
POWERFULMOVES merged commit 11673c9 into main Jul 24, 2026
18 of 19 checks passed
@POWERFULMOVES
POWERFULMOVES deleted the docs/cipher-store-status branch July 24, 2026 13:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs Documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants