Skip to content

docs: exact remediation SQL for known issue #15 (embedding dimension mismatch) #64

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
kartikmanimuthu merged 1 commit into from
Oct 19, 2026
Merged

docs: exact remediation SQL for known issue #15 (embedding dimension mismatch) #64

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 21 additions & 0 deletions docs/superpowers/claw-studio-known-issues.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -419,6 +419,27 @@ misconfigured row has `embeddingDimensions: null`, so `&&` short-circuited and t
at least surface a clear `ClawEmbeddingsConfigError` instead of a raw Postgres 22000 until it's
corrected.

Exact remediation, once DB access is available — find the affected row(s) first (any provider whose
stored dimension doesn't match the column, or whose model is a known mismatch like Titan G1):

```sql
SELECT id, "tenantId", "embeddingModel", "embeddingDimensions" FROM llm_providers
WHERE "embeddingModel" IS NOT NULL
AND ("embeddingDimensions" IS NULL OR "embeddingDimensions" != 1024);
```

Then, per affected row (nothing was ever successfully written at the wrong dimension, so no
re-embedding is required — this is a config correction, not a data migration):

```sql
UPDATE llm_providers
SET "embeddingModel" = 'amazon.titan-embed-text-v2:0', "embeddingDimensions" = 1024
WHERE id = '<affected row id>';
```

This is deployment-specific data, not something a PR against this repo can fix — recorded here so
whoever has DB access can apply it directly from the issue, without re-deriving the root cause.

---

## ✅ 16. FIXED (2026-08-03) — memory extraction intermittently fails on malformed LLM JSON
Expand Down