fix(memory): improve error message when node:sqlite is unavailable by rrrrrredy · Pull Request #69199 · openclaw/openclaw

rrrrrredy · 2026-04-20T04:56:03Z

Summary

Keeps the existing PR branch scoped to extensions/memory-core.
Classifies node:sqlite / missing built-in sqlite runtime errors in buildMemorySearchUnavailableResult(error, overrides?).
Keeps the existing quota and generic branches, and keeps explicit warning / action overrides authoritative.
Fixes the latest CI lint finding by using String#includes() for the sqlite-missing checks.

Behavior

When the runtime cannot load node:sqlite, memory_search now returns the same unavailable result shape with a targeted warning/action instead of the generic embedding-provider message.

The action matches current OpenClaw support policy: Node.js >=22.19.0, with Node.js 24 recommended. The doc link uses the valid Memory CLI page: https://docs.openclaw.ai/cli/memory.

Real Behavior Proof

Behavior or issue addressed: memory_search unavailable payloads now classify missing node:sqlite runtime errors with targeted warning/action text while preserving quota, generic, and explicit override behavior.
Real environment tested: Windows PowerShell in the OpenClaw repo; old-runtime missing-builtin reproduction plus Node.js v24.13.0 for helper output, tests, and lint.
Exact steps or command run after this patch: node -e "try { require('node:sqlite'); console.log('node:sqlite available'); } catch (error) { console.log(String(error.message)); }"; node --import tsx -e "import { buildMemorySearchUnavailableResult } from './extensions/memory-core/src/tools.shared.ts'; ..."; node scripts/test-projects.mjs extensions/memory-core/src/tools.test.ts; node node_modules/oxlint/bin/oxlint extensions/memory-core/src/tools.shared.ts extensions/memory-core/src/tools.test.ts; node node_modules/oxlint/bin/oxlint --tsconfig config/tsconfig/oxlint.extensions.json extensions/memory-core.
Evidence after fix (screenshot, recording, terminal capture, console output, redacted runtime log, linked artifact, or copied live output): Copied terminal output below shows the missing builtin error, the after-fix unavailable payload, override preservation, and targeted test/lint output.
Observed result after fix: A missing node:sqlite error returns disabled: true, unavailable: true, the original error string, and targeted Node.js upgrade guidance; custom warning and action overrides still win; the targeted memory-core tests pass.
What was not tested: No known gaps for this helper-level unavailable payload change; a full old-Node live memory index/search session was not run because the focused bug is the formatter branch and the old-runtime reproduction plus helper output exercise that behavior directly.
Proof limitations or environment constraints: The old-runtime missing-builtin command demonstrates the source error; the current supported Node.js 24 runtime is used for the branch output and tests.

Old-runtime reproduction of the missing builtin:

$ node -e "try { require('node:sqlite'); console.log('node:sqlite available'); } catch (error) { console.log(String(error.message)); }"
No such built-in module: node:sqlite

Current branch unavailable payload for that error:

$ node --import tsx -e "import { buildMemorySearchUnavailableResult } from './extensions/memory-core/src/tools.shared.ts'; console.log(JSON.stringify(buildMemorySearchUnavailableResult('No such built-in module: node:sqlite'), null, 2));"
{
  "results": [],
  "disabled": true,
  "unavailable": true,
  "error": "No such built-in module: node:sqlite",
  "warning": "Memory search is unavailable because node:sqlite is not available in this Node.js runtime.",
  "action": "Use OpenClaw with Node.js 22.19.0 or newer; Node.js 24 is recommended for memory search. See https://docs.openclaw.ai/cli/memory.",
  "debug": {
    "warning": "Memory search is unavailable because node:sqlite is not available in this Node.js runtime.",
    "action": "Use OpenClaw with Node.js 22.19.0 or newer; Node.js 24 is recommended for memory search. See https://docs.openclaw.ai/cli/memory.",
    "error": "No such built-in module: node:sqlite"
  }
}

Override preservation check:

$ node --import tsx -e "import { buildMemorySearchUnavailableResult } from './extensions/memory-core/src/tools.shared.ts'; console.log(JSON.stringify(buildMemorySearchUnavailableResult('No such built-in module: node:sqlite', { warning: 'custom warning', action: 'custom action' }), null, 2));"
{
  "results": [],
  "disabled": true,
  "unavailable": true,
  "error": "No such built-in module: node:sqlite",
  "warning": "custom warning",
  "action": "custom action",
  "debug": {
    "warning": "custom warning",
    "action": "custom action",
    "error": "No such built-in module: node:sqlite"
  }
}

