Bug Description
Topic Judge (任务边界检测) has never worked since installing memos-local-openclaw-plugin. Every single call fails with HTTP 404 error.
Environment
- Plugin version: memos-local-openclaw-plugin v1.0.3
- OpenClaw version: (latest)
- OS: macOS
- Installation date: 2026-03-20
Configuration
```json
{
"provider": "openai_compatible",
"model": "MiniMax-M2.7-highspeed",
"endpoint": "https://api.minimaxi.com/v1",
"apiKey": "***"
}
```
Error Details
Error message:
[plugins] [error] judgeNewTopic failed (openai_compatible/MiniMax-M2.7-highspeed), no more fallbacks: Error: OpenAI topic-judge failed (404): <html>
<head><title>404 Not Found</title></head>
<center><h1>404 Not Found</h1></center>
Statistics:
- Topic Judge calls: 559
- Failures: 559 (100% failure rate)
- First failure: 2026-03-20T08:11:21 (first ever call after installation)
What Works
Other AI calls using the same MiniMax configuration work correctly:
- ✅ Summarizer
- ✅ Memory Filter (filterRelevant)
- ✅ Dedup Judge (judgeDedup)
Only Topic Judge fails with 404.
Analysis
Looking at the source code (src/ingest/providers/openai.ts), the topic-judge call uses the same endpoint and model as other calls:
// judgeNewTopicOpenAI function (line 213)
const endpoint = normalizeChatEndpoint(cfg.endpoint ?? "https://api.openai.com/v1/chat/completions");
// endpoint becomes: https://api.minimaxi.com/v1/chat/completions
// model: MiniMax-M2.7-highspeed
// max_tokens: 10
The only difference is max_tokens: 10 (very short response expected).
Expected Behavior
Topic Judge should return "NEW" or "SAME" to detect conversation topic boundaries. Currently, all calls fall back to null, which disables task boundary detection.
Possible Causes
- MiniMax API may not support certain request patterns for topic-judge
- The model name "MiniMax-M2.7-highspeed" may not be valid for topic-judge endpoint
- MiniMax API at api.minimaxi.com may have different behavior for short max_tokens requests
Logs
```
2026-03-20T08:11:21.166+08:00 [plugins] [error] judgeNewTopic failed (openai_compatible/MiniMax-M2.7-highspeed), no more fallbacks: Error: OpenAI topic-judge failed (404):
2026-03-22T12:37:24.954+08:00 [gateway] Topic judge result: null(fallback)
```
Workaround
None known. Task boundary detection is completely disabled.
Bug Description
Topic Judge (任务边界检测) has never worked since installing memos-local-openclaw-plugin. Every single call fails with HTTP 404 error.
Environment
Configuration
```json
{
"provider": "openai_compatible",
"model": "MiniMax-M2.7-highspeed",
"endpoint": "https://api.minimaxi.com/v1",
"apiKey": "***"
}
```
Error Details
Error message:
Statistics:
What Works
Other AI calls using the same MiniMax configuration work correctly:
Only Topic Judge fails with 404.
Analysis
Looking at the source code (
src/ingest/providers/openai.ts), the topic-judge call uses the same endpoint and model as other calls:The only difference is
max_tokens: 10(very short response expected).Expected Behavior
Topic Judge should return "NEW" or "SAME" to detect conversation topic boundaries. Currently, all calls fall back to null, which disables task boundary detection.
Possible Causes
Logs
```
2026-03-20T08:11:21.166+08:00 [plugins] [error] judgeNewTopic failed (openai_compatible/MiniMax-M2.7-highspeed), no more fallbacks: Error: OpenAI topic-judge failed (404):
2026-03-22T12:37:24.954+08:00 [gateway] Topic judge result: null(fallback)
```
Workaround
None known. Task boundary detection is completely disabled.