Replace Qdrant memory stack with ClawMem#28
Replace Qdrant memory stack with ClawMem#28snahrup wants to merge 2 commits intoghostwright:mainfrom
Conversation
Remove the raw Anthropic API dependency entirely. Judge calls now use the Claude Agent SDK query() with native json_schema outputFormat, tools disabled (tools: []), and maxTurns: 1 for sandboxed single-pass evaluation. JudgeError class carries cost info on failures so the daily cap tracks actual spend even when parsing fails. All ANTHROPIC_API_KEY references removed from code, tests, config, and docs. Author: Steve Nahrup
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: b3c48319f0
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "@anthropic-ai/sdk": "^0.80.0", | ||
| "@modelcontextprotocol/sdk": "^1.28.0", | ||
| "@slack/bolt": "^4.6.0", | ||
| "clawmem": "file:../ClawMem", |
There was a problem hiding this comment.
Pointing clawmem to file:../ClawMem makes installs fail for a normal clone/CI checkout where no sibling ../ClawMem repo exists, which in turn breaks runtime imports like clawmem/src/llm.ts and prevents tests/startup from running. This effectively turns the project into a non-self-contained build unless every environment is manually prepared with that external path.
Useful? React with 👍 / 👎.
| : { clawmem: false, configured: false }; | ||
|
|
||
| const uptimeSeconds = Math.floor((Date.now() - deps.startedAt) / 1000); | ||
| const allHealthy = memoryHealth.qdrant && memoryHealth.ollama; | ||
| const status = memoryHealth.clawmem ? "ok" : memoryHealth.configured ? "down" : "ok"; |
There was a problem hiding this comment.
When deps.memory is unavailable (for example after memory init fails and MCP is created without a ready memory instance), this fallback sets configured: false, so the status expression returns "ok" even though memory is down. That causes phantom://health to falsely report healthy state and hides a real backend failure from monitoring/clients.
Useful? React with 👍 / 👎.
1 participant
Summary
Verification