Targeted test run on Node.js 24.13.0:

$ node scripts/test-projects.mjs extensions/memory-core/src/tools.test.ts
Test Files  1 passed (1)
Tests       19 passed (19)
[test] passed 1 Vitest shard

Lint checks:

$ node node_modules/oxlint/bin/oxlint extensions/memory-core/src/tools.shared.ts extensions/memory-core/src/tools.test.ts
# passed

$ node node_modules/oxlint/bin/oxlint --tsconfig config/tsconfig/oxlint.extensions.json extensions/memory-core
# passed

Note: node scripts/run-bundled-extension-oxlint.mjs and node scripts/run-oxlint-shards.mjs --threads=8 both timed out locally on Windows after 5 minutes with no diagnostics, but the CI failure was the two prefer-includes findings in extensions/memory-core/src/tools.shared.ts; the changed file and memory-core extension path now pass oxlint directly.

This PR narrows the error-message logic in buildMemorySearchUnavailableResult to detect node:sqlite unavailability and return a targeted warning/action instead of the generic embedding-provider message. A matching unit test locks in the new payload. The change is minimal, well-scoped, and correctly handles the three failure branches (SQLite missing → quota exhausted → generic).

Confidence Score: 5/5

Safe to merge — only changes error-message branching logic with a corresponding test.

The sole remaining finding is a P2 style inconsistency (raw reason vs normalized string for regex matching); both approaches are functionally equivalent and carry no correctness risk.

No files require special attention.

Prompt To Fix All With AI

This is a comment left during a code review.
Path: extensions/memory-core/src/tools.shared.ts
Line: 122-124

Comment:
**Inconsistent string normalization between checks**

`isQuotaError` pipes `reason` through `normalizeLowercaseStringOrEmpty` before testing, but `isSqliteMissing` tests the raw `reason` and relies on the `i` flag instead. Both approaches work, but mixing them is needlessly inconsistent. Consider normalizing `isSqliteMissing` the same way for symmetry, or note the intentional difference with a comment.

```suggestion
  const isQuotaError = /insufficient_quota|quota|429/.test(normalizeLowercaseStringOrEmpty(reason));
  const normalizedReason = normalizeLowercaseStringOrEmpty(reason);
  const isSqliteMissing =
    /node:sqlite|no such built-in module.*sqlite|missing node:sqlite/.test(normalizedReason);
```

How can I resolve this? If you propose a fix, please make it concise.

_{Reviews (1): Last reviewed commit: "fix(memory): improve sqlite unavailable ..." | Re-trigger Greptile}

greptile-apps · 2026-04-20T05:14:29Z

  const isQuotaError = /insufficient_quota|quota|429/.test(normalizeLowercaseStringOrEmpty(reason));
-  const warning = isQuotaError
-    ? "Memory search is unavailable because the embedding provider quota is exhausted."
-    : "Memory search is unavailable due to an embedding/provider error.";
-  const action = isQuotaError
-    ? "Top up or switch embedding provider, then retry memory_search."
-    : "Check embedding provider configuration and retry memory_search.";
+  const isSqliteMissing =
+    /node:sqlite|no such built-in module.*sqlite|missing node:sqlite/i.test(reason);


Inconsistent string normalization between checks

isQuotaError pipes reason through normalizeLowercaseStringOrEmpty before testing, but isSqliteMissing tests the raw reason and relies on the i flag instead. Both approaches work, but mixing them is needlessly inconsistent. Consider normalizing isSqliteMissing the same way for symmetry, or note the intentional difference with a comment.

Suggested change

const isQuotaError = /insufficient_quota|quota|429/.test(normalizeLowercaseStringOrEmpty(reason));

const warning = isQuotaError

? "Memory search is unavailable because the embedding provider quota is exhausted."

: "Memory search is unavailable due to an embedding/provider error.";

const action = isQuotaError

? "Top up or switch embedding provider, then retry memory_search."

: "Check embedding provider configuration and retry memory_search.";

const isSqliteMissing =

/node:sqlite|no such built-in module.*sqlite|missing node:sqlite/i.test(reason);

const isQuotaError = /insufficient_quota|quota|429/.test(normalizeLowercaseStringOrEmpty(reason));

const normalizedReason = normalizeLowercaseStringOrEmpty(reason);

const isSqliteMissing =

/node:sqlite|no such built-in module.*sqlite|missing node:sqlite/.test(normalizedReason);

Prompt To Fix With AI

This is a comment left during a code review. Path: extensions/memory-core/src/tools.shared.ts Line: 122-124 Comment: **Inconsistent string normalization between checks** `isQuotaError` pipes `reason` through `normalizeLowercaseStringOrEmpty` before testing, but `isSqliteMissing` tests the raw `reason` and relies on the `i` flag instead. Both approaches work, but mixing them is needlessly inconsistent. Consider normalizing `isSqliteMissing` the same way for symmetry, or note the intentional difference with a comment. ```suggestion const isQuotaError = /insufficient_quota|quota|429/.test(normalizeLowercaseStringOrEmpty(reason)); const normalizedReason = normalizeLowercaseStringOrEmpty(reason); const isSqliteMissing = /node:sqlite|no such built-in module.*sqlite|missing node:sqlite/.test(normalizedReason); ``` How can I resolve this? If you propose a fix, please make it concise.

rrrrrredy · 2026-04-23T01:46:23Z

Status update as of 2026-04-23: this is the active clean respin for #59457, the current checks are green, and the scope is limited to the SQLite-unavailable messaging fix in memory-core. If that narrower scope looks right, I would appreciate maintainer review on this version.

clawsweeper · 2026-04-29T04:23:44Z

Codex review: needs maintainer review before merge. Reviewed June 22, 2026, 2:08 PM ET / 18:08 UTC.

Summary
The PR adds missing-node:sqlite classification to memory-search unavailable-result formatting and tests the targeted warning/action plus explicit override preservation.

PR surface: Source +14, Tests +42. Total +56 across 2 files.

Reproducibility: yes. Current main source routes missing node:sqlite manager setup failures into the generic unavailable-result helper, and the PR body includes terminal output for the missing-builtin error plus the after-fix payload.

Review metrics: none identified.

Stored data model
Persistent data-model change detected: unknown-data-model-change: extensions/memory-core/src/tools.shared.ts, unknown-data-model-change: extensions/memory-core/src/tools.test.ts, vector/embedding metadata: extensions/memory-core/src/tools.shared.ts, vector/embedding metadata: extensions/memory-core/src/tools.test.ts. Confirm migration or upgrade compatibility proof before merge.

Root-cause cluster
Relationship: canonical
Canonical: #69199
Summary: This PR is the canonical active item for the immediate missing-node:sqlite unavailable-payload UX fix; fallback search and provider-error hinting are adjacent work.

Members:

fixed_by_candidate: [UX]: error response is not actionable when is missing — wrong root cause diagnosis and no resolution path #59457 - The closed issue reports the same immediate generic-message bug and names this PR as the active clean fix path.
superseded: fix(memory): improve error message when node:sqlite is unavailable #59637 - The older closed PR attempted the same error-message fix but carried broad unrelated workflow and asset churn.
partial_overlap: [Feature]: Add keyword fallback for memory_search when node:sqlite is unavailable #93150 - The open issue tracks longer-term keyword fallback for missing SQLite and explicitly leaves this PR's remediation text out of scope.
partial_overlap: fix(memory): fall back to keyword search without sqlite #93260 - The open PR implements degraded keyword fallback for the same missing-SQLite failure mode, but changes manager behavior rather than replacing this narrower unavailable-payload fix.
adjacent_distinct: fix(memory-core): add actionable remediation hints for memory search embedding errors #75951 - That open PR also touches memory-search remediation hints, but it targets embedding-provider errors rather than missing node:sqlite runtime errors.

Proposal only: this assessment does not dispatch repair, suppress jobs, mutate sibling items, close, or merge anything.

Merge readiness
Overall: 🦞 diamond lobster
Proof: 🦞 diamond lobster
Patch quality: 🦞 diamond lobster
Result: ready for maintainer review.

Overall follows the weaker of proof and patch quality, so missing proof can cap an otherwise strong patch.

Risk before merge

[P1] Live mergeability is currently unknown, and a maintainer comment says the branch needed an update against current main for Dependency Guard, so landing should refresh the exact head against current main.

Maintainer options:

Decide the mitigation before merge
Land this narrow unavailable-payload formatter/test change, and keep degraded keyword fallback behavior in [Feature]: Add keyword fallback for memory_search when node:sqlite is unavailable #93150 or fix(memory): fall back to keyword search without sqlite #93260 as the separate capability decision.
Pause or close
Do not merge this PR until maintainers decide whether the risk is worth taking.

Next step before merge

No ClawSweeper repair lane is needed because no concrete patch defect was found; maintainers should review/refresh the branch and merge if exact-head checks and mergeability pass.

Security
Cleared: The diff only changes memory-core error-message branching and tests; it does not touch dependencies, workflows, secrets, permissions, package resolution, or code-execution surfaces.

Review details

Best possible solution:

Land this narrow unavailable-payload formatter/test change, and keep degraded keyword fallback behavior in #93150 or #93260 as the separate capability decision.

Do we have a high-confidence way to reproduce the issue?

Yes. Current main source routes missing node:sqlite manager setup failures into the generic unavailable-result helper, and the PR body includes terminal output for the missing-builtin error plus the after-fix payload.

Is this the best way to solve the issue?

Yes. The narrow maintainable fix is to classify known SQLite-runtime messages inside the existing unavailable-result helper while preserving quota, generic, and explicit override behavior.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against 25090056dc22.

Label changes

Label justifications:

P2: This fixes a real but bounded memory-search UX bug where missing SQLite support points users and agents toward the wrong provider remediation.
rating: 🦞 diamond lobster: Overall readiness is 🦞 diamond lobster; proof is 🦞 diamond lobster and patch quality is 🦞 diamond lobster.
status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Sufficient (live_output): The PR body provides copied live terminal output showing the missing-builtin reproduction, after-fix unavailable payload, override preservation, and targeted test/lint runs, which is sufficient for this helper-level formatter change.
proof: sufficient: Contributor real behavior proof is sufficient. The PR body provides copied live terminal output showing the missing-builtin reproduction, after-fix unavailable payload, override preservation, and targeted test/lint runs, which is sufficient for this helper-level formatter change.

Evidence reviewed

PR surface:

Source +14, Tests +42. Total +56 across 2 files.

View PR surface stats

Area	Files	Added	Removed	Net
Source	1	25	11	+14
Tests	1	43	1	+42
Docs	0	0	0	0
Config	0	0	0	0
Generated	0	0	0	0
Other	0	0	0	0
Total	2	68	12	+56

What I checked:

Current main still has generic non-quota guidance: buildMemorySearchUnavailableResult on current main only special-cases quota errors; missing SQLite errors still fall into the generic embedding/provider warning and action. (extensions/memory-core/src/tools.shared.ts:115, 25090056dc22)
Caller routes manager setup failures through the helper: When memory manager setup returns an error, memory_search records cooldown and returns buildMemorySearchUnavailableResult(memory.error). (extensions/memory-core/src/tools.ts:444, 25090056dc22)
SQLite loader produces the error family being classified: The memory host SDK wraps failed require("node:sqlite") loads as a missing-node:sqlite SQLite-support error. (packages/memory-host-sdk/src/host/sqlite.ts:17, 25090056dc22)
PR head implements the narrow classifier: The PR adds targeted warning/action constants and classifies node:sqlite, missing built-in sqlite, and existing SQLite-support-unavailable messages before preserving quota precedence and explicit overrides. (extensions/memory-core/src/tools.shared.ts:122, 10e3b0db1d43)
PR head adds regression coverage: The tests cover the missing-node:sqlite unavailable payload and verify explicit warning/action overrides still win. (extensions/memory-core/src/tools.test.ts:127, 10e3b0db1d43)
Latest release has not shipped the fix: The latest release tag still has the generic non-quota fallback in the same helper, so the PR remains necessary for released users. (extensions/memory-core/src/tools.shared.ts:108, c645ec4555c0)

Likely related people:

steipete: History shows this person introduced and refactored the memory-core helper boundary and memory host SDK path that this PR relies on. (role: feature-history contributor; confidence: high; commits: 3d0050c306ac, d0ce2d104443, bd6c7969ea9c; files: extensions/memory-core/src/tools.shared.ts, extensions/memory-core/src/tools.ts, packages/memory-host-sdk/src/host/sqlite.ts)
vincentkoc: Recent path history touches the same memory-core helper and release/current-main surface around the unavailable-result behavior. (role: recent area contributor; confidence: medium; commits: c645ec4555c0; files: extensions/memory-core/src/tools.shared.ts, extensions/memory-core/src/tools.ts, packages/memory-host-sdk/src/host/sqlite.ts)
Takhoffman: Recent memory diagnostics work touched adjacent memory behavior and tests, making this person a useful reviewer for memory-search UX changes. (role: adjacent memory contributor; confidence: medium; commits: c37e49f275fb; files: extensions/memory-core/src/tools.shared.ts, extensions/memory-core/src/tools.test.ts)
zerone0x: Current blame on the helper and SQLite loader points to a recent broad current-main commit that carried these files, though the behavior predates that commit. (role: recent current-main touch; confidence: low; commits: 3a7cdaf32c87; files: extensions/memory-core/src/tools.shared.ts, packages/memory-host-sdk/src/host/sqlite.ts)

What the crustacean ranks mean

🦀 challenger crab: rare, exceptional readiness with strong proof, clean implementation, and convincing validation.
🦞 diamond lobster: very strong readiness with only minor maintainer review expected.
🐚 platinum hermit: good normal PR, likely mergeable with ordinary maintainer review.
🦐 gold shrimp: useful signal, but proof or patch confidence is still limited.
🦪 silver shellfish: thin signal; proof, validation, or implementation needs work.
🧂 unranked krab: not merge-ready because proof is missing/unusable or there are serious correctness or safety concerns.
🌊 off-meta tidepool: rating does not apply to this item.

Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

How this review workflow works

ClawSweeper keeps one durable marker-backed review comment per issue or PR.
Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
Maintainers can also comment @clawsweeper review to request a fresh review only.
Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

clawsweeper · 2026-05-20T02:45:29Z

ClawSweeper PR egg

🎁 Pass real behavior proof to wake the egg and unlock a hatchable treat.

Where did the egg go?

The egg game starts only after the PR passes the real-behavior proof check.
Before that, no creature or rarity is rolled. The treat waits for real proof.
This is still just collectible flavor: proof affects review readiness, not creature quality.

RomneyDa · 2026-05-29T06:35:14Z

Heads up: this PR needs to be updated against current main before the new required Dependency Guard check can pass.

openclaw-barnacle · 2026-06-13T05:02:36Z

This pull request has been automatically marked as stale due to inactivity.
Please add updates or it will be closed.

rrrrrredy · 2026-06-15T03:28:32Z

@clawsweeper re-review

clawsweeper · 2026-06-15T03:28:35Z

🦞🧹
ClawSweeper re-review requested.

I asked ClawSweeper to review this item again.
Action: item re-review queued (workflow sweep.yml, event repository_dispatch).
Result: the existing ClawSweeper review comment will be edited in place when the review finishes.

Re-review progress:

State: Failed
Detail: The targeted re-review did not finish cleanly. Check the workflow run for details.
Run: https://github.com/openclaw/clawsweeper/actions/runs/27522241955
Updated: 2026-06-15T03:51:45.095Z

clawsweeper · 2026-06-15T05:21:55Z

🦞🧹
ClawSweeper re-review requested.

I asked ClawSweeper to review this item again.
Action: item re-review queued (workflow sweep.yml, event repository_dispatch).
Result: the existing ClawSweeper review comment will be edited in place when the review finishes.

Re-review progress:

State: Failed
Detail: The targeted re-review did not finish cleanly. Check the workflow run for details.
Run: https://github.com/openclaw/clawsweeper/actions/runs/27525826673
Updated: 2026-06-15T05:30:24.551Z

vincentkoc · 2026-06-23T02:24:50Z

Thanks @rrrrrredy for the original scoped implementation in #69199.

I am closing this because the replacement PR has now landed: #95916, merged as 19627c7dd9b6f4eb25a896168f53c5528917108e. Clownfish used a replacement path to carry the narrow node:sqlite unavailable guidance fix forward while preserving attribution for your source PR.

If the landed behavior does not match the original intent or a separate reproduction remains, please reply and we can reopen or split that follow-up.

openclaw-barnacle Bot added extensions: memory-core Extension: memory-core size: XS labels Apr 20, 2026

rrrrrredy mentioned this pull request Apr 20, 2026

fix(memory): improve error message when node:sqlite is unavailable #59637

Closed

21 tasks

rrrrrredy marked this pull request as ready for review April 20, 2026 05:13

greptile-apps Bot reviewed Apr 20, 2026

View reviewed changes

This was referenced Apr 23, 2026

[Feature]: Add file-based fallback search when node:sqlite is unavailable #59451

Closed

[UX]: error response is not actionable when is missing — wrong root cause diagnosis and no resolution path #59457

Closed

openclaw-barnacle Bot added the triage: needs-real-behavior-proof Candidate: external PR needs after-fix proof from a real setup. label May 20, 2026

openclaw-barnacle Bot added the stale Marked as stale due to inactivity label Jun 13, 2026

fix(memory): classify missing node sqlite search errors

c4d7092

rrrrrredy force-pushed the fix/memory-search-sqlite-error-clean branch from 7492cf1 to c4d7092 Compare June 15, 2026 03:28

openclaw-barnacle Bot added size: S and removed size: XS labels Jun 15, 2026

rrrrrredy mentioned this pull request Jun 15, 2026

[Feature]: Add keyword fallback for memory_search when node:sqlite is unavailable #93150

Open

clawsweeper Bot mentioned this pull request Jun 18, 2026

fix(memory): fall back to keyword search without sqlite #93260

Closed

clawsweeper Bot mentioned this pull request Jun 21, 2026

fix(memory-core): add actionable remediation hints for memory search embedding errors #75951

Closed

5 tasks

vincentkoc mentioned this pull request Jun 23, 2026

fix(memory): improve node:sqlite unavailable guidance #95916

Merged

vincentkoc closed this Jun 23, 2026

vincentkoc added the clownfish Tracked by Clownfish automation label Jun 23, 2026

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

fix(memory): improve error message when node:sqlite is unavailable#69199

fix(memory): improve error message when node:sqlite is unavailable#69199
rrrrrredy wants to merge 2 commits into
openclaw:mainfrom
rrrrrredy:fix/memory-search-sqlite-error-clean

rrrrrredy commented Apr 20, 2026 •

edited

Loading

Uh oh!

greptile-apps Bot commented Apr 20, 2026

Uh oh!

greptile-apps Bot Apr 20, 2026

Uh oh!

rrrrrredy commented Apr 23, 2026

Uh oh!

clawsweeper Bot commented Apr 29, 2026 •

edited

Loading

Uh oh!

clawsweeper Bot commented May 20, 2026

Uh oh!

RomneyDa commented May 29, 2026

Uh oh!

openclaw-barnacle Bot commented Jun 13, 2026

Uh oh!

rrrrrredy commented Jun 15, 2026

Uh oh!

clawsweeper Bot commented Jun 15, 2026 •

edited

Loading

Uh oh!

clawsweeper Bot commented Jun 15, 2026 •

edited

Loading

Uh oh!

vincentkoc commented Jun 23, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Uh oh!

Conversation

rrrrrredy commented Apr 20, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Behavior

Real Behavior Proof

Related

Uh oh!

greptile-apps Bot commented Apr 20, 2026

Greptile Summary

Confidence Score: 5/5

Uh oh!

greptile-apps Bot Apr 20, 2026

Choose a reason for hiding this comment

Uh oh!

rrrrrredy commented Apr 23, 2026

Uh oh!

clawsweeper Bot commented Apr 29, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

clawsweeper Bot commented May 20, 2026

Uh oh!

RomneyDa commented May 29, 2026

Uh oh!

openclaw-barnacle Bot commented Jun 13, 2026

Uh oh!

rrrrrredy commented Jun 15, 2026

Uh oh!

clawsweeper Bot commented Jun 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

clawsweeper Bot commented Jun 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

vincentkoc commented Jun 23, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

rrrrrredy commented Apr 20, 2026 •

edited

Loading

clawsweeper Bot commented Apr 29, 2026 •

edited

Loading

clawsweeper Bot commented Jun 15, 2026 •

edited

Loading

clawsweeper Bot commented Jun 15, 2026 •

edited

Loading