Previously only 'plugins' and 'skills' were protected. Any user could
register @admin, @settings, @dashboard, @search, etc. as a publisher
handle, shadowing those platform routes via the $owner catch-all.
Add all current top-level src/routes/ segments to
RESERVED_PUBLIC_OWNER_HANDLES, grouped by purpose:
- Content browsing: skills, souls, plugins, packages, publishers, orgs
- Profile shortlinks: p, u
- User flows: search, import, upload, publish-skill, publish-plugin,
stars, dashboard, settings
- Admin/internal: admin, management, audits
- Informational: docs, cli
- Auth/account: user, users
Also add a doc comment noting to update this set when new top-level
routes are added.
* fix: restrict membership management to org publishers
* fix(api): ignore stale personal publisher memberships
* fix(api): reject stale personal publisher publish targets
* fix(api): reject stale personal publisher memberships
* fix(api): use personal publisher links for package access
* fix(api): guard personal publisher owner scopes
* fix: enforce publisher ownership for skill reads
* fix: narrow personal publisher dashboard owner
* fix: ignore stale personal package memberships
* fix: allow own legacy personal skill destination
* fix: preserve legacy personal package dashboards
* fix: preserve legacy personal skill dashboards
* fix: avoid redundant personal publisher boolean coercion
* fix: preserve legacy personal publisher access
* fix: include legacy direct packages in personal dashboard
* fix: close stale personal publisher ownership gaps
---------
Co-authored-by: Patrick Erichsen <patrick.a.erichsen@gmail.com>
* fix: hide package resources when owners are banned
* fix(api): attribute unban package restores to moderator
* fix(web): clarify package effects in ban confirmations
* fix(api): continue package ban batches during in-flight bans
* fix: keep package unban restore scoped to ban batch
* fix: retimestamp package releases during repeated bans
* fix: start package ban batches after user ban commit
* fix: preserve manual package moderation after unban
* fix: cover personal publisher package sanctions
* fix: restore personal publisher packages in autoban remediation
* fix: bound package publish token revocation batches
* fix: clear package ban reason during remediation restore
* fix: block direct package ban restores
* fix: scan linked personal publisher packages during sanctions
* fix: tighten package sanction restore batches
* fix: block personal publisher publishes after owner ban
* fix: allow initial package ban cleanup before commit
---------
Co-authored-by: Patrick Erichsen <patrick.a.erichsen@gmail.com>
* fix: block direct skill transfers under moderation
* fix(api): block accepted transfers for moderated skills
* fix(api): block malware-flagged skill transfers
* fix: cover moderated skill transfer bypasses
* test: support ownership heal transfer sync
* fix: close moderated transfer backfill gaps
* fix: block soft-deleted transfer guard state
---------
Co-authored-by: Patrick Erichsen <patrick.a.erichsen@gmail.com>
* feat: add GET /api/v1/skills/export for batch ZIP download
Add a new REST API endpoint that allows authenticated admin users to
export skills in bulk as a merged ZIP archive, designed for the ClawHub
China mirror site to efficiently sync skill data.
- New endpoint: GET /api/v1/skills/export?startDate=&endDate=&limit=&cursor=
- Admin-only auth via requireExportAuth (Bearer token + role check)
- Zip Slip protection: validateSlug + validateFilePath
- Duplicate ZIP path detection in buildMergedExportZip
- Per-skill metadata written to _export_skill_meta.json (avoids collision with skill files)
- Error recording: missing version/blob logged to _errors.json
- Dedicated rate limit tier: export { ip: 10, key: 60, adminKey: 600 }
- Cursor-based pagination on skillSearchDigest.by_active_created index
- Chunked parallel blob reads (50 concurrent)
Co-Authored-By: Claude <noreply@anthropic.com>
* fix: allow authenticated skill exports
---------
Co-authored-by: Claude <noreply@anthropic.com>
Co-authored-by: Patrick Erichsen <patrick.a.erichsen@gmail.com>
Replace ad-hoc sign-in UI on /settings, /dashboard, /import, /stars,
/cli/auth and /docs/auth with a single SignInPrompt component that
mirrors the polished /settings design (gradient backdrop, blur, card
with shadow, LockKeyhole icon, styled GitHub sign-in button).
Also replaces inline 'Sign in to comment.' text in SoulDetailPage and
SkillCommentsPanel with a compact SignInButton size='sm'.
Adds SignInPrompt.test.tsx with 8 unit tests and -stars.test.tsx with
6 route-level tests.
Fixes stars.tsx loading logic so unauthenticated users see the prompt
immediately instead of a skeleton.
- bun run build: pass
- bun run format:check: pass
- bun run lint: pass
- bun run test: 1,758 tests pass
Co-authored-by: Patrick Erichsen <patrick.a.erichsen@gmail.com>
* fix: prevent skill transfer acceptance after requester is banned
The acceptTransferInternal mutation did not verify whether the transfer
requester (fromUser) was banned or deactivated when the skill still
belonged to that user. This created a race condition where a pending
transfer could be accepted after the requester was banned, allowing
the skill to escape the ban batch and remain alive under a new owner.
This change moves the requester validity check before the ownership
branch, so it is evaluated unconditionally for all transfers.
Fixes a security vulnerability where banned users' skills could
survive moderation actions via pending transfers.
* fix: harden skill transfer acceptance
Co-authored-by: vyctorbrzezowski <krzyszchweski@gmail.com>
---------
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* feat: add local dev persona fab
* fix: time out stalled dev persona auth
* fix: restrict dev persona auth to local deployments
* chore: refresh static check dependencies
Redesign Settings into focused account, organization, API token, and account deletion views.
Follow-up verification:
- restored the Separator primitive usage so the Radix dependency remains active and static checks pass
- gated the organization member query to the organizations view with a selected org
- added focused settings coverage for default account rendering, organizations navigation/member loading, and legacy hash migration
Validation:
- bun install --frozen-lockfile
- bun run test -- src/routes/-settings.test.tsx src/__tests__/header.test.tsx
- bun run test:ui-contract
- bun run ci:static
- bunx tsc --noEmit
- bunx tsc -p packages/schema/tsconfig.json --noEmit
- bunx tsc -p packages/clawhub/tsconfig.json --noEmit
- VITE_CONVEX_URL=https://example.invalid bun run build
- GitHub repo-owned PR checks passed on verified signed head 7abd808fd4
Vercel fork authorization remained a non-code failure; authenticated local visual proof was blocked by missing GitHub login credentials, while signed-out settings route dev QA rendered without framework overlay.
Align signed-in header avatar controls across desktop and mobile so the menu trigger keeps consistent sizing, truncation, and dropdown styling.\n\nCo-authored-by: vyctorbrzezowski <krzyszchweski@gmail.com>
Add the publishers discovery/profile surface and harden the landing fixups for existing publisher aggregate rows and scoped plugin links.
Co-authored-by: Vyctor Huggo Przozwski <krzyszchweski@gmail.com>
Co-authored-by: Peter Steinberger <peter@steipete.com>
Complete CLI device login with Convex-backed device-code endpoints, the web approval page, API URL discovery, endpoint rate limiting, and approval state hardening.\n\nTests:\n- bunx vitest run convex/httpApi.handlers.test.ts packages/clawhub/src/deviceAuth.test.ts\n- bun run --cwd packages/clawhub test:src -- src/deviceAuth.test.ts\n- bunx tsc --noEmit\n- bunx tsc -p packages/schema/tsconfig.json --noEmit\n- bunx tsc -p packages/clawhub/tsconfig.json --noEmit\n- bun run ci:static\n- bun run ci:types-build\n- bunx convex codegen\n\nCo-authored-by: Lumen <openclaw@openclaw-secure.local>
Add per-skill CLI pinning and harden install semantics so pinned skills cannot be overwritten by forced installs.\n\nTests:\n- bunx vitest run packages/clawhub/src/cli/commands/skills.test.ts packages/clawhub/src/skills.test.ts packages/schema/src/schemas.test.ts\n- bun run --cwd packages/clawhub verify:build\n- bun run ci:static\n- bunx tsc -p packages/schema/tsconfig.json --noEmit\n- bunx tsc -p packages/clawhub/tsconfig.json --noEmit\n\nCo-authored-by: deepujain <deepujain@users.noreply.github.com>
Clean stale seed lookup/badge rows during repeated local Convex dev seed resets, and delete package fixtures in an order that avoids the package-release trigger fallback query limit.\n\nTests:\n- bun run test -- convex/devSeed.rescanFixtures.test.ts\n- bun run format:check\n- bun run lint\n- bunx tsc --noEmit\n- bunx tsc -p packages/schema/tsconfig.json --noEmit\n- bunx tsc -p packages/clawhub/tsconfig.json --noEmit\n- git diff --check origin/main...HEAD\n\nCo-authored-by: vyctorbrzezowski <krzyszchweski@gmail.com>
Document local Convex HTTP route usage through the site proxy port and make setup-worktree reject local site URL misconfigurations that point browser/auth routes at the function port.\n\nTests:\n- bun run test -- scripts/setup-worktree.test.ts\n- bun run format:check\n- bun run lint\n- bunx tsc --noEmit\n- bunx tsc -p packages/schema/tsconfig.json --noEmit\n- bunx tsc -p packages/clawhub/tsconfig.json --noEmit\n- git diff --check origin/main...HEAD\n\nCo-authored-by: vyctorbrzezowski <krzyszchweski@gmail.com>
Require the ClawSweeper GitHub App dispatch token path and remove the PAT fallback from dispatch credentials. Missing-app-secret deployments still exit through the existing no-token notice.\n\nTests:\n- rg -n "OPENCLAW_GH_TOKEN|steps\.token\.outputs\.token" .github/workflows/clawsweeper-dispatch.yml .github/workflows\n- bun run format:check\n- bun run lint\n- git diff --check origin/main...HEAD\n\nCo-authored-by: José Antonio Mijares <joseamijares@hotmail.com>
Rename the /skills alternate browse view from Cards to Grid while preserving legacy view=cards URLs as a compatible alias.\n\nTests:\n- VITE_CONVEX_URL=https://example.invalid bun run test -- src/__tests__/skills-index.test.tsx src/__tests__/skills-toolbar.test.tsx\n- bun run format:check\n- bun run lint\n- bunx tsc --noEmit\n- bunx tsc -p packages/schema/tsconfig.json --noEmit\n- bunx tsc -p packages/clawhub/tsconfig.json --noEmit\n\nCo-authored-by: vyctorbrzezowski <krzyszchweski@gmail.com>
Restore downloads, all-time installs, stars, and version metrics on owned skill rows in the dashboard. Also makes dropdown menu items use the expected pointer cursor.\n\nTests:\n- bunx vitest run src/routes/-dashboard.test.tsx --reporter verbose\n- bun run format:check\n- bun run lint\n- bunx tsc --noEmit\n- bunx tsc -p packages/schema/tsconfig.json --noEmit\n- bunx tsc -p packages/clawhub/tsconfig.json --noEmit\n- bun run test\n\nCo-authored-by: fuller-stack-dev <263060202+fuller-stack-dev@users.noreply.github.com>
Adds indexed, paginated dashboard skill loading and Load More UI.\n\nMaintainer validation after rebasing onto current main:\n- bun run test -- convex/skills.dashboard.test.ts src/routes/-dashboard.test.tsx\n- bun run test -- convex/skills.dashboard.test.ts convex/skills.list.test.ts\n- bunx tsc -p tsconfig.json --noEmit\n- bunx tsc -p packages/schema/tsconfig.json --noEmit\n- bunx tsc -p packages/clawhub/tsconfig.json --noEmit\n- bun run lint\n- bun run build\n\nNote: full bun run test currently has unrelated package publish route failures on current main; PR-focused tests and build are clean. Vercel PR preview remains blocked by fork deployment authorization.
Summary:
- Refresh the About page Recent Patterns section to explicitly allow specific maintainer-approved patterns.
- Replace the top-nav git icon with the GitHub mark for GitHub sign-in.
- Clean up ClawPack internal type exports and make Convex integrity hashing compatible with CI WebCrypto.
Validation:
- bun run format:check
- bun run lint
- bun run ci:static
- bun run ci:unit
- bunx tsc --noEmit
- bunx tsc -p packages/schema/tsconfig.json --noEmit && bunx tsc -p packages/clawhub/tsconfig.json --noEmit
- bun run test -- convex/lib/clawpack.test.ts
- VITE_CONVEX_URL=https://example.invalid bun run build
- GitHub checks for PR #1980 all passed
Split PR validation into explicit static, unit, package, type/build, HTTP e2e, and browser-smoke gates. Add local ci:* scripts and document the required status checks.
Make skill and plugin detail hero action panels span the full content width, moving scans/install above long-form detail content.\n\nVerified with local focused tests, lint, targeted formatting, diff check, build, and green PR CI build.
Remove the inherited global hover underline from full-card link surfaces while preserving normal inline link behavior.
Validated with targeted formatter/lint checks and a local browser hover pass across home category, carousel, trending, skills, plugins, and users card/list surfaces.
Restore the public header, hero, featured carousel, Trending Now, category grid, footer, and UI design-contract guardrails. Remove tweakcn/custom visual overlay settings and stale density preference plumbing, while preserving reviewed search/typeahead behavior and latest review fixes.
Refs #1819.
Read-only star status queries now treat stale, missing, deleted, or deactivated auth users as not starred instead of throwing. Star and unstar mutations still require an active authenticated user.
Validated locally:
- bunx vitest run convex/stars.test.ts convex/lib/access.test.ts
- bunx tsc -p packages/schema/tsconfig.json --noEmit
- bunx tsc -p packages/clawhub/tsconfig.json --noEmit
- bunx tsc --noEmit
- git diff --check origin/main...HEAD
CSS-only stabilization for the skill install surface.
- neutralize Radix scroll-lock body compensation now that the app reserves scrollbar gutter globally
- make the install surface span the full hero width and keep the two install panels balanced
- reserve stable space for prompt feedback and prompt preview content to avoid toggle reflow
Verified locally:
- bunx tsc -p packages/schema/tsconfig.json --noEmit
- bunx tsc -p packages/clawhub/tsconfig.json --noEmit
- bun run build
Repair the skill install surface follow-up typecheck issue after #1800 merged.
- replace the unused local exhaustiveness sentinel in `skillDetailUtils` with a shared `assertNever` helper
- keep the package-manager switch exhaustive without tripping `noUnusedLocals`
Add a dedicated skill install surface that pairs OpenClaw prompt-driven install with visible CLI commands.
- add Install with OpenClaw and CLI Commands panels to the skill detail page
- add Copy Prompt modes for Install Only and Install & Setup plus package-manager switching for the ClawHub CLI command
- add regression coverage for the new surface and make the repo build path use the working Vite invocation
vercel.json currently allow-lists SVG-only hosts (img.shields.io,
shields.io, badgen.net, flat.badgen.net) while dangerouslyAllowSVG:
false rejects every SVG source. Those two settings are incompatible,
and every badge in every README on production is returning 400
INVALID_IMAGE_OPTIMIZE_REQUEST (e.g. the license badge on
/plugins/@opik/opik-openclaw).
Switch to the pattern Vercel documents for safely serving SVGs in
their NEXTJS_SAFE_SVG_IMAGES conformance rule:
- dangerouslyAllowSVG: true — lets the optimizer accept SVG inputs
- contentDispositionType: attachment — forces download instead of
inline document rendering if someone navigates directly to the
/_vercel/image URL (the only context where SVG scripts would run)
- contentSecurityPolicy: script-src 'none'; sandbox; — blocks script
execution in the response
Defense in depth: browsers already sandbox SVGs loaded through <img>
so scripts don't run there anyway; the CSP + attachment header cover
the edge case of someone opening the optimizer URL directly. Net
security is equivalent to rejecting SVGs, but badges actually render.
Docs: https://vercel.com/docs/conformance/rules/NEXTJS_SAFE_SVG_IMAGES
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Replaces the React <img> wrapper with a tiny rehype plugin that rewrites
image srcs in the HAST. Same behavior (external http(s) URLs routed
through /_vercel/image; local/relative/data: URIs pass through), less
surface area:
- One shared plugin wired into both MarkdownPreview and SkillDetailTabs
via rehypePlugins instead of a components override at each call site
- Dropped ProxiedImg.tsx + its 7 unit tests; the two integration tests
in MarkdownPreview.test.tsx still assert the proxy URL shape for both
<img> and  syntax
- Stopped reading <img width="..."> for the proxy's w= param. Vercel
requires w to match a value in vercel.json sizes, so arbitrary README
widths (e.g. width="200") would have been rejected. Always w=1024 now;
the HTML width attribute still drives layout
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Closes the XSS / IP-leak surface from rendering third-party README
images directly on clawhub.ai. Routes external http(s) <img> sources
through Vercel's /_vercel/image endpoint, which enforces a host
allow-list, rejects SVG by default, and re-encodes rasters to webp.
Docs: https://vercel.com/docs/image-optimization
- vercel.json: add `images` config — host allow-list (raw.githubusercontent,
shields.io, etc., based on NuGet's published README allow-list),
dangerouslyAllowSVG=false, formats=[webp], 1d minimum cache TTL.
- src/components/ProxiedImg.tsx: small wrapper that rewrites external
http(s) src URLs to /_vercel/image?url=...&w=...&q=75. Local paths,
relative paths, and data: URIs pass through unchanged.
- MarkdownPreview + SkillDetailTabs: pass ProxiedImg as the `img`
component override to react-markdown — covers both raw HTML <img>
and markdown  syntax.
- package.json: drop unused `next` dep (vestigial from staging merge,
zero imports anywhere; doesn't affect next-themes).
Tests: 1028/1028 (was 1017, added 11 — ProxiedImg unit tests +
markdown integration tests covering proxied vs passthrough paths).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
8 typecheck errors that have been on main alongside the lint debt:
- convex/apiSurface.typecheck.ts: drop two stale @ts-expect-error
directives. The `increment` references they guarded no longer
exist (functions renamed to *Internal); runtime internal-only
enforcement is preserved by `internalMutation`.
- src/components/MarkdownPreview.tsx: cast createHighlighter result
to AnyHighlighter, narrow loadHighlighter return via the local
promise variable, type baseRehype + memoized rehypePlugins as
PluggableList (drops `as const` readonly mismatch with
ReactMarkdown's prop type).
- src/lib/theme.test.tsx: rename remaining "hub" usages to "claw"
(theme families collapsed to one in PR #1573 — the last "hub"
references in the harness button + applyTheme call would never
compile under the current ThemeName type).
- src/lib/packageApi.test.ts: add `?.` on the nullable result.
Full suite: lint 0, tests 1017/1017, typecheck 0.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Two pre-existing test failures on main, both caused by UI/data
changes in PR #1573 that the tests weren't updated for:
- theme.test.tsx: expected stored theme "hub" to round-trip, but
the staging merge collapsed all families into a single "claw"
theme — unknown families now fall back to "claw". Test now
asserts the legacy fallback behavior it claims to test.
- skill-detail-page.test.tsx: gated on the platform license
summary text, which was removed from SkillMetadataSidebar in
4d1a08b. Drop the obsolete assertion; the report-button
findByRole on the next line provides the same render-wait.
Full suite: 1017/1017 pass.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Fixes 70 oxlint errors that landed in the 2026-04-18 staging merge and
have kept main red ever since. Three rule categories:
- typescript-eslint(no-unnecessary-type-conversion): drop redundant
String/Number/Boolean wraps + 'as T' casts on values already typed.
- typescript-eslint(consistent-return): unify mixed return paths,
mostly in useEffect callbacks (early-return vs cleanup-fn) and CLI
command handlers.
- typescript-eslint(no-unnecessary-type-parameters): drop generics
used only once in a signature; replace with concrete types.
- Plus a handful of no-unused-vars, no-shadow, and one
no-redundant-type-constituents (JSX.Element -> ReactNode).
No runtime behavior changes. Full lint clean (0 errors); test suite
shows the same 2 pre-existing failures as main, no new regressions.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Plugin/soul READMEs that use raw HTML (e.g. centered logos via
<h1 align="center">, <picture>, <br/>) were rendering as escaped
text because @create-markdown/preview escapes all HTML. Swap the
renderer for react-markdown + remark-gfm + rehype-raw +
rehype-sanitize (GitHub's stack), with rehype-shiki-from-highlighter
for fenced code block syntax highlighting.
Sanitize runs before shiki so user HTML is scrubbed, and shiki's
trusted styled output flows through untouched.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* Refresh OG image and bust cache version
- Replace the social preview artwork with a new branded SVG and updated PNG
- Add a versioned og image URL in the root head tags to ensure the new asset is served
* Refresh OG image design
- Redesign the social preview graphic for the new ClawHub branding
- Bump the OG image version so the updated asset is served
* fix: refine clawhub og image
* fix: center og logo layout
* fix: emphasize clawhub branding in og image
* Refresh OG image branding
- Update Open Graph artwork and logo asset
- Adjust root metadata to use the new social preview image
* fix: refine clawhub og image
* fix: tighten og image layout
* fix: remove og logo panel
* fix: reduce og logo scale
* fix: align og image to new comp
- Show the logo mark in the mobile drawer title
- Tighten mobile suggestion spacing on small screens
- Add test coverage for the branded mobile nav header
- Simplify home and settings labels by removing redundant icons
- Swap automation icons to refresh glyphs in sidebars and toolbar
- Add subtle border and shadow treatment to the brand mark
Switch footer grid from auto-sized centered columns to equal 1fr
columns that span the full screen width.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Shift all theme variants (claw dark/light, hub dark/light) to the
bolder home-v2 backgrounds (#060608 dark, #faf6f1 light cream).
Harmonize surface, nav-bg, input-bg, and overlay-bg to match.
Set every radius token (--r-lg/md/sm/xs/pill) and home-v2 hardcoded
radii to a single consistent 8px value.
Remove home-v2–specific overrides for app-shell background, navbar
background, footer transparency, and navbar-inner max-width that
previously caused visual divergence between the home page and the
rest of the app.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Uncomment the brand logo image in the header navbar and reduce footer
vertical padding, gaps, and margins to ~55% of original height while
centering the grid columns and link text.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* improve about page rejection categories: add icons, fix grid, polish cards
- Add lucide-react icons to each rejection category card for visual scanning
- Fix unbalanced grid layout by removing featured card sizing, using clean 2/3-col grid
- Fix broken hover transitions (var(--transition-fast) was undefined outside reduced-motion)
- Add lift-on-hover effect and icon glow matching home page card patterns
- Render backtick-wrapped text as styled inline code elements
- Improve description text contrast from ~3.5:1 to ~4.8:1 (WCAG AA)
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: use h3 for card titles to fix heading hierarchy (WCAG 1.3.1)
Change rejection category card titles from <h2> to <h3> since the parent
section already uses <h2> for "Immediate rejection categories". Updates
the matching CSS selector from .about-rule-card h2 to h3.
Also adds tests for renderWithInlineCode helper covering plain text,
single/multiple code spans, empty input, and code-only strings.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: remove white backgrounds from all logo assets
- Remove white backgrounds from clawd-logo.png, clawd-mark.png,
logo192.png, logo512.png — now transparent PNGs
- Convert white strokes to dark (#1a0808) in both PNGs and logo.svg
so segments separate cleanly on any background
- Defringe antialiased edges to eliminate white halos
- Regenerate favicon.ico from transparent source
- Update manifest.json background_color from #ffffff to #0a0a0a
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* consolidate logo assets: delete SVGs, use only PNGs with transparent bg
- Delete public/logo.svg, public/og.svg, src/logo.svg (dead/unused SVGs)
- Remove logo.svg favicon link from __root.tsx (favicon.ico remains)
- Remove white backgrounds from clawd-logo.png and clawd-mark.png
- Convert white strokes to dark (#1a0808), defringe antialiased edges
- Regenerate logo192.png, logo512.png, favicon.ico from clean sources
- Only canonical logo files are now clawd-logo.png and clawd-mark.png
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* style: widen navbar search bar and polish hero section
Let the search bar span the full width between brand and theme toggle
by removing the oversized right-column minimum and theme-toggle min-width.
Widen the hero search container, subtitle, and tighten vertical padding
for a sleeker feel.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: use :is(h2, h3) selector for about-rule-card headings
The /souls page reuses about-rule-card with <h2> elements. Using
:is(h2, h3) ensures both heading levels get styled consistently.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* feat: slot machine Easter egg on hero label triple-click
Triple-clicking "BUILT BY THE COMMUNITY" triggers a casino-style slot
machine across all 3 headline words. Reels spin and stop sequentially
with a 1/13 jackpot chance. Winning fires a confetti celebration with
golden text glow. Auto-resets after the animation completes.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* feat: add cooldown, longer celebration, and Hack x3 lobster jackpot
- 18s cooldown after a win, 3s after a loss to prevent spam
- Win celebration extended to 10s for screenshot opportunities
- Hack x3 jackpot triggers aquatic theme: cyan/teal text glow,
ocean-colored confetti with bubble and claw particles, and the
lobster logo fades in behind the headline
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* feat: tune slot machine odds to 1/25 any jackpot, 1/100 Hack jackpot
Replace pure random picks with controlled probability: 4% chance of
any jackpot per spin, with 25% of jackpots being Hack (= 1% overall).
Non-jackpot spins re-roll accidental triple matches to keep odds exact.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: clean up slot timers on unmount, fix about-grid specificity
Add useEffect cleanup to clear slot machine timers/intervals when
the home route unmounts mid-animation. Fix about-grid media query
specificity by including .about-panel-categories .about-grid to
override the higher-specificity base rule.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
* fix: hide logo, use ClawHub as home link, and clean up rejection categories grid
Comment out the brand logo image for now, rename "Immediate rejection
categories" to "Rejection Categories", remove the featured card variant,
and switch to an auto-fill grid so cards spread evenly at full width.
Add overflow: visible on the categories panel to prevent hover shadow
clipping.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: impose max page width on home page using --page-max (1536px)
Constrain .home-v2-main to max-width: var(--page-max) and center it
with margin-inline: auto. Extend the home page background color to the
full viewport via .app-shell:has(.home-v2-main) for both light and dark
themes so the background bleeds edge-to-edge beyond the content column.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: remove extra footer padding and ensure full-width nav/footer for boxed layout
Zero out the outer .site-footer padding and set background to transparent
on home-v2 pages so the app-shell background bleeds through edge-to-edge.
Remove the redundant light-mode footer background override (app-shell
background already covers it). Nav and footer now visually span full
viewport width while .home-v2-main content stays boxed at --page-max.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: reduce carousel card hover effect and increase track padding
The carousel cards were getting clipped by the parent overflow:hidden
container. Reduce the hover transform from translateY(-4px) scale(1.01)
to translateY(-2px) and shrink box-shadow spread across all theme
variants. Increase carousel track top padding from 4px to 12px to
accommodate the upward shift without cutoff.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: address review feedback — mobile brand, category grid, hover drama
- Keep brand name visible on mobile (remove display:none for
.brand-name-responsive at ≤639px) so the home link is always
discoverable. Add TODO comment on the commented-out logo block.
- Add .about-panel-categories .about-grid to the ≤640px media query
so the category grid correctly collapses to single-column on mobile.
- Bump carousel card hover to translateY(-3px) with 0 6px 24px shadow
for a slightly more dramatic lift — still within the 12px top / 48px
bottom track padding so nothing clips.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* chore: remove unused footer divider element
The site-footer-divider was already hidden via CSS (display: none) on
home-v2 pages. Remove the element entirely since it serves no purpose.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Include static scan results in the skill version security snapshot so inspect/API responses reflect the same moderation-relevant signal already used elsewhere. Also add regression coverage for suspicious, malicious, and static-only scan combinations.
Co-authored-by: davida-ps <232346510+davida-ps@users.noreply.github.com>
Co-authored-by: Luke <92253590+ImLukeF@users.noreply.github.com>
On Windows, opening auth URLs via `cmd /c start` can truncate query parameters because `&` is treated as a command separator. Use `explorer` instead so the browser opener gets the full URL without shell parsing, and cover the Windows spawn args in the CLI UI test.
Co-authored-by: hugh <1012760428@qq.com>
Add and refine styles for the Home V2 UI: introduce navbar search/home styles, motto and headline variants, section copy/eyebrow rules, discovery and categories layouts, and responsive grid stacking. Adjust hv2 color variables (text-secondary/tertiary) and move category border to the grid element; update spacing/alignment for carousel and section headers. Add light/dark theme overrides to improve navbar, tabs and search contrast and hover states. Misc minor typographic and spacing refinements for a more cohesive Home V2 appearance.
* build(deps-dev): bump vite in the npm_and_yarn group across 1 directory (#1561)
Bumps the npm_and_yarn group with 1 update in the / directory: [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite).
Updates `vite` from 8.0.1 to 8.0.5
- [Release notes](https://github.com/vitejs/vite/releases)
- [Changelog](https://github.com/vitejs/vite/blob/main/packages/vite/CHANGELOG.md)
- [Commits](https://github.com/vitejs/vite/commits/v8.0.5/packages/vite)
---
updated-dependencies:
- dependency-name: vite
dependency-version: 8.0.5
dependency-type: direct:development
dependency-group: npm_and_yarn
...
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* fix: detect generated-source template injection in skill scans (#1597)
* fix: detect exposed resource identifiers in skill scans (#1598)
* fix: restore ci checks after lockfile drift
* refactor: address actionable review cleanup (#1601)
* fix: prevent starring soft-deleted skills and fix star count reconciliation (#1605)
* feat: Add support for Chinese Japanese and Korean(CJK) skills search (#1596)
Merged via squash.
Prepared head SHA: ab58f01be7
Co-authored-by: pq-dong <40668796+pq-dong@users.noreply.github.com>
Co-authored-by: momothemage <35096042+momothemage@users.noreply.github.com>
Reviewed-by: @momothemage
* docs: document CLI config paths across platforms (#1252)
* docs: document CLI config paths across platforms
* docs: clarify legacy config fallback
---------
Co-authored-by: ImLukeF <92253590+ImLukeF@users.noreply.github.com>
* fix: point plugin metadata help link to OpenClaw docs (#1399)
* fix: point plugin metadata help link to OpenClaw docs
* fix: open plugin metadata docs in a new tab
* fix(cli-auth): ensure fallback token renders before redirect on Windows/Chrome (#1486)
* fix(cli-auth): ensure fallback token renders before redirect on Windows/Chrome
React batches state updates, so setToken() and window.location.assign()
previously raced: the navigation could fire before React re-rendered the
fallback token UI. On Chrome/Windows this means a failed http:// redirect
(ERR_CONNECTION_REFUSED, HTTPS-first interference) would replace the page
with an error screen before the user ever saw the token.
Use flushSync() to render the token synchronously, then attempt
window.location.assign(). If the redirect fails the token and a "Retry
redirect to CLI" link are already painted on screen.
Fixes#1469
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* test: cover cli auth fallback redirect
---------
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-authored-by: ImLukeF <92253590+ImLukeF@users.noreply.github.com>
* fix: reduce souls browse overfetch (#1637)
* fix: improve admin user search coverage (#1466)
* fix admin user search coverage
* fix admin user search without full table scan
* feat: include stats in package detail API response
Expose package detail stats through the shared API contract and the app client.
This lands the original package detail stats work and folds in the follow-up cleanup to keep the response shape sourced from the shared schema instead of a hand-maintained app-local type.
Co-authored-by: Saurabh Jain <saurabhjain1592@gmail.com>
* test: cover package detail stats response
* fix: normalize misleading MIME types for text files
* feat: modernize clawhub app store
---------
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Luke <92253590+ImLukeF@users.noreply.github.com>
Co-authored-by: Momo <35096042+momothemage@users.noreply.github.com>
Co-authored-by: pqdong <40668796+pq-dong@users.noreply.github.com>
Co-authored-by: Jholly <xiangjunkong90@gmail.com>
Co-authored-by: loong <46096863+robinspt@users.noreply.github.com>
Co-authored-by: Yaovi <dkpoga@gmail.com>
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-authored-by: Saurabh Jain <saurabhjain1592@gmail.com>
* feat: redesign ClawHub marketplace with modern utility store theme
Update styles.css and index.tsx for new modern design
Co-authored-by: Val Alexander <68980965+BunsDev@users.noreply.github.com>
* style: polish marketplace UI with modern design updates
Co-authored-by: Val Alexander <68980965+BunsDev@users.noreply.github.com>
* fix: resolve 500 errors in TanStack Router loaders
Co-authored-by: Val Alexander <68980965+BunsDev@users.noreply.github.com>
* fix: resolve SSR error bubbling in TanStack Router
Ensure loader errors don't escape SSR and hydrate correctly.
Co-authored-by: Val Alexander <68980965+BunsDev@users.noreply.github.com>
* feat: handle errors in Package API calls to prevent SSR and HMR errors
Co-authored-by: Val Alexander <68980965+BunsDev@users.noreply.github.com>
* feat: update branding to OpenClaw's black, white, and red color scheme
Implement new color scheme across dark, light themes and interactive elements
Co-authored-by: Val Alexander <68980965+BunsDev@users.noreply.github.com>
* feat: use Vite's native tsconfig paths
Replace deprecated plugin with native option and remove unused import.
Co-authored-by: Val Alexander <68980965+BunsDev@users.noreply.github.com>
* fix: add defensive checks in fetchPluginCatalog
Ensure proper handling of undefined and unexpected API responses.
Co-authored-by: Val Alexander <68980965+BunsDev@users.noreply.github.com>
* fix: add defensive checks to PluginsIndex for SSR errors
Handle undefined loader data in PluginsIndex component.
Co-authored-by: Val Alexander <68980965+BunsDev@users.noreply.github.com>
* refactor: optimize skill detail page layout
Redesign skill detail page to maximize space, remove sidebar, create metadata bar, and add responsive breakpoints.
Co-authored-by: Val Alexander <68980965+BunsDev@users.noreply.github.com>
* fix: add global overflow protection to detail pages
Add overflow prevention for text elements and links.
Co-authored-by: Val Alexander <68980965+BunsDev@users.noreply.github.com>
* feat: highlight parent tabs with activePathPrefixes
Add activePathPrefixes to NavItem and update navigation to highlight parent tabs.
Co-authored-by: Val Alexander <68980965+BunsDev@users.noreply.github.com>
* feat: add user preferences customization section
Add 'usePreferences' hook and new Switch component; enhance settings page with Customization section.
Co-authored-by: Val Alexander <68980965+BunsDev@users.noreply.github.com>
* feat: optimize layout and create DESIGN.md
Fix orphan cards, enforce equal card heights, add branding accents, improve visual hierarchy, add responsive breakpoints, create design document
Co-authored-by: Val Alexander <68980965+BunsDev@users.noreply.github.com>
* Update src/routes/plugins/index.tsx
Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
* Update src/components/layout/Container.tsx
Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
---------
Co-authored-by: v0 <v0[bot]@users.noreply.github.com>
Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
Expose package detail stats through the shared API contract and the app client.
This lands the original package detail stats work and folds in the follow-up cleanup to keep the response shape sourced from the shared schema instead of a hand-maintained app-local type.
Co-authored-by: Saurabh Jain <saurabhjain1592@gmail.com>
* fix(cli-auth): ensure fallback token renders before redirect on Windows/Chrome
React batches state updates, so setToken() and window.location.assign()
previously raced: the navigation could fire before React re-rendered the
fallback token UI. On Chrome/Windows this means a failed http:// redirect
(ERR_CONNECTION_REFUSED, HTTPS-first interference) would replace the page
with an error screen before the user ever saw the token.
Use flushSync() to render the token synchronously, then attempt
window.location.assign(). If the redirect fails the token and a "Retry
redirect to CLI" link are already painted on screen.
Fixes#1469
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* test: cover cli auth fallback redirect
---------
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-authored-by: ImLukeF <92253590+ImLukeF@users.noreply.github.com>
- Re-throw non-rate-limit errors in plugin loader so route error
boundary handles real failures instead of showing empty results
- Bump requestRef on query clear to invalidate in-flight searches
and prevent stale results from repopulating
- Replace Promise.all with Promise.allSettled in unified search so
one failing provider doesn't blank results from other sources
- Log unexpected errors in unified search catch block
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Reject empty reason strings in setSoftDeleted calls + re-add .catch()
for error feedback (both reported-skills and skill-tools sections)
- Replace useQuery with ConvexHttpClient.query() on /users public
browse page per CLAUDE.md policy
- Add by_active_handle compound index on users table to avoid full
table scan in queryUsersForPublicList
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Keep feature branch UI overhaul (custom CSS) while incorporating
security/stability fixes from main:
- setSoftDeleted now requires moderation reason (runtime-critical)
- moderationNotes displayed in skill detail when available
- Rate limit handling for plugin catalog
- Tailwind @theme block for auto-merged component compatibility
- Capability tag passthrough to SecurityScanResults
- ALL_CATEGORY_KEYWORDS export for skills browse model
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Clear `hasMore` and `nextCursor` when a scan hits the budget but returns no items
- Prevent the client IntersectionObserver from looping on empty auto-load responses
2026-04-06 13:31:33 -05:00
Val Alexanderandgreptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
- Thread capability tags through skills search and public listing
- Add toolbar tag picker and preserve tag state in routing
- Cover tag-filtered search and browse query behavior with tests
- Clear `hasMore` and `nextCursor` when a scan hits the budget but returns no items
- Prevent the client IntersectionObserver from looping on empty auto-load responses
2026-04-05 20:57:34 -05:00
Val Alexanderandgreptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
- Thread capability tags through skills search and public listing
- Add toolbar tag picker and preserve tag state in routing
- Cover tag-filtered search and browse query behavior with tests
- Thread capability tags through skills search and public listing
- Add toolbar tag picker and preserve tag state in routing
- Cover tag-filtered search and browse query behavior with tests
- Surface retryable empty states for plugin catalog and detail pages
- Preserve Retry-After metadata in package API errors
- Add staged-secret scanning and auto-installed git hooks
- Add shared Radix/Tailwind UI primitives and empty/loading/error states
- Modernize route layouts, forms, tabs, nav, and markdown rendering
- Tighten package/auth API behavior and update tests for the new UX
- surface capability tags in the management view
- align tests with updated loading and toggle behavior
- relax package API credential assertion for env-dependent URLs
- Accept unknown error shapes in `ErrorFallback`
- Extract user-facing text from `error.message`, `error.error`, or string values
- Keep a default message when no useful detail is available
- replace react-markdown rendering with a shared Shiki-powered preview
- update skill, soul, and plugin detail views to use the new component
- add markdown preview dependencies and adjust tests
- Add a resetKey prop to `ErrorBoundary` so caught errors clear when navigation changes
- Wrap root children in a pathname-aware boundary to recover from route-level failures
- Add reusable Radix-based UI primitives and layout helpers
- Refresh skill, soul, and dashboard pages with new empty/error/loading states
- Update dependencies for the modernized component stack
Theming (P0):
- Removed all 78 [data-theme="dark"] override selectors (dark is now
default, these were dead code with conflicting warm colors)
- Replaced 56 instances of rgba(255,107,74,x) warm coral with
rgba(255,255,255,x) monochrome equivalents
- Replaced hard-coded warm hex colors (#c35640, #ff6b4a, etc.) with
gray monochrome values
- CSS file reduced from ~6300 to 5909 lines
Touch targets (P1):
- Added min-height: 36px to .btn (was ~24px)
- Added min-height: 36px to .navbar-tab (was ~27px)
- Added min-height: 32px to .sidebar-option and .sidebar-checkbox
- Increased padding on buttons and tabs
Accessibility (P2/P3):
- Comprehensive prefers-reduced-motion: reduce rule — disables all
animations AND transitions for users who prefer reduced motion
- Covers shimmer, fadeIn, fadeUp, and all CSS transitions
Complete visual redesign to a dark, monochrome, terminal-inspired
aesthetic inspired by Warp, modern TUI tools, and blueprint designs.
Color system:
- Default is now dark (#0a0a0a bg, #e0e0e0 ink, #141414 surface)
- All accent colors removed — monochrome only (white as accent)
- Borders use rgba(255,255,255,0.08) for subtle separation
- Light theme available as optional override via [data-theme="light"]
Typography:
- All fonts now IBM Plex Mono (display, body, code all monospace)
- Brand name is lowercase monospace
- Section titles are uppercase monospace with letter-spacing
- Tags and badges use monospace font
Geometry:
- All border-radius reduced to 1-2px (sharp TUI corners)
- No shadows anywhere (--shadow: none)
- No backdrop-filter blur on navbar
- Cards, buttons, inputs all have sharp edges
Components:
- Buttons: transparent bg with border, monospace text
- Primary buttons: white on black (inverted)
- Tags: border-only, no colored backgrounds
- Cards: dark surface with subtle border
- Brand mark: 24px square instead of 28px circle
Layout:
- Replaced category grid with simple quick links
- Removed all warm color references
- Home section titles are small uppercase labels
- Skill list item names use --ink (no accent color)
- Switch light theme from warm beige (#f8f2ed) to neutral white (#fafafa)
with neutral gray ink (#1a1a1a) and borders (rgba black)
- Switch dark theme from warm brown to neutral dark (#111111) with
neutral gray borders (rgba white)
- Replace fake category grid (8 keyword-search cards) with curated
quick links (Most starred, New this week, Browse plugins, Staff picks)
- Add "What are skills?" explainer paragraph below hero CTAs
- Add fadeIn animation on results list when data arrives
- Add "Clear" button in browse results toolbar when filters are active
- Tighten browse layout gap from 24px to 16px
- Import internalMutation from convex/functions (not _generated/server)
to get trigger wrapping per CLAUDE.md rules
- Derive activeCategory from current search query so sidebar category
selection shows correct visual/ARIA state
- Push moderationStatus filter server-side in repairGlobalStats to
avoid full table scan
- Reset skillCount/pluginCount to 0 in useUnifiedSearch catch block
to prevent stale badge values after search errors
- Add textarea-based clipboard fallback for unsupported contexts
- Show copied and failed states in the copy button
- Add labels and formatting for plugin capability values
2026-04-01 09:24:00 -05:00
Val Alexanderandgreptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
- Rework the hero into a two-column grid with sidebar actions and metadata
- Move version, badges, and security scan content into clearer sections
- Add responsive spacing tweaks for mobile navigation
- Rework plugin list filters into a more compact mobile-friendly toolbar
- Expand plugin detail pages with install, capability, compatibility, and verification sections
- Tighten shared toggle and scan result spacing for the new layout
- Reduce navbar padding and gaps on small screens
- Compact toggle group, theme buttons, and user trigger
- Hide extra dashboard summary text on narrow layouts
- Wrap long URLs, token strings, and changelogs to prevent overflow
- Make key controls and dashboard grids shrink more gracefully on small screens
- Relax textarea and file viewer sizing for better mobile usability
Bring all interactive elements to 44px WCAG touch target minimum,
fix diff editor horizontal scroll on mobile, stack skills table on
small phones, add 480px breakpoint for tiny devices, and tighten
spacing across dashboard/management/dialog components.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* feat: add ability to delete version tags from skill detail page
- Add deleteTags mutation to convex/skills.ts (protects 'latest' tag)
- Add delete button (×) on each tag in SkillHeader (visible to owner/moderator only)
- Wire up onTagDelete prop from SkillDetailPage to SkillHeader
- Add .tag-delete CSS styles
Closes: version tags accumulate across publishes with no way to remove them
* fix: address review feedback on deleteTags PR
- Add window.confirm() before deleting a tag (P2: missing confirmation)
- Skip db.patch when no tags are actually removed (P2: unnecessary write)
- Add test suite for deleteTags mutation covering:
- Tag deletion with latest protection
- No-op when only latest is targeted
- No-op for nonexistent tags
- Permission check for non-owner
- Moderator access on other user's skill
- Skill not found error
* fix: repair deleteTags test harness
* fix: satisfy deleteTags test typecheck
---------
Co-authored-by: Jeff <tjefferson518@gmail.com>
* feat: redesign plugins page and skills list view
Redesigned the plugins page with a cleaner toolbar (pill search,
toggle filter buttons) and simplified card layout. Added a proper
table-style list view for skills with skill name, version, summary,
and author avatar columns. Also polished the sort dropdown with a
chevron indicator, added card shadows for better separation, and
tightened up the theme toggle and sign-in button.
* feat: add publisher org ownership
* feat: migrate legacy publisher handles to orgs
---------
Co-authored-by: Peter Steinberger <steipete@gmail.com>
- Rename /packages route to /plugins with /packages redirecting
- Nav links now say "Plugins" and point to /plugins
- Plugins page only shows code-plugin and bundle-plugin (no skills)
- "Official only" → "Verified only"; blue checkmark badge for verified publishers
- Compact card footer: "by author · v1.2.3" inline with verified badge
- Remove duplicate Skill/Skill tag bubbles
- Update tests to match new routes and behavior
- Enhanced AGENTS.md with clearer project structure and development commands.
- Updated CHANGELOG.md to reflect recent fixes and additions.
- Improved formatting in CONTRIBUTING.md for better readability.
- Adjusted package.json and configuration files for consistent command structure.
- Refined README.md and VISION.md for clarity and organization.
- Standardized code formatting in various TypeScript files for consistency.
These changes aim to enhance documentation clarity and maintainability across the repository.
When a publish-time backup and the cron backup push concurrently, the
second push fails with "not a fast forward" because the branch moved.
Split backupSkillToGitHub into two phases:
1. Create blobs (storage downloads) — done once
2. Fetch ref, build tree, commit, push — retried up to 3x on conflict
Same retry applied to deleteGitHubSkillBackup.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The schema import in skills.ts (needed for getPage) transitively pulls
in authTables from @convex-dev/auth/server. All test files that import
from skills.ts need this export in their mock.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Instead of scanning 500+ rows of the sort index and filtering for
highlighted skills in JS (which fails when highlighted skills are
sparse among 25K+ rows), query the skillBadges table via by_kind_at
index to find highlighted skill IDs directly, then look up their
digests. Also simplifies the non-highlighted path to a single getPage
call since the multi-round loop was only needed for highlighted.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Remove the V3 fallback branch and useV4 parameter from
useSkillsBrowseModel since V4 is verified and the only path used.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- /skills browse page now uses listPublicPageV4 via useV4 flag
- Homepage popular skills section uses listPublicPageV4
- Remove /skillsv4 and /test-v4 temporary test routes
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
When V4 returns hasMore=true but nextCursor=null, the next load-more
call would pass cursor=null, triggering the replace branch instead of
append. Treat this edge case as 'done' to prevent silent list reset.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Root cause of V4 returning empty in production: `getPage()` ignores the
`indexFields` property at runtime and always calls `getIndexFields(table,
index, schema)`. Without `schema`, it threw "schema is required" silently.
Fixes:
- Pass `schema` instead of `indexFields` to `getPage()`
- Use `absoluteMaxRows` instead of `targetMaxRows` (ignored when
`endIndexKey` is provided)
- Remove unused `DIGEST_INDEX_FIELDS` constant
Staged release:
- Add `/skillsv4` route (same UI as `/skills` but using V4 backend)
- Add `/test-v4` debug page for raw V4 API testing
- Add `useV4` flag to `useSkillsBrowseModel` hook
- Keep `/skills` on V3 until V4 is verified in production
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Replace `import schema from './schema'` with inline DIGEST_INDEX_FIELDS
lookup, avoiding @convex-dev/auth/server transitive dependency in tests
- Gut V1 test to match gutted handler (single stub verification)
- Fix load-more test to use V4 response shape
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Replace V2 test suite with single stub verification (no DB reads)
- Update skills-index tests: paginationOpts → cursor/numItems,
isDone/continueCursor → hasMore/nextCursor
- Update default convexHttpMock to return V4 shape
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Remove sortToIndex and getTrendingEntries (only used by gutted V1)
- Remove unused leaderboard imports
- Rename shadowed 'v' parameter to 'val' in encode/decodeIndexKey
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Use tagged object encoding for undefined index key values instead of
plain string sentinel to avoid collisions
- Add try/catch in decodeIndexKey, treat malformed cursors as first page
- When highlightedOnly filters out all fetched rows, advance nextCursor
to last fetched position instead of returning null (prevents restart loop)
- Update V3 JSDoc to reflect its current role
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
getPage walks the entire index unless bounded. Without constraining
startIndexKey/endIndexKey to the equality prefix ([undefined] for base,
[undefined, false] for nonsuspicious), desc order returns soft-deleted
items first, producing empty pages.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Use convex-helpers getPage() instead of .paginate() so that page cursors
are derived from actual index field values. Two users requesting the same
page now produce identical query args, enabling shared query caching.
- Add listPublicPageV4 with IndexKey-based cursor encoding
- Gut listPublicPage (V1) and listPublicPageV2 to return empty results
- Keep listPublicPageV3 intact for any remaining subscribers
- Switch frontend browse model and homepage to V4
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Duplicate of listPublicPageV2 as a separate Convex function. Frontend
switched to V3 so any remaining V2 calls in the dashboard are from
stale browser tabs with old bundles.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Cast page item to Record to access latestVersion property that isn't
on the narrow return type.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Remove fallback expectations — pre-backfill rows without owner fields
are now skipped, and missing latestVersionSummary returns null instead
of fetching from skillVersions.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
listPublicPageV2 was calling buildPublicSkillEntries which fell back to
ctx.db.get() for owners and versions, adding skills/users/skillVersions
to the query's read set. Now that digest rows have owner fields and
latestVersionSummary backfilled, we can construct the full response from
skillSearchDigest alone — writes to other tables no longer bust the cache.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- search.test: expect users lookup NOT called when digest has owner data
- listPublicPageV2.test: expect by_nonsuspicious_* indexes when nonSuspiciousOnly
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- P2: When digestToOwnerInfo returns { owner: null } (deactivated/deleted
user), fall back to live users table lookup instead of dropping the skill
from results. Applies to hydrateResults, lexicalFallbackSkills, and
buildPublicSkillEntries.
- P1: If compound index returns zero results on the first page (isSuspicious
not yet backfilled), fall back to base index with JS filtering so the
homepage isn't empty during migration.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Encodes the patterns learned from bandwidth optimization so AI coding
assistants get them right from the start — digest owner fields over
users table reads, compound indexes over JS filtering, one-shot fetches
for public pages, change detection in triggers.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Three bandwidth fixes:
1. search.hydrateResults / lexicalFallbackSkills: use digestToOwnerInfo()
to resolve owner data from the digest instead of ctx.db.get(ownerUserId)
on the users table. Eliminates users from the read set for ~99% of
search calls (8+ GB in 72h).
2. skills.listPublicPageV2: use compound by_nonsuspicious_* indexes when
nonSuspiciousOnly is true, filtering isSuspicious at the DB level
instead of scanning and discarding in JS (30+ GB in 72h).
3. maintenance.backfillDigestIsSuspicious: targeted backfill that sets
isSuspicious on digest rows where it's undefined, using the digest's
own moderationFlags/moderationReason. Must run before compound indexes
take effect.
Deploy sequence:
1. Deploy functions
2. npx convex run maintenance:backfillDigestIsSuspicious --prod
3. Compound indexes work immediately for backfilled rows
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* test(cli): add tests for install --force rm ordering
Add three tests to verify that --force install does not delete the local
skill directory before pre-download checks have passed:
- rm not called when skill is malware-blocked
- rm not called when API fetch fails (skill not found)
- rm called before download when all checks pass (happy path)
* fix(cli): move rm after checks in install --force
Previously, install --force deleted the local skill directory before
fetching metadata or running moderation checks. If any check failed
(skill deleted, malware-blocked, not found), the local copy was lost.
This is inconsistent with cmdUpdate, which already checks before
deleting. Move rm to after all checks pass, just before download.
This does not alter the meaning of --force; it narrows the window in
which data is removed before the command has confirmed the replacement
is viable.
* fix(cli): validate forced install version before rm
---------
Co-authored-by: Jonathan Deamer <202770+jonathandeamer@users.noreply.github.com>
- Replace usePaginatedQuery mocks with convexHttp.query mocks in
browse page tests
- Update load-more test to use convexHttp instead of loadMorePaginated
- Update backend tests to reflect new behavior: getOwnerInfo skips
db.get when digest has pre-resolved owner data
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
listPublicPageV2 is the #1 DB bandwidth consumer (31GB+ spikes) because
usePaginatedQuery creates reactive subscriptions. Any write to
skillSearchDigest invalidates all active subscribers simultaneously —
a thundering herd. This replaces reactive subscriptions with one-shot
ConvexHttpClient.query() calls on both the /skills browse page and the
home page, eliminating the reactive read set entirely.
Also short-circuits getOwnerInfo() to return pre-resolved owner data
from the digest before hitting ctx.db.get(ownerUserId), removing the
users table from the reactive read set for listPublicPageV2.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Prevents unhandled promise rejections on transient network/backend
failures. Empty state is an acceptable fallback for the home page.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The home page used useQuery for highlighted and popular skills, creating
live reactive subscriptions that re-executed on every skillSearchDigest
write (crons, triggers). Since the home page doesn't need live updates,
switch to one-shot convex.query() fetches on mount to eliminate unnecessary
reactive invalidation.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Existing skillSearchDigest rows created before the latestVersionSummary
denormalization lack the field, causing listPublicPageV2 to fall back to
reading full skillVersions docs (~6KB each, 14MB per call).
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The by_active_updated index orders by updatedAt which is mutable —
rows can shift during a paginated scan causing double-counting or
skipping. Default _creationTime ordering is immutable and stable.
isPublicSkillDoc already filters softDeletedAt in JS.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The skills trigger unconditionally wrote to skillSearchDigest on every skill
mutation, even when only stat fields were updated with identical values.
This caused every cron that patches skills (stat sync, backfill) to invalidate
all active listPublicPageV2 subscriptions, triggering massive re-execution
storms (55 GB bandwidth spikes).
Now upsertSkillSearchDigest compares new fields against the existing row and
skips the write when nothing changed. This prevents unnecessary reactive
invalidation while still keeping the digest current for real changes.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The daily updateGlobalStatsInternal cron read all ~19K skillSearchDigest docs
(17.8 MB) in a single mutation, exceeding the Convex bytes-read limit.
Switch to an action-based approach that pages through the table in ~1000-doc
queries (each ~900 KB), then writes the result in a separate mutation.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Add delayMs param, stop flag via skillStatBackfillState, and status
query so backfill speed can be adjusted without redeploying.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
digestToOwnerInfo now checks for profile data (name/displayName/image)
in addition to handle when deciding whether to return an owner object.
Handle-less visible users get their full profile; deactivated users
(no handle AND no profile data) correctly get owner: null.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Write ownerHandle: '' (not undefined) for visible users without a
handle and for deactivated users, so digestToOwnerInfo can distinguish
"not backfilled" (undefined → fallback to DB) from "backfilled but
no handle" ('' → use userId fallback, skip DB read).
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Prevent baking deactivated/deleted user info into the digest.
The trigger and backfill now write undefined for owner fields
when the owner is not visible, matching the live query path.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
listPublicPageV2 (419 GB) and search.hydrateResults (1.76 TB) both read
full users docs for every unique owner. Denormalize ownerHandle, ownerName,
ownerDisplayName, ownerImage into the digest so query paths skip ctx.db.get
entirely. One extra read per skill mutation (rare) vs eliminating reads on
every query (very frequent).
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Use the public user serializer for `skills.getBySlug` so Convex query responses no longer expose private account metadata like email addresses from public endpoints.
Made-with: Cursor
Verifies that old digest rows without latestVersionSummary correctly
fall back to ctx.db.get(latestVersionId) for version data.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Eliminates ~9MB of skillVersions reads per listPublicPageV2 call by
copying latestVersionSummary from skills into the digest via the
existing trigger. Old rows without the field fall back to fetching
the full version doc.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: allow ownership healing when previous owner is deleted/banned
The GitHub identity check in `publishOrUpdateSkillInternal` and
`checkSlugAvailability` was unreachable when the skill owner's account
was deleted or deactivated. This created a permanent deadlock: the
original owner could not sign in, and no one (not even the same GitHub
user with a new Convex Auth record) could reclaim the slug.
Move the `canHealSkillOwnershipByGitHubProviderAccountId` check before
the deleted/deactivated early-exit so ownership healing still works for
duplicate Convex Auth user records where the old record was later banned.
When healing is not possible (different GitHub identity or missing
auth records), show a message directing the user to contact
security@openclaw.ai instead of a generic "Slug is already taken".
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* chore: drop unused skills sort index map
---------
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-authored-by: Nimrod Gutman <nimrod.gutman@gmail.com>
* fix: surface auth errors from OAuth callback to the UI
When `afterUserCreatedOrUpdated` throws a `ConvexError` (e.g. banned or
deleted account), the error was silently discarded — the user was
redirected back to the sign-in page with no feedback.
Parse the error from the OAuth callback URL hash fragment in the
`ConvexAuthProvider` `replaceURL` callback and expose it via a
lightweight `useAuthError` hook (backed by `useSyncExternalStore`).
Display the error next to the sign-in button in both Header and the
CLI auth page, and add `.catch()` to `signIn()` calls to avoid
unhandled promise rejections.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* fix(auth): handle oauth callback sign-in errors
---------
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-authored-by: Nimrod Gutman <nimrod.gutman@gmail.com>
Most skillSearchDigest rows have isSuspicious: undefined (not false),
so eq('isSuspicious', false) returns zero results. Revert to regular
indexes with JS filtering until the field is backfilled.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Add by_nonsuspicious_* indexes to skillSearchDigest (matching the
existing ones on the skills table) so nonSuspiciousOnly filtering
happens at the index level instead of in JS. This eliminates empty
filtered pages without needing a multi-paginate loop.
TODO: once deployed and stable, remove the duplicate by_nonsuspicious_*
indexes from the skills table (no longer queried by listPublicPageV2).
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Convex only allows a single .paginate() call per query function.
The while loop that skipped empty filtered pages violated this
constraint, causing "ran multiple paginated queries" errors on prod.
Remove the loop — clients will handle empty filtered pages by
requesting the next page via continueCursor.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The rebuildTrendingLeaderboardInternal mutation queries ~31,500
skillDailyStats docs (7 days × ~4,500/day) in a single transaction,
hitting Convex's 32K document read limit on prod (71 errors/72h).
Split into action → query → mutation pattern so each day's query runs
in its own transaction with its own 32K budget:
- getDailyStats (internalQuery): reads one day's stats
- writeTrendingLeaderboard (internalMutation): writes leaderboard + prunes
- rebuildTrendingLeaderboardAction (internalAction): orchestrates the above
The old single-mutation path is kept as a fallback.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Problem:
Skills using legitimate API integrations (process.env + fetch) were
permanently flagged as malicious due to CREDENTIAL_HARVEST being
classified as a malicious-level reason code. Once flagged, skills could
not recover to normal status even after clean VT and OpenClaw scans,
because:
1. syncModerationReasons used a partial-update path that only patched
moderationReason without reconciling moderationFlags, moderationStatus,
or moderationVerdict.
2. Static scan "you are now a/an" regex over-matched common skill
preambles, adding spurious INJECTION_INSTRUCTIONS flags.
3. No mechanism existed for external scanner results (VT/LLM) to
override static suspicious findings when both independently
confirmed the skill as safe.
Solution:
- Downgrade CREDENTIAL_HARVEST from malicious.env_harvesting to
suspicious.env_credential_access — env+network is suspicious, not
malicious, for API integration skills (moderationReasonCodes.ts).
- Remove "you are now a/an" regex from markdown scanning to stop
false INJECTION_INSTRUCTIONS flags (moderationEngine.ts).
- Add external scanner override in buildModerationSnapshot: when both
VT and LLM report clean/benign, demote suspicious.* static codes
from verdict calculation while preserving malicious.* codes and
keeping all findings in evidence for transparency (moderationEngine.ts).
- Route syncModerationReasons through approveSkillByHashInternal for
rows with sha256hash, ensuring full moderation state reconciliation.
For legacy no-hash rows: malicious → escalateSkillByIdInternal
(immediate hide); clean/suspicious → updateSkillModerationReasonInternal
(partial fix, matches pre-existing behavior) (vt.ts, skills.ts).
- Add escalateSkillByIdInternal mutation for atomic emergency
escalation by skillId (sets moderationReason, moderationFlags,
moderationStatus, hiddenAt, isSuspicious) (skills.ts).
- Ensure approveSkillByHashInternal explicitly hides malicious skills
by setting moderationStatus to 'hidden' (skills.ts).
- Bump MODERATION_ENGINE_VERSION to v2.1.0.
Frontend:
- Add StaticAnalysisDetail component to display static scan findings
with severity-aware styling (SkillSecurityScanResults.tsx).
- getStaticGuidance now accepts vtStatus/llmStatus and shows "Confirmed
safe by external scanners" (benign/green) when both are clean, instead
of always showing yellow "Patterns worth reviewing" for critical
severity findings.
- Render SecurityScanResults and disclaimer when only static findings
are present (SkillHeader.tsx).
Testing:
- 7 new unit tests in moderationEngine.test.ts covering:
- CREDENTIAL_HARVEST downgrade (suspicious, not malicious)
- "you are now" no longer flagged in markdown
- "ignore previous instructions" still flagged
- buildModerationSnapshot: VT+LLM clean demotes suspicious codes
- buildModerationSnapshot: malicious codes preserved despite clean VT+LLM
- Single-scanner-clean does not demote suspicious codes
- VT suspicious + LLM clean does not demote suspicious codes
- All existing tests pass with engine version bump to v2.1.0.
Follow-up needed (not in this commit):
- One-time backfill for already-misflagged skills (cursor-based,
re-run approveSkillByHashInternal on isSuspicious=true + clean VT).
Made-with: Cursor
Both functions were hitting Bytes Read Limit errors scanning the full
skills table (~1.9KB/doc × 9K docs ≈ 17MB). Switch to the lightweight
skillSearchDigest table (~800 bytes/row) which carries all fields
needed by toPublicSkill/isPublicSkillDoc/isSkillSuspicious.
- Add 5 sort indexes to skillSearchDigest matching the ones used by
SORT_INDEXES (by_active_created, by_active_name, by_active_stats_*)
- listPublicPageV2: query skillSearchDigest, map via digestToHydratableSkill
- countPublicSkillsForGlobalStats: query skillSearchDigest
- Widen buildPublicSkillEntries/filterPublicSkillPage to HydratableSkill[]
- Guard latestVersionSummary access (digest rows don't carry it)
- Update test mocks to expect skillSearchDigest table
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Switches the 500-row lexicalFallbackSkills scan from full skill docs
(~3-5KB each) to lightweight digest rows (~800 bytes each), reducing
DB read bandwidth by ~75%.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Build the seen-ID set from vector results rather than only successful
hydrations, so soft-deleted and suspicious embeddings aren't re-hydrated
on each candidate-limit expansion loop iteration.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Replace ~28 manual syncSkillSearchDigest/upsertSkillSearchDigest calls
across 4 files with a single Triggers handler in convex/functions.ts
that fires automatically on every skills table write. This eliminates
the risk of new mutations silently breaking digest consistency.
- Add convex-helpers as direct dependency
- Create convex/functions.ts wrapping mutation/internalMutation with triggers
- Update all 39 convex modules to import from ./functions
- Remove syncSkillSearchDigest from lib (no longer needed)
- Add normalizeId mock to test db objects for trigger wrapper compat
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Add syncSkillSearchDigest calls to 6 maintenance mutations that patch
digest-relevant fields without syncing (applyEmptySkillCleanup,
applySkillBadgeBackfillPatch, upsertSkillBadgeRecord,
backfillDenormalizedBadges, backfillIsSuspicious, applySkillBackfillPatch)
- Replace unsafe `as unknown as Doc<'skills'>` cast with typed
HydratableSkill interface and digestToHydratableSkill mapper — compiler
now catches field drift between digest and skill doc
- DRY up extractDigestFields/digestToHydratableSkill with shared
SHARED_KEYS array and pick() helper
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
When a skill is hard-deleted, syncSkillSearchDigest now removes the
corresponding digest row instead of silently no-oping. Also adds
skillSearchDigest table handling to reclaim test mock.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
DRY up duplicated validator definitions (forkOf, badges, stats, moderationStatus)
into shared constants reused by both tables to prevent schema drift.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
hydrateResults reads full skill docs (~3-5KB each) but only needs ~800
bytes for toPublicSkill/isPublicSkillDoc/isSkillSuspicious. Add a
lightweight skillSearchDigest projection table that is kept in sync by
all skill mutation paths.
Also fix the searchSkills while loop to incrementally hydrate only new
embedding IDs on each expansion instead of re-hydrating all candidates
from scratch (475 → 250 reads per search).
Expected impact: ~7x bandwidth reduction for hydrateResults
(495 GB → ~70 GB at current traffic).
Post-deploy: npx convex run maintenance:backfillSkillSearchDigestInternal --prod
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The static OG image still said "ClawdHub" and "clawdhub.com" — regenerated
from the already-correct og.svg source.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Add missing sha256 field to file mocks in moderation.test.ts
- Accept softDeletedAt param in makeSkillDoc in search.test.ts
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
When both filters are active, use the nonsuspicious index for isSuspicious
and apply highlightedOnly as a JS filter on top, instead of scanning the
full table with both filters in JS.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Restore the NONSUSPICIOUS_SORT_INDEXES map and index branching logic that
was lost during the PR #572 merge. When nonSuspiciousOnly is set, queries
now use by_nonsuspicious_* indexes with isSuspicious=false in the predicate
instead of scanning the full table and filtering in JS — eliminating
bytesReadLimit errors under load.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The --limit flag under the 'explore' command's Flags section was
missing the proper two-space indentation, making it inconsistent
with other flag lists in the document.
- Add Node.js v18/20/22/24 prerequisite (Convex backend rejects v25+)
- Remove duplicate CONVEX_SITE_URL from .env.local example
- Reorder steps so Convex backend starts before auth/JWT setup
- Add "Set backend environment variables" section (bunx convex env set)
- Clarify that AUTH_GITHUB_ID/SECRET and SITE_URL must be set on the
Convex backend, not just in .env.local
- Make frontend port explicit (bun run dev -- --port 3000)
- Add updateGlobalStatsInternal step after seeding
The nonsuspicious index fallback now fires on any page (not just the
first) and reuses the client's cursor via stale-cursor recovery. This
prevents pagination from breaking when a SORT_INDEXES cursor is sent
back to the NONSUSPICIOUS_SORT_INDEXES path on page 2+.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Fix P1: remove !result.isDone guard from listPublicPageV2 backfill
fallback so it fires when the nonsuspicious index is empty (isDone=true)
- Fix updateTags to update latestVersionSummary when repointing latest tag
- Parallelize leaderboard daily queries with Promise.all
- Over-fetch stale-reason candidates (2x limit) before VT filtering
- Reconcile existing latestVersionSummary in backfill instead of skipping
- Add _creationTime approximation comment
- Rebuild schema dist to include author field on ClawdisSkillMetadata
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The explicit ClawdisSkillMetadata interface (needed because ArkType's
[inferred] doesn't resolve all fields) now has a keyof-based type guard
that triggers a compile error if the interface keys drift from the schema.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Replace ArkType `[inferred]` type alias for ClawdisSkillMetadata with
an explicit interface so TS can see envVars/dependencies/author/links
- Extract listBySkillHandler from comments.ts so tests can call it
directly without accessing private _handler property
- Rebuild packages/schema dist output
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Phase 1: Add `by_moderation` compound index and rewrite 8 cron query
functions to use `.withIndex()` instead of `.filter().collect()` full
table scans (~6 GB/day saved).
Phase 2: Denormalize `isSuspicious` onto skills table with 6 compound
indexes so `listPublicPageV2` can filter at the index level instead of
paginating the entire table (~1 TB/day saved). Includes backfill
mutation and write-path updates across all moderation mutations.
Phase 3: Add `latestVersionSummary` denormalization to avoid reading
full ~6.4 KB `skillVersions` docs on list pages (~500 GB/day saved).
Phase 4: Split trending leaderboard query to one day at a time to stay
under 32K doc limit. Reduce global stats recount from hourly to daily
since delta tracking handles real-time accuracy (~400 MB/day saved).
Phase 5: Add "Convex Query & Bandwidth Rules" section to AGENTS.md.
Backfill commands (run after deploy):
bunx convex run maintenance:backfillIsSuspiciousInternal
bunx convex run maintenance:backfillLatestVersionSummaryInternal
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Fixes#209 by removing overly broad regex patterns that flag legitimate
authentication and payment integration skills.
## Problem
Skills like openbotauth (OAuth identity verification) were being flagged
as suspicious because they mention "token", "api key", or "password" in
their description or metadata. The regex scanner was too aggressive,
catching legitimate auth flows alongside actual threats.
## Solution
Removed three overly broad patterns:
- `suspicious.secrets` - flagged ANY mention of token/api key/password
- `suspicious.crypto` - flagged ANY mention of wallet/seed phrase/crypto
These are common in legitimate skills:
- OAuth skills mention "token" for authentication flows
- API integrations mention "api key" for service credentials
- Database skills mention "password" for connections
- Crypto wallet skills mention "seed phrase" for key management
The LLM evaluator already handles credential proportionality analysis
(section 4 of security prompt). The regex scan should only catch
ACTUAL malicious patterns, not keywords that appear in legitimate contexts.
## What Still Gets Flagged
Kept patterns that catch real threats:
- `suspicious.keyword` - malware, stealer, phishing, keylogger
- `suspicious.webhook` - discord/slack webhooks (data exfiltration)
- `suspicious.script` - curl | bash (arbitrary code execution)
- `suspicious.url_shortener` - bit.ly etc (URL obfuscation)
## Testing
- Added 18 comprehensive tests for pattern detection
- Verified OAuth skills (openbotauth, trello) are NOT flagged
- Verified malicious patterns ARE still flagged
- All 418 existing tests pass
## Security Impact
This does NOT weaken security:
- LLM evaluator still analyzes credential proportionality
- Actual malicious patterns (webhooks, curl|bash, etc) still caught
- Only removes false positives on legitimate auth keywords
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
onQueryChange called navigate() on every keystroke to sync the query
to the URL. Each navigate triggers history.replaceState, TanStack
Router re-evaluation, and useSearch() invalidation, causing multiple
re-renders per keystroke.
Keep setQuery() immediate so the controlled input stays responsive,
but debounce the navigate() call at 220 ms (matching the existing
search-action debounce). Cancel the pending timer when search.q
changes externally (browser back/forward) to prevent the debounced
navigate from overwriting the external URL change.
Made-with: Cursor
Replace the useEffect + useRef approach for setting webkitdirectory/
directory attributes with a ref callback that sets the attributes
every time the input element is mounted. This ensures folder selection
mode persists after page refresh, where React hydration could strip
the non-standard attributes.
Also removes the @ts-expect-error JSX props since the attributes are
now set imperatively via the ref callback.
When VirusTotal returns scan results with AV engine stats but no Code Insight
AI analysis, the skill status was stuck on 'Pending'. This fix adds fallback
logic to check last_analysis_stats (malicious/suspicious/harmless/undetected)
to determine scan status.
Functions updated:
- pollPendingScans: Check AV engines before requesting rescan
- backfillPendingScans: Check AV engines before marking as no results
- rescanActiveSkills: Check AV engines before keeping as pending
- backfillActiveSkillsVTCache: Check AV engines before skipping
Fixes#33435
- Increase upload timeout from 15s to 120s for multipart form uploads
(apiRequestForm and curl-based form upload). Regular API requests
remain at 15s.
- Improve timeout error message from bare "Timeout" to
"Request timed out after Ns" so users know what happened.
- Normalize non-Error throws (e.g. DOMException from AbortController
across runtimes) into proper Error instances, preventing the
misleading "Non-error was thrown" message from p-retry.
- Preserve the original error as `cause` on the wrapped Error.
cmdSearch and cmdExplore were not calling getOptionalAuthToken()
and did not pass the token to apiRequest, unlike install/update/uninstall.
This caused 'missing API token' errors on registries that require auth
(e.g. private Hermit instances).
parseFrontmatterLevelDeclarations did not handle the requires block
(env, bins, anyBins, config) or primaryEnv when declared at the
top level of SKILL.md frontmatter without a metadata.openclaw wrapper.
This caused the security scanner to always show "Required env vars: none"
for skills using that format, triggering false-positive suspicious flags.
Also extends the evalCtx.homepage fallback chain to check
clawdis.homepage and clawdis.links.homepage so skills declaring
homepage inside the metadata block are picked up by the scanner.
* feat(registry): support env vars, dependencies, author, and links in skill manifest
Closes#350
Add structured declarations for environment variables, package
dependencies, author identity, and project links to the skill
registry manifest. These fields can be declared in the clawdis
metadata block or as top-level frontmatter keys.
Changes:
- schema: add EnvVarDeclaration, DependencyDeclaration, SkillLinks
types to ClawdisSkillMetadata
- parser: extract envVars, dependencies, author, links from both
clawdis block and top-level frontmatter (fallback for skills
without a clawdis block)
- UI: render env vars with required/optional badges and descriptions,
dependencies with type/version/links, and project links in the
skill detail page install card
- security: update evaluator prompt to recognize envVars alongside
requires.env and primaryEnv
- tests: 7 new test cases covering all declaration formats
* fix(ui): handle unspecified env required state and stable keys
* docs(changelog): credit metadata manifest expansion (#360) (thanks @mahsumaktas)
---------
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* feat(api): expose security evaluation results
- Add security field to skill version API responses
- Map llmAnalysis database field to public API format
- Display security info in CLI inspect command
- Enable security tools like clawsec-clawhub-checker to access internal security checks
Security field includes:
- status: clean|suspicious|malicious|pending|error
- hasWarnings: boolean
- checkedAt: timestamp
- model: evaluation model name
Backward compatible: optional field, no breaking changes.
* fix: ensure hasWarnings is always boolean
- Add ?? false to coerce undefined to false when dimensions is undefined
- Fixes Greptile comment: hasWarnings can be undefined instead of boolean
- Ensures SecurityStatusSchema validation passes on client side
* Update convex/httpApiV1/skillsV1.ts
Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
* fix(api-cli): harden security inspect output + tests (#362) (thanks @abutbul)
---------
Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* fix(cli): handle missing browser opener gracefully
On headless Linux servers without xdg-open, 'clawhub login' crashes with
ENOENT error. This change catches the error and prints the URL for manual
copy-paste instead of crashing.
Fixes crash on:
- VPS/cloud servers
- Docker containers
- CI environments
- WSL without browser integration
* fix(cli): test browser-opener fallback messaging (#163) (thanks @aronchick)
---------
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* feat: surface platform/architecture labels on skill cards and API
Expose existing `os` and `nix.systems` metadata from skill frontmatter
through the HTTP API and render as compact tags on browse/search views.
- Widen `PublicSkillListVersion` and `SkillListEntry` types to include
`os` and `nix.systems` fields (data already flows through, types were
artificially narrow)
- Add `metadata: { os, systems }` to `/api/v1/skills/{slug}` and
`/api/v1/skills` list responses
- Add `formatSystemsList` and `getPlatformLabels` helpers to map nix
system strings to human-readable labels (e.g. aarch64-darwin → macOS ARM64)
- Add `platformLabels` prop to `SkillCard`, render as `.tag .tag-compact`
- Show platform labels in both card grid and list views
- Update HTTP API docs with new `metadata` field
Coded by Claude Opus 4.6 (Claude Code)
Reviewed and tested by Jason (@asyncjason)
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: remove redundant optional chaining on clawdis
Address greptile-apps review comment — clawdis is already confirmed
truthy by the ternary condition, so `?.` is unnecessary.
Coded by Claude Opus 4.6 (Claude Code)
Reviewed and tested by Jason (@asyncjason)
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: include version data in listPublicPageV2 for platform labels
The browse listing passed includeVersion: false, causing latestVersion
to always be null and platform/arch labels to never render.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
---------
Co-authored-by: Jason Separovic <jason@wilma.dog>
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
* docs: add CONTRIBUTING.md and refresh README header
Add a comprehensive CONTRIBUTING.md covering local Convex setup,
env var configuration, GitHub OAuth, JWT keys, database seeding,
CLI development, PR guidelines, and AI-generated code policy.
Refresh the README with a centered logo, quick links row, and
clickable doc references. Condense the Local dev section to link
to CONTRIBUTING.md for full setup details.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: add #clawhub discord channel
---------
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
* fix: prevent filtered skills pagination flicker
Skip fully filtered-out pages in public skills pagination so highlighted/non-suspicious filtering doesn't return empty pages with more cursor state, which caused repeated loading-more flicker.
Co-authored-by: Cursor <cursoragent@cursor.com>
* fix: rely on inferred Convex paginate result type
Remove the custom runPaginate annotation so TypeScript infers the exact Convex paginate result shape and preserves stronger type-safety.
Co-authored-by: Cursor <cursoragent@cursor.com>
---------
Co-authored-by: Cursor <cursoragent@cursor.com>
Retry-After was set to an absolute Unix epoch timestamp (e.g. 1771404540),
which violates RFC 9110 §10.2.3. Clients treating it as delay-seconds
would wait ~56 years. Now emits the actual seconds until reset.
Closes#407
Address review feedback:
- Use undici's EnvHttpProxyAgent instead of ProxyAgent. This properly
handles HTTPS_PROXY vs HTTP_PROXY per-scheme, respects NO_PROXY,
and uses connect.timeout instead of requestTls.
- Update docs to mention NO_PROXY support.
The CLI creates a custom undici Agent via setGlobalDispatcher() which
overrides any proxy configuration. Since Node.js native fetch (backed
by undici) does not automatically respect HTTP_PROXY/HTTPS_PROXY env
vars, the CLI fails with 'fetch failed' on systems that require a
proxy for outbound connections.
Import ProxyAgent from undici and use it when any of the standard proxy
environment variables (HTTPS_PROXY, HTTP_PROXY, https_proxy, http_proxy)
is set. When no proxy variable is present, behavior is unchanged.
Also adds proxy documentation to cli.md and a troubleshooting entry.
Address review feedback:
- Guard rescan de-escalation with `status === 'clean'` so pending/unknown
verdicts don't accidentally clear the suspicious flag
- Fix approveSkillByHashInternal where `alreadyFlagged` in the condition
`(isSuspicious || alreadyFlagged) && !bypassSuspicious` prevented clean
verdicts from reaching the isClean branch that properly checks whether
a different scanner set the flag
The daily VT rescan updated vtAnalysis on the version but only called
escalateByVtInternal for suspicious/malicious verdicts. When a verdict
improved from suspicious to clean, the version's vtAnalysis was updated
(website shows "Benign") but the skill's moderationFlags kept the stale
"flagged.suspicious" entry (CLI warns "suspicious"). Now the rescan
calls approveSkillByHashInternal to clear the flag on de-escalation.
Avoids leaving an explicit undefined key in the badges object which
could fail Convex validation.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Add backfillDenormalizedBadgesInternal: syncs skillBadges table →
skill.badges field so listing/search reads are correct
- Simplify hydrateResults fallback
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Remove badge table queries from listing and search paths (~200 queries
per page load eliminated). Use denormalized skill.badges field instead.
- Sync skill.badges when badges are mutated (upsertSkillBadge/removeSkillBadge).
- Add embeddingSkillMap lookup table (~100 bytes/doc) so search hydration
can skip reading full skillEmbeddings docs (~12KB each with vector).
- Remove dead badge query exports from search module.
- Reduce lexical fallback scan limit from 1200 to 500.
- Add backfill mutation for embeddingSkillMap with graceful fallback.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Skills should never have more than a handful of badge records.
Using .take(10) instead of .collect() avoids unbounded reads.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The 5-minute stat event processor was patching skill documents on every run,
which invalidated listPublicPageV2 reactive queries for ALL subscribers —
causing a thundering herd responsible for ~17 TB (59%) of the 28.65 TB
monthly db bandwidth.
Split into two paths:
- Daily stats (15-min cron): writes to skillDailyStats only, no skill doc patches
- Skill doc sync (6-hour cron): patches skill documents with accumulated deltas
Also skip reading version docs in listPublicPageV2 and search hydration
(version data is only needed on detail pages, not listings).
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Prevent activating skills with quality.low moderation reason
- Add skill lookup and moderationReason check in 3 locations where skills are activated
- This ensures quality gate quarantine is not bypassed when VT scan is unavailable or stale
Resolves review comments on #300
Published skills stay permanently hidden in search when VirusTotal
cannot produce a verdict. Three code paths leave moderationStatus as
'hidden' with no recovery:
1. VT_API_KEY not configured — scan skipped, skill stays hidden
2. VT hash not found after 10 poll attempts — marked stale, stays hidden
3. VT hash found but no Code Insight after 10 attempts — same
Fix: call setSkillModerationStatusActiveInternal in all three paths so
the skill becomes searchable. If VT later returns a malicious verdict,
approveSkillByHashInternal will correctly re-hide and flag it.
Closes#139
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Show 'Loading skills…' instead of 'No skills match' when pagination is not exhausted
- Hide 'Scroll to load more' when results are empty
- Add tests for both cases
* fix: return proper HTTP status codes for delete/undelete errors
The delete and undelete handlers for skills and souls were catching all
errors and returning 401 Unauthorized, even for errors like:
- 'Skill not found' (should be 404)
- 'Forbidden' (should be 403)
- Other validation errors (should be 400)
This change updates the error handling to return appropriate status codes:
- 401 Unauthorized: authentication failures
- 403 Forbidden: authorization failures (not owner/admin/moderator)
- 404 Not Found: skill/soul/user not found
- 400 Bad Request: other errors with descriptive message
Fixes#34
* fix(cli): use proper Error objects in abort timeouts
When AbortController.abort() receives a string instead of an Error,
the string itself is thrown. pRetry then wraps it in a confusing
message: 'Non-error was thrown: Timeout'
Changed all 3 occurrences in http.ts:
- apiRequest (line 57)
- apiRequestForm (line 106)
- downloadZip (line 141)
Now timeouts will surface as proper Error objects with clear messages.
* test: add e2e test for delete error handling
Verifies that deleting a non-existent skill returns a proper 'not found'
error instead of a generic 'Unauthorized' message.
* fix: use Error for timeout abort in e2e helper
* feat: add skill file viewer
* fix: prevent file viewer state updates after unmount
* feat: add ban reasons to moderation
* chore: release 0.6.0
* docs: reset changelog for next release
* feat: add LLM security evaluation at publish time
Add OpenClaw LLM-based security evaluator that runs alongside VirusTotal
when skills are published. Reads SKILL.md prose, metadata, install specs,
and file manifest, then assesses coherence across 5 dimensions to catch
social engineering vectors that VT/regex miss (e.g. instruction-only skills
with no code files).
- convex/lib/securityPrompt.ts: system prompt, message assembly, response
parsing, injection pattern detection
- convex/llmEval.ts: evaluateWithLlm action, evaluateBySlug convenience
action, backfillLlmEval for existing skills
- convex/schema.ts: llmAnalysis field on skillVersions
- convex/skills.ts: updateVersionLlmAnalysisInternal mutation,
getActiveSkillBatchForLlmBackfillInternal query, defense-in-depth
multi-scanner flag merging in approveSkillByHashInternal
- convex/lib/skillPublish.ts: schedule LLM eval alongside VT scan
- SkillDetailPage.tsx: OpenClaw row, LlmAnalysisDetail expandable
component with 5 dimension rows, guidance panel, findings section
- styles.css: analysis detail styles from mockup
* fix: collapse OpenClaw analysis by default, fix row spacing, switch to gpt-5-mini
* fix: add retry with backoff for OpenAI rate limits, fix JSON mode requirement
* fix: increase max_output_tokens for reasoning model, fix backfill error retry
* feat: recognize metadata.openclaw as valid frontmatter namespace
* fix: eval assembler falls back to metadata.openclaw for requirements
* feat: evaluator reads all file contents, not just SKILL.md
Reads all files from storage and includes their full source in the eval
prompt so the LLM can detect malicious code hidden behind clean READMEs.
Injection detection now scans all content. Per-file cap 10K chars, total
cap 50K chars.
* feat: add skill metadata docs, suspicious appeal banner for owners
- Document full frontmatter metadata reference in docs/skill-format.md
- Add metadata section + quick example to README
- Show appeal message on suspicious skills (owner-only) linking to GitHub issues
- Accept metadata.openclaw alias in README docs
- Re-evaluate all skills with full file content reading (backfill in progress)
* fix: trailing comma tolerance in JSON metadata, tone down persistence flags
- Strip trailing commas in frontmatter JSON before parsing (silent failure fix)
- Stop flagging disable-model-invocation default as a concern (it's the normal default)
- Stop flagging skills configuring themselves as privilege escalation
- Add MITRE ATLAS AML.T0051 context for when autonomous invocation actually matters
- Show actual defaults in assembled eval message instead of "not set"
* chore: fix lint issues (#213)
* perf: lazy-load diff viewer (Monaco) (#212)
* chore: fix review comments
* fix: VT scan sync race condition + LLM-first moderation model
VT no longer overwrites LLM moderation verdicts. LLM is the primary
moderation authority; VT only escalates (hides + flags) for malicious/
suspicious content via new escalateByVtInternal mutation. Stale VT polls
write vtAnalysis marker instead of overwriting moderationReason. Query
pools expanded to include LLM-evaluated skills awaiting VT results.
Ban message now references malicious skills and security@openclaw.ai.
* fix: handle GitHub API rate limits in account age check (#246)
* fix: handle GitHub API rate limits in account age check
The GitHub account lookup uses unauthenticated requests (60 req/hr
per IP). Since this runs server-side in Convex, all users share the
same IP and quickly exhaust the rate limit, causing "GitHub account
lookup failed" errors during skill publish.
- Detect 403/429 responses and surface a clear rate-limit message
- Support optional GITHUB_TOKEN env var for authenticated requests
(5,000 req/hr)
Fixes#155
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: stabilize GitHub account gate tests and docs
---------
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* docs: thank @superlowburn for PR #246
* fix: prioritize relevant skills in search
* fix: add lexical fallback for skill search recall
* test: add search fallback coverage
* test: fix search test handler typing
* fix(http): remove allowH2 from undici Agent — causes fetch failed on Node.js 22+ (#245)
* Remove allowH2 option from global dispatcher
fix/remove-allowH2-undici-node22-compat
* fix(http): remove allowH2 from e2e dispatcher
---------
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* docs: add 0.6.1 unreleased changelog from post-0.6.0 commits
* fix: allow soft-deleted users to re-authenticate
Fixes Issue #32 where users who soft-deleted their accounts were unable to sign back in because the re-auth logic was only triggering when an existingUserId was passed by the auth provider, which doesn't happen during a standard fresh login flow.
* test: update auth tests for direct deletedAt check
* fix: restore existingUserId check for type safety
* fix: update tests to include required existingUserId parameter
* fix: resolve final lint error in auth tests
* fix: ensure reactivation only matches soft-deleted user (prevents bypass)
* fix: allow re-auth when existingUserId is null
* fix: use valid crons.interval and set to 1 minute
* test: add missing coverage for fresh-login reactivation and identity mismatch guard
* fix: scope reauth fix; keep banned users blocked (#177) (thanks @tanujbhaud)
* fix: include comment deltas in action-based stat processing & add stats reconciliation (#194)
Bug 1: applyAggregatedStatsAndUpdateCursor was missing 'comments' in both
the guard condition and the applySkillStatDeltas call. This caused comment
count deltas to be silently dropped during cron-based event processing,
while stars/downloads/installs were processed correctly.
Bug 2: No reconciliation mechanism existed. If events were missed due to
cursor issues or processing errors, skill stats (stars, comments) would
remain stale with no way to recover. Added reconcileSkillStarCounts
maintenance mutation that counts actual records in the stars and comments
tables and patches any out-of-sync skill stats.
Fixes#193
Co-authored-by: Limitless2023 <limitless@users.noreply.github.com>
* fix: prevent horizontal overflow from long code blocks in skill pages (#183)
* Fix: Prevent horizontal overflow from long code blocks in skill pages
- Add max-width: 100% to .file-list-body and .file-row
- Prevents page-wide overflow when skills contain long code examples
- Markdown pre blocks already have overflow-x: auto, but parent containers were expanding infinitely
- Fixes issue where skills with 400+ char lines (e.g. browser automation commands) cause horizontal scrolling
Affected: Skills with long inline code in markdown (browser act commands, etc.)
* fix: add max-width to .file-list container to prevent overflow
- Also ensures .file-list-body constraint is inherited properly
- Prevents long code blocks from expanding file list container
* fix: add max-width to all markdown containers and pre tags
- Add max-width: 100% to .markdown, .tab-body, .markdown pre
- Ensures code blocks are constrained and show horizontal scrollbar
- Prevents content from expanding parent containers beyond viewport
* fix: add overflow-x to parent containers for horizontal scroll
Adds overflow-x: auto to .skill-detail-stack, .tab-card, and .tab-body
to ensure long code blocks are scrollable within the content area
instead of causing page-wide horizontal overflow.
Fixes horizontal overflow issue on skill pages with long code examples
(e.g., browser automation commands with 400+ character lines).
Tested on zepto skill page - page now stays within viewport (1200px)
and code blocks are accessible via horizontal scrollbar in tab area.
* docs: note code-block overflow fix in changelog (#183) (thanks @bewithgaurav)
---------
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* chore(release): 0.6.1
* fix: prevent infinite loading loop on skills page (#90)
* fix: prevent infinite loading loop on skills pageAdd isLoadingMore guard to IntersectionObserver useEffect to preventcontinuous WebSocket queries when user is idle at bottom of page.The observer now won't set up while a request is in progress, breakingthe infinite loop cycle.Fixes: Related to #89
* fix: prevent repeated skills auto-load requests (#90) (thanks @xcqtnr)
* fix: resolve PR merge conflicts and keep observer regression test (#90) (thanks @xcqtnr)
---------
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* fix(cli): secure config file permissions (#164)
* fix(cli): secure config file permissions and reduce duplication
Security:
- Config files now created with 0600 permissions (owner read/write only)
- Config directories created with 0700 permissions
- Protects API tokens from other users on shared systems
Maintainability:
- Extract resolveConfigPath() helper to reduce code duplication
- Same legacy fallback logic (clawhub -> clawdhub) now in one place
* fix(cli): tolerate unsupported chmod errors for config
---------
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* fix: make /search host-aware in SSR (#257)
* fix: make /search mode-aware
Notes:\n- Medium: /search now depends on getSiteMode() during beforeLoad. On server-side routing, if VITE_SITE_MODE isn’t set and VITE_SOULHUB_SITE_URL is set (as in .env.local), getSiteMode() will resolve to souls and redirect /search to / even on the ClawdHub deployment. This is a regression risk vs the old always-/skills redirect. Confirm deployment envs guarantee correct mode. src/routes/search.tsx:9-31
* fix: make /search host-aware in SSR
* chore: fix lint and route tree for /search route
---------
Co-authored-by: Sash Zats <sash@zats.io>
* fix(vt): explicit return types and missing undici dependency (#255)
* fix(vt): explicit return types and missing undici dependency
Refactor action handlers in convex/vt.ts to use explicit return types, resolving circular type inference (TS7022). Also add undici to devDependencies for E2E tests.
* fix: add root undici devDependency for e2e (#255) (thanks @tanujbhaud)
---------
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* Fix initial skill sorting (#92)
* fix: initial skill sorting
* chore: update unit test
* fix: use correct indexes for skill sorting
* chore: cleanup
* fix: land skill sorting update (#92) (thanks @bpk9)
---------
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* fix: harden download rate limiting and dedupe (#43) (thanks @regenrek)
- add download-specific rate limit tier\n- add per-IP/day dedupe + daily pruning\n- keep moderation gating + deterministic zips\n- add optional forwarded-IP trust via TRUST_FORWARDED_IPS
* fix: harden skill listing and rate limiting under load
* fix: replace skill report prompt with modal
* fix: add skill publish anti-spam caps and quarantine
* docs: add git local-branch cleanup fallback
* fix: enforce quality gate and trust-tier spam checks
* fix: prevent autobanned users from self-reactivating
* test: expand reauth ban regression coverage
* feat: add empty-skill cleanup backfill with ban nominations
* fix: make empty-skill cleanup resumable
* feat: add non-suspicious skills filter toggle
* style: polish selected states in skills toolbar
* feat: default skills sort to downloads
* fix: enforce downloads as canonical default skills sort
* fix: force canonical downloads sort in skills browse mode
* fix: bypass suspicious flags for privileged owners and polish comment delete UI
* fix: add privileged-owner suspicious flag reconciler
* fix: force auth redirects and registry to canonical clawhub host
* feat: auto-generate missing skill summaries
* fix: make skill summary backfill resumable
* feat: add self-scheduling skill summary backfill job
* perf: short-circuit empty skill summary generation
* style: polish upload page layout and actions
* feat: show popular non-suspicious skills on homepage
* fix: normalize legacy skill stats to prevent homepage crash
* fix: render homepage popular cards from nested skill entries
* style: refine global UI theme, borders, and spacing
* fix: resolve search timeout and improve skills page UI alignment (#53)
* fix: resolve search timeout and improve skills page UI alignment
- Added a 10s timeout to OpenAI embedding requests to prevent hanging searches.
- Fixed a TypeScript error in search.ts regarding entry hydration.
- Restructured skills page layout and CSS to ensure consistent alignment between the search toolbar and skill cards.
* fix: resolve search timeout and improve skills page UI alignment
- Added a 10s timeout to OpenAI embedding requests to prevent hanging searches.
- Fixed a TypeScript error in search.ts regarding entry hydration.
- Restructured skills page layout and CSS to ensure consistent alignment between the search toolbar and skill cards.
* style: format skills index layout block
---------
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* docs: thank @GhadiSaab for #53
* style: shift UI palette to cool blue tones
* style: remove remaining warm accent literals
* style: darken hero primary CTA in dark mode
* fix: show stars in popular skill cards
* fix: simplify skills CTA label
* fix: dedupe download metrics hourly by user-or-ip identity (#278)
* style: restore brown palette and dark-mode CTA tone
* fix(comments): stop updating skills.updatedAt on comment add/remove (#55)
* fix(comments): stop updating skills.updatedAt on comment add/remove
Comments are not content changes, so they shouldn't invalidate skill
list queries that depend on updatedAt. This reduces query invalidation
when users add or remove comments.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* test(comments): add updatedAt invalidation regression coverage
---------
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* refactor(comments): extract handlers and harden mutation tests
* feat: make account deletion irreversible and migrate lint to oxlint
* chore: add oxfmt config
* fix(cli): throw Error for all timeout aborts (#283)
* fix(cli): throw Error on timeout aborts
Users have seen an elevated number of:\n clawdhub search image\n ✖ Non-error was thrown: "Timeout". You should only throw errors.\n\nInvestigation shows we were aborting with a string instead of an Error. Switching to controller.abort(new Error('Timeout')) makes retries/formatting treat it as a real error and clears the message.\n\nExample after change:\n clawdhub search image\n table-image v1.0.0 Table Image (0.332)\n nano-banana-pro v1.0.1 Nano Banana Pro (0.319)\n vap-media v1.0.1 AI media generation API - Flux2pro, Veo3.1, Suno Ai (0.281)\n clawdbot-meshyai-skill v0.1.0 Meshy AI (0.276)\n venice-ai-media v1.0.0 Venice AI Media (0.274)\n daily-recap v1.0.2 Daily Recap (0.260)\n openai-image-gen v1.0.1 Openai Image Gen (0.260)\n bible-votd v1.0.1 Bible Verse of the Day (0.248)\n orf v1.0.1 ORF (0.224)\n smalltalk v1.0.1 Smalltalk (0.161)
* fix(http): wrap fetch calls in try-finally to prevent timer leaks
Addresses Vercel review comment: clearTimeout was not called on error paths when fetch throws an exception.
* fix(cli): unify timeout abort handling
---------
Co-authored-by: Sash Zats <sash@zats.io>
* refactor(cli): centralize HTTP status errors and timeout tests (#286)
* fix: keep new skill versions pending until VT verdict
* style: remove residual blue accents and warm base palette
* fix: add retry logic for OpenAI embedding API failures (#272)
* fix: add retry logic for OpenAI embedding API failures
Fixes#149
When importing or uploading skills, the OpenAI embedding API call could
fail with transient errors (rate limits, timeouts, network issues),
causing the entire import to fail with a generic "Server Error".
This adds retry logic with exponential backoff (1s, 2s, 4s delays):
- Retries on 429 (rate limit) and 5xx server errors
- Retries on network/fetch errors
- Logs warnings for debugging
- Max 3 retries before failing with clear error message
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: correct retry count and broaden network error catch
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: address retry loop off-by-one, broaden error catch, preserve original error
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: harden embeddings retry semantics
* style: format embeddings retry changes
---------
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* fix: sync handle on user ensure
* fix: sync handle on user ensure (#293) (thanks @christianhpoe)
* feat: improve moderation/admin UX + language-aware quality gate
- API: owner-visible responses for hidden/soft-deleted skills\n- Admin: add unban user mutations + docs\n- Quality: Intl.Segmenter tokenization + CJK signal to reduce false rejects\n- Jobs: skill-stat-events interval 15m -> 5m\n- Tests: add coverage for owner-visible states + non-Latin docs\n- Changelog: add Unreleased entry
* refactor: simplify user ensure updates
* fix(cors): complete CORS + tokenized CLI reads (#296)
* fix(cors): add Access-Control-Allow-Origin headers to API and downloads
* fix: add CORS to error/raw paths & add CLI install auth
* fix: add OPTIONS handler for CORS preflight
* fix(cors): complete CORS + tokenized CLI reads
* test(cli): fix config mock typing
---------
Co-authored-by: Grenghis-Khan <63885013+Grenghis-Khan@users.noreply.github.com>
* refactor: centralize CORS + CLI auth token (#297)
* refactor(convex): centralize CORS headers
* refactor(cli): centralize auth token lookup
* fix(skills): keep global sorting across pagination (#98)
* fix: initial skill sorting
* chore: update unit test
* fix: use correct indexes for skill sorting
* chore: cleanup
* fix(skills): preserve server order for paginated sorting
* chore(lint): apply biome formatting fixes
* chore(convex): bump tsconfig lib to ES2022
* fix(skills): add deterministic tie-breaker for search sorting
* fix(skills): stable sorting across pagination (#98) (thanks @CodeBBakGoSu)
---------
Co-authored-by: Brian Kasper <bkasperr@gmail.com>
Co-authored-by: knox-glorang <knox@glorang.com>
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* chore: drop convex-helpers (#302)
* perf: batch tag resolution to reduce action→query round-trips
- Add getVersionsByIds batch query to skills.ts and souls.ts
- Replace per-item tag resolution with batch resolution in httpApiV1.ts
- Reduces N action→query round-trips to 1 for list endpoints
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* fix: add null guard and short-circuit for empty tags
- Short-circuit when no version IDs to resolve
- Add null coalescing for runQuery response
- Fixes potential crash when tags are empty or query returns null
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* refactor: batch resolve tags in v1 API (#112) (thanks @mkrokosz)
* fix: handle duplicate Convex Auth user records in publish ownership check (#180)
* fix: handle duplicate user records in publish ownership check
* fix: heal publish ownership via GitHub auth identity
---------
Co-authored-by: Emmet Brown <emmet@Emmets-Mac-mini.local>
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* fix: gate publish by immutable GitHub account ID
* refactor: simplify GitHub age gate cache
* fix(api): centralize v1 soft-delete error mapping
* chore(cli): align http client with main
* test(api): cover v1 soft-delete error mapping
* test(api): reposition soft-delete mapping test
* fix: default to CF-only client IP parsing
* docs: changelog credit + v1 delete status codes
* fix(cli): clarify logout only affects local config (#166)
* fix(cli): clarify logout only affects local config
Users may assume 'clawhub logout' revokes their token everywhere.
In reality, the token remains valid on the server until explicitly
revoked in the web UI. This could be a security concern on shared
machines.
Update the message to set correct expectations.
* fix(cli): clarify logout revocation scope (#166) (thanks @aronchick)
* chore: sync changelog for merge (#166) (thanks @aronchick)
---------
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* feat: anti-squatting protection, backup restore, and ban flow improvements (#298)
* feat: anti-squatting protection, backup restore, and ban flow improvements
- Add `reservedSlugs` table with 90-day cooldown to prevent slug squatting
after skill deletion. Hard-delete finalize phase reserves slugs for the
original owner; `insertVersion` blocks non-owners during cooldown.
- Change ban flow from hard-delete to soft-delete: `banUserWithActor` now
sets `moderationReason: 'user.banned'` and syncs embedding visibility.
`unbanUserWithActor` restores all ban-hidden skills and releases slug
reservations automatically.
- Align `autobanMalwareAuthorInternal` with the same soft-delete + embedding
visibility pattern so unban recovery works uniformly.
- Add admin `reclaimSlug` / `reclaimSlugInternal` mutations for reclaiming
squatted slugs, with audit logging.
- Add GitHub backup restore system (`githubRestore.ts`,
`githubRestoreMutations.ts`, `githubRestoreHelpers.ts`) that reads from
the `clawdbot/skills` backup repo and re-creates skill records. Squatter
eviction runs synchronously in the same transaction as restore to avoid
async race conditions.
- Add `POST /api/v1/users/restore` and `POST /api/v1/users/reclaim` admin
HTTP endpoints for bulk operations.
- Add `trustedPublisher` flag on users; trusted publishers bypass the
`pending.scan` auto-hide for new skill publishes.
- Add `setTrustedPublisher` / `setTrustedPublisherInternal` admin mutations.
Addresses: slug squatting prevention, skill backup/restore, ban recovery,
and trusted publisher workflow improvements.
Co-authored-by: Cursor <cursoragent@cursor.com>
* fix: harden restore/reclaim + ban flow (#298) (thanks @autogame-17)
---------
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* refactor: post-#298 cleanup (#313)
* refactor: consolidate slug + embedding helpers
* refactor: batch ban/unban skill updates
* refactor: report batched ban/unban scheduling
* fix: unblock package typecheck
* refactor: split httpApiV1 + consolidate moderation batches (#315)
* refactor: dedupe v1 file response + unify embedding patches (#316)
* Devin/1771112524 skill metadata update (#312)
* fix: sync GitHub profile on login to handle username renames (#303)
When a user renames their GitHub account, the stored username becomes stale
and causes 'GitHub account lookup failed' errors during skill publishing.
This fix:
- Adds syncGitHubProfile function that fetches current profile using the
immutable GitHub numeric ID
- Adds syncGitHubProfileInternal mutation to update user's name, handle,
displayName, and image when they change
- Schedules the sync as a background action on every login via
afterUserCreatedOrUpdated callback
The sync is best-effort (silently fails if GitHub API unavailable) since
it's not on the critical path. It only updates fields if the username
has actually changed.
Fixes#303
Co-Authored-By: Ian Alloway <adapter_burners.1y@icloud.com>
* fix: allow updating skill summary/description on subsequent publishes (#301)
Previously, the skill summary was only extracted from metadata.description
in the SKILL.md frontmatter. This change also checks for a direct
'description' field in the frontmatter, ensuring that users can update
their skill description by modifying either location.
The fix prioritizes the new description from the current publish over
the existing skill summary, allowing updates to be reflected correctly.
Fixes#301
Co-Authored-By: Ian Alloway <adapter_burners.1y@icloud.com>
* fix: throttle GitHub profile sync
* feat: show skill owner avatars
* fix: avoid nested owner links
* refactor: centralize profile sync + owner lookup
* docs: changelog for #312 (thanks @ianalloway)
---------
Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* style: polish markdown code blocks
* feat: show skill owner avatars on home + lists
* feat: sync GitHub profile name
* feat: improve skill card meta layout
* fix: make ghost buttons look like buttons
* fix: match skill hero cta widths
* fix: prefer $HOME over os.homedir() for path resolution (#299)
* fix: prefer $HOME over os.homedir() for path resolution
os.homedir() reads from /etc/passwd which can return a stale path
after a Linux user rename (usermod -l). Prefer the $HOME environment
variable which reflects the current session.
Closes#82
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: normalize resolveHome output
---------
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* UI: allow copying security scan summary text (#322)
* fix(ui): prevent analysis toggle when selecting summary (#324)
* feat: add uninstall command for skills (#241)
* feat: add uninstall command for skills
Implements `clawhub uninstall <slug>` to properly remove installed skills.
Changes:
- Added cmdUninstall function in skills.ts
- Validates skill is installed before removal
- Removes skill directory and lockfile entry
- Supports --yes flag to skip confirmation prompt
- Added comprehensive test coverage
Closes#221
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: require --yes in non-interactive mode and update lockfile before rm
Address review feedback:
- Fail with "Pass --yes (no input)" when running non-interactively
without --yes flag, matching delete/star/unstar/moderation commands
- Update lockfile before removing directory to avoid inconsistent state
if rm succeeds but writeLockfile fails
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: harden skill uninstall flow (#241) (thanks @superlowburn)
* docs: document uninstall CLI command (#241) (thanks @superlowburn)
* test: fix cmdUninstall mock typing (#241) (thanks @superlowburn)
---------
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* feat: add skill file viewer
* fix: prevent file viewer state updates after unmount
* fix: lazy-load skill file viewer (#44) (thanks @regenrek)
---------
Co-authored-by: Sergiy Dybskiy <s@serg.tech>
Co-authored-by: Peter Steinberger <steipete@gmail.com>
Co-authored-by: theonejvo <theonejvo@users.noreply.github.com>
Co-authored-by: Vignesh <vigneshnatarajan92@gmail.com>
Co-authored-by: Steve <superlowburn@gmail.com>
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Co-authored-by: DColl <david.coll.78@gmail.com>
Co-authored-by: Tanuj Bhaud <tanujbhaud@gmail.com>
Co-authored-by: Limitless <127183162+Limitless2023@users.noreply.github.com>
Co-authored-by: Limitless2023 <limitless@users.noreply.github.com>
Co-authored-by: Gaurav Sharma <sharmag@microsoft.com>
Co-authored-by: xcqtnr <xcqtnr0.0@gmail.com>
Co-authored-by: David Aronchick <aronchick@gmail.com>
Co-authored-by: Sash Zats <sash@zats.io>
Co-authored-by: Tanuj Bhaud <128238320+tanujbhaud@users.noreply.github.com>
Co-authored-by: Brian Kasper <brian@bkasper.com>
Co-authored-by: ghadi saab <ghadisaab21@gmail.com>
Co-authored-by: sethconvex <seth@convex.dev>
Co-authored-by: ChristianHPoe <chpoensgen@me.com>
Co-authored-by: Grenghis-Khan <63885013+Grenghis-Khan@users.noreply.github.com>
Co-authored-by: CodeBBakGoSu <127713112+CodeBBakGoSu@users.noreply.github.com>
Co-authored-by: Brian Kasper <bkasperr@gmail.com>
Co-authored-by: knox-glorang <knox@glorang.com>
Co-authored-by: Matthew Krokosz <mattkrokosz@gmail.com>
Co-authored-by: emmet-bot <emmet@universaleverything.io>
Co-authored-by: Emmet Brown <emmet@Emmets-Mac-mini.local>
Co-authored-by: autogame-17 <166480271+autogame-17@users.noreply.github.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Ian Alloway <adapter_burners.1y@icloud.com>
Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Co-authored-by: CleanApp <165804662+borisolver@users.noreply.github.com>
* feat: add uninstall command for skills
Implements `clawhub uninstall <slug>` to properly remove installed skills.
Changes:
- Added cmdUninstall function in skills.ts
- Validates skill is installed before removal
- Removes skill directory and lockfile entry
- Supports --yes flag to skip confirmation prompt
- Added comprehensive test coverage
Closes#221
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: require --yes in non-interactive mode and update lockfile before rm
Address review feedback:
- Fail with "Pass --yes (no input)" when running non-interactively
without --yes flag, matching delete/star/unstar/moderation commands
- Update lockfile before removing directory to avoid inconsistent state
if rm succeeds but writeLockfile fails
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: harden skill uninstall flow (#241) (thanks @superlowburn)
* docs: document uninstall CLI command (#241) (thanks @superlowburn)
* test: fix cmdUninstall mock typing (#241) (thanks @superlowburn)
---------
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* fix: prefer $HOME over os.homedir() for path resolution
os.homedir() reads from /etc/passwd which can return a stale path
after a Linux user rename (usermod -l). Prefer the $HOME environment
variable which reflects the current session.
Closes#82
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: normalize resolveHome output
---------
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* fix: sync GitHub profile on login to handle username renames (#303)
When a user renames their GitHub account, the stored username becomes stale
and causes 'GitHub account lookup failed' errors during skill publishing.
This fix:
- Adds syncGitHubProfile function that fetches current profile using the
immutable GitHub numeric ID
- Adds syncGitHubProfileInternal mutation to update user's name, handle,
displayName, and image when they change
- Schedules the sync as a background action on every login via
afterUserCreatedOrUpdated callback
The sync is best-effort (silently fails if GitHub API unavailable) since
it's not on the critical path. It only updates fields if the username
has actually changed.
Fixes#303
Co-Authored-By: Ian Alloway <adapter_burners.1y@icloud.com>
* fix: allow updating skill summary/description on subsequent publishes (#301)
Previously, the skill summary was only extracted from metadata.description
in the SKILL.md frontmatter. This change also checks for a direct
'description' field in the frontmatter, ensuring that users can update
their skill description by modifying either location.
The fix prioritizes the new description from the current publish over
the existing skill summary, allowing updates to be reflected correctly.
Fixes#301
Co-Authored-By: Ian Alloway <adapter_burners.1y@icloud.com>
* fix: throttle GitHub profile sync
* feat: show skill owner avatars
* fix: avoid nested owner links
* refactor: centralize profile sync + owner lookup
* docs: changelog for #312 (thanks @ianalloway)
---------
Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* feat: anti-squatting protection, backup restore, and ban flow improvements
- Add `reservedSlugs` table with 90-day cooldown to prevent slug squatting
after skill deletion. Hard-delete finalize phase reserves slugs for the
original owner; `insertVersion` blocks non-owners during cooldown.
- Change ban flow from hard-delete to soft-delete: `banUserWithActor` now
sets `moderationReason: 'user.banned'` and syncs embedding visibility.
`unbanUserWithActor` restores all ban-hidden skills and releases slug
reservations automatically.
- Align `autobanMalwareAuthorInternal` with the same soft-delete + embedding
visibility pattern so unban recovery works uniformly.
- Add admin `reclaimSlug` / `reclaimSlugInternal` mutations for reclaiming
squatted slugs, with audit logging.
- Add GitHub backup restore system (`githubRestore.ts`,
`githubRestoreMutations.ts`, `githubRestoreHelpers.ts`) that reads from
the `clawdbot/skills` backup repo and re-creates skill records. Squatter
eviction runs synchronously in the same transaction as restore to avoid
async race conditions.
- Add `POST /api/v1/users/restore` and `POST /api/v1/users/reclaim` admin
HTTP endpoints for bulk operations.
- Add `trustedPublisher` flag on users; trusted publishers bypass the
`pending.scan` auto-hide for new skill publishes.
- Add `setTrustedPublisher` / `setTrustedPublisherInternal` admin mutations.
Addresses: slug squatting prevention, skill backup/restore, ban recovery,
and trusted publisher workflow improvements.
Co-authored-by: Cursor <cursoragent@cursor.com>
* fix: harden restore/reclaim + ban flow (#298) (thanks @autogame-17)
---------
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* fix(cli): clarify logout only affects local config
Users may assume 'clawhub logout' revokes their token everywhere.
In reality, the token remains valid on the server until explicitly
revoked in the web UI. This could be a security concern on shared
machines.
Update the message to set correct expectations.
* fix(cli): clarify logout revocation scope (#166) (thanks @aronchick)
* chore: sync changelog for merge (#166) (thanks @aronchick)
---------
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* fix: handle duplicate user records in publish ownership check
* fix: heal publish ownership via GitHub auth identity
---------
Co-authored-by: Emmet Brown <emmet@Emmets-Mac-mini.local>
Co-authored-by: Peter Steinberger <steipete@gmail.com>
- Short-circuit when no version IDs to resolve
- Add null coalescing for runQuery response
- Fixes potential crash when tags are empty or query returns null
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Add getVersionsByIds batch query to skills.ts and souls.ts
- Replace per-item tag resolution with batch resolution in httpApiV1.ts
- Reduces N action→query round-trips to 1 for list endpoints
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* fix: add retry logic for OpenAI embedding API failures
Fixes#149
When importing or uploading skills, the OpenAI embedding API call could
fail with transient errors (rate limits, timeouts, network issues),
causing the entire import to fail with a generic "Server Error".
This adds retry logic with exponential backoff (1s, 2s, 4s delays):
- Retries on 429 (rate limit) and 5xx server errors
- Retries on network/fetch errors
- Logs warnings for debugging
- Max 3 retries before failing with clear error message
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: correct retry count and broaden network error catch
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: address retry loop off-by-one, broaden error catch, preserve original error
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: harden embeddings retry semantics
* style: format embeddings retry changes
---------
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Co-authored-by: Peter Steinberger <steipete@gmail.com>
* fix(cli): throw Error on timeout aborts
Users have seen an elevated number of:\n clawdhub search image\n ✖ Non-error was thrown: "Timeout". You should only throw errors.\n\nInvestigation shows we were aborting with a string instead of an Error. Switching to controller.abort(new Error('Timeout')) makes retries/formatting treat it as a real error and clears the message.\n\nExample after change:\n clawdhub search image\n table-image v1.0.0 Table Image (0.332)\n nano-banana-pro v1.0.1 Nano Banana Pro (0.319)\n vap-media v1.0.1 AI media generation API - Flux2pro, Veo3.1, Suno Ai (0.281)\n clawdbot-meshyai-skill v0.1.0 Meshy AI (0.276)\n venice-ai-media v1.0.0 Venice AI Media (0.274)\n daily-recap v1.0.2 Daily Recap (0.260)\n openai-image-gen v1.0.1 Openai Image Gen (0.260)\n bible-votd v1.0.1 Bible Verse of the Day (0.248)\n orf v1.0.1 ORF (0.224)\n smalltalk v1.0.1 Smalltalk (0.161)
* fix(http): wrap fetch calls in try-finally to prevent timer leaks
Addresses Vercel review comment: clearTimeout was not called on error paths when fetch throws an exception.
* fix(cli): unify timeout abort handling
---------
Co-authored-by: Sash Zats <sash@zats.io>
When AbortController.abort() receives a string instead of an Error,
the string itself is thrown. pRetry then wraps it in a confusing
message: 'Non-error was thrown: Timeout'
Changed all 3 occurrences in http.ts:
- apiRequest (line 57)
- apiRequestForm (line 106)
- downloadZip (line 141)
Now timeouts will surface as proper Error objects with clear messages.
The delete and undelete handlers for skills and souls were catching all
errors and returning 401 Unauthorized, even for errors like:
- 'Skill not found' (should be 404)
- 'Forbidden' (should be 403)
- Other validation errors (should be 400)
This change updates the error handling to return appropriate status codes:
- 401 Unauthorized: authentication failures
- 403 Forbidden: authorization failures (not owner/admin/moderator)
- 404 Not Found: skill/soul/user not found
- 400 Bad Request: other errors with descriptive message
Fixes#34
2026-01-25 21:12:02 +00:00
975 changed files with 263064 additions and 31110 deletions
description:"Use when ClawHub needs Codex review, autoreview, second-model review, or a final advisory review gate before commit, PR update, ship, or maintainer handoff."
---
# Autoreview
Run Codex's built-in code review as a closeout check. This is code review
(`codex review`), not Guardian `auto_review` approval routing.
Codex native review mode performs best and is recommended. Non-Codex reviewers
are fallback or second-opinion paths that receive a generated diff prompt, not
the full Codex review-mode runtime.
Use when:
- the user asks for Codex review, autoreview, or second-model review
- after non-trivial code edits, before final/commit/ship
- reviewing a local branch or PR branch after fixes
- closing out ClawHub maintainer work that touched source, tests, Convex, UI,
CLI packages, or workflows
## Contract
- Treat review output as advisory. Never blindly apply it.
- Verify every finding by reading the real code path and adjacent files.
- Read dependency docs/source/types when the finding depends on external
printf 'fallback: opencode run\n' | tee -a "$review_output"
"$opencode_bin" run --pure --dir "$repo_root" "Review the attached prompt file. Do not modify files." --file "$prompt_file" 2>&1 | tee -a "$review_output"
description:"Use for ClawHub staff moderation actions with the repo-local clawhub-mod tool: unhide skills, ban or unban users, change roles, and verify moderation state."
---
# ClawHub Moderation
Use the repo-local `clawhub-mod` tool from a checked-out ClawHub repo. It wraps
the existing ClawHub CLI auth/config and HTTP API surfaces. Do not call Convex
internal mutations directly for staff actions.
## Safety Rules
- Require an explicit target from the user: skill slug, user handle, or user id.
- Require a reason for `skills unhide`, `users ban`, and `users unban`.
- Before any write, show the exact command and ask for confirmation unless the
user already said to proceed or supplied `--yes`.
- Prefer handles for humans. Use `--id` only when the user provides a user id.
- Never bypass API-token auth, server role checks, or audit logging.
- After the write, verify state with the CLI/API and report the result.
## Commands
Run from the ClawHub repo root:
```sh
bun run mod -- --help
```
Authenticate or validate the current token:
```sh
bun run mod -- login
bun run mod -- whoami
```
Unhide a skill after moderator review:
```sh
bun run mod -- skills unhide <slug> --reason "<reason>" --yes
```
List and triage skill reports:
```sh
bun run mod -- skills reports --status open
bun run mod -- skills triage-report <report-id> --status confirmed --action hide --note "<note>" --yes
```
Ban a user:
```sh
bun run mod -- users ban <handleOrId> --reason "<reason>" --yes
```
Unban a user:
```sh
bun run mod -- users unban <handleOrId> --reason "<reason>" --yes
```
Change a user role:
```sh
bun run mod -- users set-role <handleOrId> <user|moderator|admin> --yes
```
Use `--id` when `<handleOrId>` is a user id. Use `--fuzzy` only when the user
has asked for fuzzy handle resolution or the exact handle is ambiguous.
The old top-level aliases still exist for user commands:
```sh
bun run mod -- ban-user <handleOrId> --reason "<reason>" --yes
bun run mod -- unban-user <handleOrId> --reason "<reason>" --yes
```
## Verification
- For skills, inspect the page/API status after `skills unhide`.
- For users, prefer `bun run mod -- whoami` for the current token and user
search/admin surfaces for target accounts where available.
- If verification is blocked by auth or missing admin access, report the command
result and the verification blocker plainly.
## Impact Notes
-`skills unhide` is a moderator manual restore. It clears skill hidden state,
applies a clean manual override to top-level moderation fields, preserves
version-level scanner records, updates public stats, and writes audit logs.
- There is no standalone `skills hide` command in `clawhub-mod`; use report
triage with `--action hide` when resolving a report that should hide a skill.
-`ban-user` is disruptive: it revokes API tokens, marks the user deleted,
hides owned skills, soft-deletes comments, and writes audit logs.
-`unban-user` is admin-only. It clears ban state and restores skills that were
hidden by the matching ban flow; revoked API tokens stay revoked.
description:Use when reviewing, triaging, validating, or discussing ClawHub GitHub issues or pull requests, including author context, CI, UI proof, evidence, labels, close decisions, and maintainer handoff.
---
# ClawHub PR Maintainer
Use this skill for maintainer-facing ClawHub GitHub workflow, not for ordinary
implementation work.
## Start With Live GitHub State
- Use `gh pr view` or `gh issue view` against `openclaw/clawhub`; verify live
state before commenting, labeling, closing, or recommending merge.
- For PRs, read title, body, author, labels, comments, files, commits, status
checks, review state, and linked issues.
- Surface author identity briefly: GitHub name/login and account age when
useful. Treat identity as triage signal, never as proof by itself.
description:Propose a ClawHub policy, product, trust, or interface decision for feedback.
title:"RFC: "
labels:
- "type: rfc"
- "status: review"
body:
- type:markdown
attributes:
value:|
Use RFCs for decisions that need visible feedback before they become policy, product behavior, or public API contract. Accepted repo RFC files live under `rfcs/`, not `docs/`, so draft/decision records do not publish to the docs site. Keep sensitive enforcement details, private reports, exploit specifics, and scanner thresholds out of the public issue.
- type:dropdown
id:area
attributes:
label:Area
description:Pick the primary area this RFC affects.
options:
- Moderation / policy
- Security / trust
- Product / UX
- API / CLI
- Documentation
- Other
validations:
required:true
- type:textarea
id:context
attributes:
label:Context
description:What problem, decision, or ambiguity does this RFC address?
placeholder:|
ClawHub needs a clearer policy for...
validations:
required:true
- type:textarea
id:goals
attributes:
label:Goals
description:What should this RFC achieve?
placeholder:|
- Make enforcement expectations understandable to users.
- Give moderators a consistent decision boundary.
validations:
required:true
- type:textarea
id:non_goals
attributes:
label:Non-goals
description:What is intentionally out of scope?
placeholder:|
- This RFC does not expose internal scanner thresholds.
- This RFC does not decide implementation details for every moderation tool.
validations:
required:true
- type:textarea
id:proposal
attributes:
label:Proposal
description:Describe the proposed policy, behavior, or decision.
placeholder:|
ClawHub should...
validations:
required:true
- type:textarea
id:examples
attributes:
label:Examples
description:Give concrete allowed, not allowed, or edge-case examples.
placeholder:|
Allowed:
- Defensive security review with explicit scope and evidence.
Not allowed:
- Account takeover, evasion, or non-consensual surveillance workflows.
Edge cases:
- ...
- type:textarea
id:user_impact
attributes:
label:User impact
description:How does this affect authors, users, moderators, API consumers, or external contributors?
placeholder:|
Authors will...
Users will...
Moderators will...
- type:textarea
id:open_questions
attributes:
label:Open questions
description:What feedback would be most useful before a decision?
placeholder:|
- Should appeals be handled in-product, through GitHub, or both?
- What examples would make this clearer?
validations:
required:true
- type:input
id:feedback_deadline
attributes:
label:Feedback deadline
description:Use an absolute date. Normal RFCs should stay open for 7-14 days unless urgent.
For website/UI changes, attach screenshots or recordings from the real app. Include mobile/narrow views when layout changes.
- [ ] Screenshots/recordings attached, or `N/A`
## Behavioural Proof
Describe how you verified the user-facing behavior. For UI changes, include the path tested and what changed on screen. For backend/API changes, include the request, command, or scenario that proves the behavior.
- [ ] Behavioural proof included, or `N/A`
## Security / Trust Impact
- [ ] No security/trust impact
- [ ] Security/trust impact explained
## Data / Deploy Impact
- [ ] No data/deploy impact
- [ ] Data/deploy impact explained
## Verification
- [ ]`bun run ci:static`
- [ ] Focused tests for touched behavior:
- [ ]`bun run ci:unit` or `N/A` for docs/config-only:
if ! grep -Eiq '(^|[[:space:]])@(clawsweeper|openclaw-clawsweeper)\b(\[bot\])?|(^|[[:space:]])/(clawsweeper|review|automerge|autoclose)\b' "$body_file"; then
if [[ -z "$base" || "$base" == "$zero_sha" ]]; then
base="origin/$DEFAULT_BRANCH"
fi
fi
echo "base=$base" >> "$GITHUB_OUTPUT"
echo "head=$head" >> "$GITHUB_OUTPUT"
- name:TruffleHog OSS
id:trufflehog
# Use a concrete released ref that resolves in upstream action registry.
# v3 (major tag) is not published by trufflesecurity/trufflehog.
uses:trufflesecurity/trufflehog@v3.95.3
with:
path:./
base:${{ steps.scan_range.outputs.base }}
head:${{ steps.scan_range.outputs.head }}
extra_args:--only-verified --debug
- name:Notify on Failure
if:steps.trufflehog.outcome == 'failure'
run:|
echo "::error::Verified secrets found! This PR contains live credentials that must be rotated immediately."
echo "::notice::If these secrets are already in the commit history, they cannot be removed via a simple removal commit/push. A repository owner can contact GitHub Support to purge the cached data: https://support.github.com/contact/private-information"
-`convex/_generated/` — generated Convex API/types; committed for builds.
-`docs/` — product/spec docs (see `docs/spec.md`).
-`docs/` — publishable public/operator docs for the ClawHub docs tab.
-`specs/` — product specs, plans, regression notes, design history (see `specs/spec.md`).
-`public/` — static assets.
## Durable Intent & Specs
- Use `specs/` to persist system/subsystem intent, invariants, and design rationale that future agents should preserve.
- Keep intended behavior for security-sensitive flows there, especially moderation, upload gating, scanner outcomes, appeals, bans, ownership, package installability, and API trust boundaries.
- If code changes reveal or change how a subsystem is supposed to work, update the relevant spec or add a focused spec note instead of burying the intent only in PR text or public docs.
- Keep `docs/` user/operator-facing: explain current behavior and commands there, but put internal “why this must work this way” context in `specs/`.
## Build, Test, and Development Commands
-`bun run dev` — local app server at `http://localhost:3000`.
Keep this section as the command map agents normally need, not a full `package.json` script index.
-`bun run dev` — foreground local app server at `http://localhost:3000`.
-`bunx convex dev --typecheck=disable` — local Convex backend/function watcher for manual setup.
-`bunx convex codegen` — regenerate `convex/_generated` after Convex API/schema changes.
-`bun run setup:worktree` — link `.env.local` and `.convex` from a usable source worktree into the current worktree. Use `-- --from <path>` or `CLAWHUB_WORKTREE_SOURCE=<path>` when auto-discovery picks the wrong source.
-`bun run dev:worktree` — Worktrunk-managed detached worktree server. Requires `wt` on `PATH`; from that worktree use `wt --yes url` to print the branch URL and `wt --yes stop` to stop it.
-`bun run seed:dev` — canonical local seed path; runs worktree setup, waits for local Convex, seeds local fixtures plus the public corpus, and refreshes stats.
-`bun run build` — production build (Vite + Nitro).
-`bun run preview` — preview built app.
-`bunx convex dev` — Convex dev deployment + function watcher.
-`bun run coverage` — coverage run; keep global >= 80%.
-`bun run ci:static` — required pre-handoff static gate: peer checks, audit, formatting, lint, and dead-code checks.
-`bun run ci:unit` — Vitest coverage gate; required for source/test PRs unless docs/config-only.
-`bun run ci:types-build` — full TypeScript/build gate for app, Convex, and packages.
-`bun run ci:packages` — schema, CLI, and moderation package verification.
-`bun run ci:e2e-http` — secretless HTTP and CLI e2e subset.
-`bun run ci:playwright-smoke` — chromium smoke against the public read backend.
-`bun run test:pw:local-auth` — local Convex/dev-auth browser gate for signed-in/write flows.
Specialized corpus, scanner, security-worker, UI proof, proof publishing, Crabbox, docs-authoring, and dataset scripts are real maintenance tools, but they should stay in the relevant specs, skills, or package script lookup unless the task touches that subsystem.
## Coding Style & Naming Conventions
- TypeScript strict; ESM.
- Indentation: 2 spaces, single quotes (Biome).
- Lint/format: Biome + oxlint (type-aware).
- Convex function names: verb-first (`getBySlug`, `publishVersion`).
- Inline code comments: add brief comments for tricky, bug-prone, or previously buggy logic.
## Testing Guidelines
- Framework: Vitest 4 + jsdom.
- Tests live in `src/**` and `convex/lib/**`.
- Coverage threshold: 80% global (lines/functions/branches/statements).
- Before commit/PR handoff, run `bun run ci:static` so formatting, linting, audit/peer checks, and dead-code export checks match the CI `static` job. For faster inner loops, targeted `bun run format:check -- <files>` / `bun run lint` are fine, but do not treat them as the final pre-push gate.
- Before commit/PR handoff for non-trivial code changes, use `$autoreview` until no accepted/actionable findings remain, unless equivalent manual review already happened, the change is trivial/docs-only, or the user opts out.
- Before opening a PR for source or test changes, run the targeted tests for the touched behavior and `bun run ci:unit` (`VITE_CONVEX_URL=https://example.invalid bun run coverage`) unless the change is docs/config-only or the user explicitly asks to rely on CI. For runtime, build, or package changes, also run the matching broader gate when it covers the touched surface: `bun run ci:types-build`, `bun run ci:packages`, `bun run ci:e2e-http`, or `bun run ci:playwright-smoke`.
- PRs: include summary + test commands run. Add screenshots for UI changes.
- Before merging any PR, verify TypeScript cleanly with `bunx tsc -p packages/schema/tsconfig.json --noEmit` and `bunx tsc -p packages/clawhub/tsconfig.json --noEmit`; if Convex code changed, also run the repo typecheck path used by deploy so `bunx convex deploy` will not fail on `tsc`.
- GitHub comments: for multiline `gh` comments/close messages, use `--body-file`, `--input`, or stdin/heredoc with real newlines; never pass literal `\\n` in shell strings.
- Reject PRs that add skills into source code/repo content directly (for example under `skills/` or seed-only additions intended as published skills). Skills must be uploaded/published via CLI.
- Repo-local developer skills under `.agents/skills/` are allowed only when they are ClawHub-specific, such as Convex, moderation, PR maintainer, or UI proof workflows. Keep generic shared skills such as `crabbox` and `autoreview` in the global `agent-skills` install, not this repo. Keep top-level `skills/` reserved for installed/published skill content and ignored by git.
## Production Release
- Production deploys are manual-only. Merging to `main` does **not** deploy.
- To release production, start the GitHub Actions `Deploy` workflow from `main`:
`gh workflow run deploy.yml --repo openclaw/clawhub --ref main`
- The workflow supports `full`, `backend`, and `frontend` targets.
-`frontend` currently means: wait for the Vercel production deploy for the selected `main` SHA, then run production smoke checks. It does not call `vercel deploy` directly yet.
- The workflow uses the GitHub `Production` environment for deploy secrets, but it does not require a separate approval step.
- Prod deploy secrets live on the `Production` environment, not as ordinary repo secrets. Required: `CONVEX_DEPLOY_KEY`. Optional: `PLAYWRIGHT_AUTH_STORAGE_STATE_JSON`.
- CLI npm releases are also manual-only and tag-based. Stable tags only: `vX.Y.Z`. Start `ClawHub CLI NPM Release` from `main`, first with `preflight_only=true`, then rerun it with the same tag and the successful `preflight_run_id`.
- Real CLI publishes wait at the GitHub `npm-release` environment and use npm trusted publishing. Required npm trusted publisher settings: repository `openclaw/clawhub`, workflow `clawhub-cli-npm-release.yml`, environment `npm-release`.
## Git Notes
- If `git branch -d/-D <branch>` is policy-blocked, delete the local ref directly: `git update-ref -d refs/heads/<branch>`.
## URL Quick Reference
- Canonical site: `https://clawhub.ai` (prefer this over legacy domains).
- Skill page URL format: `https://clawhub.ai/<owner>/<slug>` (owner handle preferred; falls back to owner id).
- Skill API detail URL: `https://clawhub.ai/api/v1/skills/<slug>`.
- OAuth: GitHub OAuth App credentials required for login.
## Convex Ops (Gotchas)
- New Convex functions must be pushed before `convex run`: use `bunx convex dev --once` (dev) or `bunx convex deploy` (prod).
- For non-interactive prod deploys, use `bunx convex deploy -y` to skip confirmation.
- If `bunx convex run --env-file .env.local ...` returns `401 MissingAccessToken` despite `bunx convex login`, workaround: omit `--env-file` and use `--deployment-name <name>` / `--prod`.
## Convex Query & Bandwidth Rules
- **Always use `.withIndex()` instead of `.filter()` for fields that can be indexed.** `.filter()` causes full table scans — every doc is read and billed. Even a single `.filter()` on a 16K-row table reads ~16 MB per call.
- **Convex reads entire documents** — no field projections. If you only need a few fields from large docs (~6 KB+), denormalize a lightweight summary onto the parent doc or use a lookup table (see `embeddingSkillMap`, `skill.latestVersionSummary`, `skill.badges` for examples).
- **Denormalization pattern**: persist computed fields so they can be indexed. Every mutation that updates source fields must also update the denormalized field. Always write a cursor-based backfill for new fields (see `backfillIsSuspiciousInternal`, `backfillLatestVersionSummaryInternal`, `backfillDenormalizedBadgesInternal` for examples).
- **Cron jobs must never scan entire tables.** Use indexed queries with equality filters. Use cursor-based pagination for large datasets. Prefer incremental/delta tracking over full recounts.
- **32K document limit per query.** Split `.collect()` calls by a partition field (e.g., one day at a time instead of a 7-day range). See `rebuildTrendingLeaderboardAction` in `convex/leaderboards.ts` for an example.
- **Common mistakes**: `.filter().collect()` without an index; `ctx.db.get()` on large docs in a loop for list views; while loops that paginate the whole table to find filtered results.
- **Before writing or reviewing Convex queries, check deployment health.** Run `bunx convex insights` to check for OCC conflicts, `bytesReadLimit`, and `documentsReadLimit` errors. Run `bunx convex logs --failure` to see individual error messages and stack traces. This helps identify which functions are causing bandwidth issues so you can prioritize fixes.
<!-- convex-ai-start -->
This project uses [Convex](https://convex.dev) as its backend.
When working on Convex code, **always read `convex/_generated/ai/guidelines.md` first** for important guidelines on how to correctly use Convex APIs and patterns. The file contains rules that override what you may have learned about Convex from training data.
Convex agent skills for common tasks can be installed by running `npx convex ai-files install`.
<!-- convex-ai-end -->
## Stat Field Migration Rules
The `skills` table maintains two parallel sets of stat fields as part of an in-progress field migration:
- **Always use `readCanonicalStat(skill, field)` (`convex/lib/skillStats.ts`) to read** any of the four migrated fields. It prefers the top-level field and falls back to the nested field for pre-migration documents. Never access `skill.stats.downloads` / `.stars` / `.installsCurrent` / `.installsAllTime` directly.
- **Always use `applySkillStatDeltas()` to write** stat deltas. It writes both the top-level and nested fields in the same patch to keep them in sync.
- **Both sets of fields must be written together** in any patch that touches stat values (see the return shape of `applySkillStatDeltas`).
- **Nested-only reads are acceptable only for** `stats.comments` and `stats.versions` — no top-level field exists for these yet.
- The four legacy nested fields are marked `@deprecated` in `statsValidator` (schema.ts). Any IDE access to `skill.stats.downloads` etc. will show a strikethrough warning — treat this as a signal to use `readCanonicalStat()` instead.
- When adding new stat fields, follow the same dual-write pattern and add a cursor-based backfill mutation (see `backfillSkillStatFieldsInternal` for an example).
- API/CLI: report Skill Card verification with flattened skill/version metadata, ClawScan verdict fields at `security.*`, and supporting scanner evidence under `security.signals`.
## 0.18.0 - 2026-05-25
### Changes
- CLI/API: add Skill Card verification surfaces, including `clawhub skill verify <slug>` JSON output and `--card` Markdown retrieval (#2382).
- Web/API: surface an "API key required" attribute on skills so listings, cards, and detail views show whether a skill needs an LLM API key, with publish-time inference from skill prompts and metadata (#2353) (thanks @momothemage).
### Fixes
- API: fix `GET /api/v1/skills` pagination so `cursor` advances to the next page instead of repeating the first page for supported non-trending sorts (#2275) (thanks @vyctorbrzezowski, @enerj).
- Web: block collaborative membership on personal publishers while allowing the linked owner to clean up stale extra membership rows (thanks @vyctorbrzezowski).
- Security/API: hide owned package/plugin catalog entries, revoke package publish tokens, and restore only matching ban-hidden packages on user unban (thanks @vyctorbrzezowski).
- API: block public raw skill files when moderation already blocks downloads and reject skill tags that point at another skill's version (thanks @vyctorbrzezowski).
- Web: stop stale unban restore batches from reactivating skills after the owner is banned again or deactivated (thanks @vyctorbrzezowski).
- Security/API: reject direct skill owner transfers when the skill is hidden, suspicious, or malicious (thanks @vyctorbrzezowski).
- Security/API: revalidate package publish actor, owner, and owner publisher active state in the final release insert (thanks @vyctorbrzezowski).
## 0.17.0 - 2026-05-19
- CLI/API: add self-serve org publisher creation with `clawhub publisher create <handle>` and scoped package publish errors that point to the command.
## 0.16.0 - 2026-05-18
### Fixes
- CLI/API: make package publishes robust under parallel same-publisher release jobs by avoiding unnecessary shared publisher writes, retrying transient Convex contention, and labeling contention separately from package validation failures (#2291).
- Security: move upload ClawScan classification to a GitHub Actions Codex worker, treat VirusTotal as telemetry-only signal, and trust verified `@openclaw/*` plugin packages by default.
- Security: cancel pending skill ownership transfers before rejecting accept attempts when the requester is inactive or the skill is hidden, removed, or malicious (#2276, #2277) (thanks @vyctorbrzezowski).
- API/CLI: fix package delete returning 500 for packages with capability tags when no capability search digest row existed yet (#2212) (thanks @momothemage).
- API: return a clear 400 for `/api/v1/packages/search` without a non-empty `q` instead of treating `search` as a package name (thanks @vyctorbrzezowski).
- Web/API: keep search results limited to items with match evidence, preserve trust and popularity as tie-breakers, and show `N+` counts without exact count queries (#2206) (thanks @vyctorbrzezowski).
- Web: preserve `ownerHandle` through legacy skill publish redirects so org admins land in the correct new-version owner context (#2177).
- Settings: save display name/bio changes even when a legacy personal publisher handle conflict prevents publisher profile sync (#1199).
- Auth: show a visible error if the GitHub sign-in request fails before the provider redirect starts (#2197).
- Schema: include `.tsv`, `.conf`, `.properties`, and `.dat` in the exported text-file allowlist and regenerate the committed schema package runtime (#2172, #874) (thanks @alexuser).
- API: return `400` for invalid known public package filters and invalid skill list sort values, while continuing to ignore unknown query parameters (#2184).
- API/docs: document v1 plain-text error responses and expose owner metadata in the OpenAPI search result schema (#2187) (thanks @vyctorbrzezowski).
- Web: rank publisher card preview items by downloads instead of recent publish order (thanks @vyctorbrzezowski).
- Web: remove the desktop Files tab height cap and make mobile truncation explicit (thanks @vyctorbrzezowski).
- CLI/API: include skill owner handles in search results so duplicate/common slugs are easier to disambiguate (thanks @vyctorbrzezowski).
- Web: let skill publishers pick a curated lucide icon for cards and listings (#2174) (thanks @momothemage).
- Web/API: add keyword-based plugin categories plus API-backed plugin search sorting for recently updated, newest, and name (#2118) (thanks @vyctorbrzezowski).
- Web: polish the starred skills page with grid/list controls, sorting, and optimistic unstar behavior (#2159) (thanks @vyctorbrzezowski).
- API/docs: expand the v1 OpenAPI contract with package/plugin catalog endpoints and align documented rate limits with the server constants (#2186) (thanks @vyctorbrzezowski).
- Admin/Ops: audit profile syncs, self-service account/profile changes, personal publisher syncs, and org trusted-publisher changes so slug and ownership investigations have a complete ledger.
- Dependencies: update production `@clack/prompts`, `tailwind-merge`, and `yaml` dependencies (#2198).
## 0.15.0 - 2026-05-12
### Changes
- Web: polish dashboard artifact cards, loading skeletons, skill summary/detail layout, and adoption metrics after the 0.14 release (#2150, #2153, #2156, #2157, #2158, #2160).
- Docs/dev: clarify pre-PR validation gates for local contributors (#2161).
### Fixes
- Web: show plugin settings actions to package managers and preserve manager access in dashboard rows (#2163, #2168).
- Web: refresh skill star state after mutations and keep skill tabs from causing horizontal scroll (#2154, #2155).
- Web: show owner names when handles are hidden, and clarify editable skill summary settings copy (#2151, #2162).
- Dashboard: add a publisher switcher so org-owned skills and plugins are visible to org admins after transfer or publish (#2132).
- Web: let org publishers/admins republish transferred org-owned skills without the publish form treating the existing slug as taken, including legacy users with synthesized personal publishers (#2171).
- CLI: send skill ownership command payloads as JSON objects so rename/merge operations reach the API correctly (#1300).
- CLI: keep an install fingerprint in skill origin metadata so `clawhub update <skill>` does not report fresh installs as local changes when the server cannot resolve the current hash (#169).
- CLI: migrate cached `registry.clawhub.ai` registries back to `clawhub.ai` so `clawhub explore` no longer talks to the retired Vercel deployment (#1098).
- CLI: publish `.tsv`, `.conf`, `.properties`, `.dat`, and safe extensionless text files while excluding dotfiles and sampling extensionless files before full reads (#874).
- Tests: remove obsolete rescan e2e probes that no longer match current moderation behavior (#2152).
## 0.14.0 - 2026-05-11
### Changes
- Dev: auto-start services for Codex worktrees and add a local dev persona FAB (#2146, #2147).
- Dev: add a local ClawScan dry-run helper script (#2143).
### Fixes
- API: return deterministic 403 responses for skill/package rescan and package transfer permission denials, with CI e2e coverage for protected write endpoints.
## 0.13.0 - 2026-05-11
### Changes
- Web: redesign Settings into focused account, organization, API token, and account deletion views with responsive desktop and mobile layouts (#2134) (thanks @vyctorbrzezowski).
- Web: replace the Users directory with a Publishers discovery surface covering builders and organizations, add `/publishers` as the canonical route, and keep `/users` compatibility (#2087) (thanks @vyctorbrzezowski).
- Web: polish browse/listing surfaces across skills, plugins, and search, including plugin card view parity, clearer search controls, visible safety filtering, and more consistent card metadata treatment (#2084) (thanks @vyctorbrzezowski).
- Web: allow skill owners and publisher admins to edit a skill summary from the detail page (#1411) (thanks @SylvanXiao).
- CLI/Auth: add device-code login for remote or headless shells, backed by ClawHub device authorization endpoints (#1867) (thanks @LumenFromTheFuture).
- CLI: add per-skill pinning so installed skills can be frozen against direct updates, bulk updates, and force reinstalls (#1806) (thanks @deepujain).
- Web: rename the skills and plugins browse alternate view from Cards to Grid while keeping legacy `view=cards` URLs compatible (#2119) (thanks @vyctorbrzezowski).
- Dev docs: refresh generated Convex AI guidance files (#2000).
### Fixes
- Moderation: stop treating VirusTotal Code Insight/Palm verdicts as a hide authority for skills; real AV-engine hits and ClawScan findings still contribute moderation verdicts.
- Moderation: stop treating static suspicious-only findings as a verdict; keep file/line evidence for review while VT/LLM decide public suspicious status.
- ClawScan: reduce false positives for scoped uninstall cleanup, declared provider login flows, Basic Auth/base64 handling, and user-directed provider uploads while hard-blocking stealth browser abuse patterns.
- ClawScan: lower false positives by treating purpose-aligned notes as benign unless structured LLM findings contain a material concern, and add targeted rescan batches for suspicious skills/plugins.
- Moderation: split visible ClawScan review guidance from hidden suspicious filtering, and add operator cleanup for stale aggregate rows and obvious test/placeholder suspicious skills.
- Security: add an admin-only moderation hold lift path for false-positive publisher holds, with audited skill restoration that preserves independently hidden skills (#1133) (thanks @Justincredible-tech).
- Moderation: let platform moderators and admins trigger skill/package security rescans for any owner from the CLI, without consuming the owner recovery cap.
- ClawScan: include package `openclaw.environment` env/config declarations in package review prompts so declared plugin runtime requirements are not reported as missing (#2013).
- Skills/Packages: let publisher admins manage owned lifecycle operations consistently, including skill rename/delete/restore, direct skill moves into org publishers they administer, package restore from the CLI/API, and direct moves back to their personal publisher.
- Skills: repair publisher-owned skill merges, bound historical slug redirects, block protected slug namespaces, and expire owner-unpublished slug reservations after 30 days (#2115) (thanks @fuller-stack-dev).
- Skills: allow confirmed owner migration when republishing an existing skill to another publisher, preserving versions, stats, aliases, and audit history (#1998, #2102) (thanks @momothemage).
- Security: block owner delete/undelete paths from overriding moderator or scanner hides, and return explicit 403 authz responses for owner restore denials (#2078) (thanks @momothemage).
- CLI/API: send skill transfer payloads as JSON objects so transfer requests reach the API correctly.
- Packages: keep package search digests schema-safe during delete/restore so package lifecycle CLI calls do not fail after provenance updates.
- Search: recall skill matches by non-first slug/display-name tokens while keeping multi-token queries on the direct recall path constrained to all query tokens (#2140) (thanks @momothemage).
- Search/Web: disclose when `/search` is hiding suspicious skills and add an explicit opt-out so unified search no longer silently differs from `/skills` for the same query (#2079) (thanks @momothemage).
- Uploads: accept PowerShell `.ps1`, `.psm1`, and `.psd1` files as text-based skill files while keeping normal scan coverage (#897) (thanks @cute-omega).
- Packages: count package install stat events separately from package downloads and record npm tarball fetches as installs (#1712).
- Web: keep the Publishers directory responsive for high-volume publishers by using bounded published-item previews, and abort stale unified-search plugin requests during route changes.
- Web: point skill, plugin, and soul owner links directly at canonical `/p/:handle` publisher profiles instead of legacy redirect routes.
- Web/API: ignore stale public skill-list cursors from older sort or safety-filter indexes instead of throwing pagination errors.
- Web: restore dashboard skill metrics for owned skills and use pointer cursors on dropdown menu items (#2113) (thanks @fuller-stack-dev).
- Web: show the skills browse `Hide suspicious` control only when the loaded results include suspicious skills (thanks @vyctorbrzezowski).
- Web: align signed-in header avatar controls across desktop and mobile so the menu trigger keeps consistent sizing, truncation, and dropdown styling (#2124) (thanks @vyctorbrzezowski).
- Web: constrain settings, profile content, skill detail, and plugin detail pages to the header content width while preserving profile hero bleed (thanks @vyctorbrzezowski).
- Web: show publish-page validation next to the relevant fields and upload picker so invalid inputs are not buried below the form (#908) (thanks @AndyZhengyan).
- Docs: remove README references to the inactive onlycrabs.ai domain while leaving the internal SoulHub configuration generic (#951) (thanks @muescha).
- Docs/dev: document the local Convex site proxy URL and make worktree setup reject misconfigured local site URLs that break HTTP routes (#2060) (thanks @vyctorbrzezowski).
- Dev setup: make local seed reset deterministic by cleaning stale seed lookup and badge rows for repeated Convex dev runs (#2057) (thanks @vyctorbrzezowski).
## 0.12.3 - 2026-05-06
### Fixes
- CLI/API: allow skill publishes to target an org/user publisher with `--owner` / `ownerHandle`, and keep root `SKILL.md` publishable even when broad ignore rules match Markdown files (thanks @deepujain).
- Packages: expose owned plugin/package soft-delete in the CLI and dashboard, keep moderator takedown access, and remove deleted packages from package search surfaces (thanks @Patrick-Erichsen).
- Packages: support monorepo package publishes, infer package owners from scoped names, and keep dry-run publishes metadata-only.
- Packages: validate code-plugin runtime entries against extracted files, allow admin plugin release publishes, and raise trusted-publish/admin API rate limits for legitimate publish bursts.
- API/Search: return lean skill list payloads, route package search through digest indexes, decode scoped package paths, and bound fallback scans to reduce production read pressure.
- Web: restore skill downloads and search paging, canonicalize scoped plugin paths, and improve mobile layout responsiveness.
- Security: add scanner checks for confirmation bypasses and Python file upload exfiltration while reducing generic false-positive package tags.
## 0.12.2 - 2026-05-02
### Fixes
- CLI: publish code plugins as clawpacks and allow legacy package downloads to keep older install flows working.
- CLI: add unban support, moderation diagnostics in `inspect`, manual skill-directory listing, package environment filters, and package migration-status commands.
- Web: add skills/plugins search typeahead, featured plugin curation, plugin management tools, skill upload shortcuts, and dashboard pagination.
### Fixes
- API: raise public read rate limits to reduce false-positive 429s from browser pages and production smoke tests (thanks @steipete).
- CLI/moderation: allow `delete`, `hide`, `undelete`, and `unhide` to record moderation reasons in skill notes and audit logs for legal or policy reviews (thanks @steipete).
- Packages: make package publish retries idempotent, constrain catalog queries, keep package list queries single-page, count package archive downloads, and keep beta plugin packages off `latest`.
- Search: add soul lexical fallback, non-suspicious digest indexes, normalized skill prefix recall, and more stable relevance recall windows.
- Security: broaden static scanner coverage for unsafe credential, subprocess, browser-file, provider-secret, and remote-recipe patterns while hardening prompt-boundary handling.
- Deploy/CI: harden production smoke checks, expand PR validation coverage, add dead-code gates, and stabilize CodeQL light coverage.
- Dependencies: pin `undici` on the Node 20-compatible line after reverting the incompatible v8 update.
## 0.12.0 - 2026-04-28
### Added
- Security: add owner rescan requests, owner flagged inventory, scanner-specific security pages, and in-progress scan states.
- UI: adopt shadcn-managed primitives and polish the rescan/security surfaces for mobile.
### Fixes
- Moderation: calibrate VirusTotal Code Insight suspicious verdicts so uncorroborated AI-only findings do not keep otherwise clean skills quarantined (#1830, #1841) (thanks @deepujain).
- Security: flag exposed secrets in skill docs and normalize VirusTotal engine stats before caching.
- Auth: tolerate stale auth state when reading star status.
- CI: harden and debounce ClawSweeper dispatch workflows and fix production smoke coverage.
## 0.11.0 - 2026-04-28
### Changed
- Docs: clarify that ClawHub does not support paid skills, per-skill pricing, or paywalled releases (#1752, #1844) (thanks @deepujain).
- API docs: clarify how third-party directories can reuse public ClawHub catalog endpoints while respecting rate limits and canonical links (#1825, #1845) (thanks @deepujain).
- Packages docs: document the required fields for code-plugin package publish flows (#1802) (thanks @deepujain).
- Search: add CJK tokenization support (Chinese/Japanese/Korean) with Intl.Segmenter plus fallback behavior to improve skill query matching (#1596) (thanks @pq-dong).
- Stats: centralize migrated skill stat fallback reads through `readCanonicalStat()` and add schema/agent guardrails to discourage direct legacy nested-field access (#1709) (thanks @momothemage).
### Fixes
- Packages: use the configured `GITHUB_TOKEN` for trusted-publisher repository identity lookups to avoid anonymous GitHub API rate limits during publish setup (#1820, #1846) (thanks @deepujain).
- Packages: keep package search fallback scans bounded, stop scanning after the requested result limit, and keep direct plugin-name matches scoped to the requested package family (OpenClaw #64025).
- Moderation: stop flagging declared env vars sent to their intended API while preserving broad env scraping and exfiltration findings (#1803) (thanks @deepujain).
- Moderation: stop treating generic webhook integration docs as suspicious unless they include explicit Discord or Slack webhook endpoints (#1716) (thanks @langningchen-openclaw).
- Search: increase initial vector candidate pools and align CLI search's default limit with the web UI so high-scoring matches are not missed at small limits (#1375, #1429) (thanks @tjefferson).
- Search: fall back to lexical skill search when embedding generation fails instead of returning empty skill results (#1291) (thanks @goulonghui).
- Search: rank exact slug matches above longer slugs that merely contain all query tokens (#1130) (thanks @QuinnH496).
- Search: widen lexical fallback coverage and scan recently created skills so newly published skills can be found before embeddings rank well (#1185, #1200) (thanks @thirumaleshp).
- Search: preserve vector scores across candidate expansion and require all query tokens to match exact-token filters so relevant skills are not crowded out (#1759, #1762) (thanks @LinPower).
- Stats maintenance: keep skill stat migration fields synchronized by treating top-level stat fields as canonical during backfill/reconcile fallback reads (#1704) (thanks @momothemage).
- Skill install: render OpenClaw CLI commands with the bare slug that the current CLI accepts (#1807).
- Skills: keep historical tags out of public skill detail surfaces while preserving manager visibility (#1804) (thanks @deepujain).
- Skills moderation: keep hash-based scanner callbacks from overwriting skill-level moderation for older versions (#1805) (thanks @deepujain).
- Skills: prevent backport publishes from clobbering `latest` state and guard malformed persisted latest semver values during publish comparisons (#1832) (thanks @momothemage).
## 0.10.0 - 2026-04-05
### Added
- Design system: introduce a shared UI component library (`src/components/ui/`) built on Radix UI primitives — Button, Card, Badge, Tabs, Dialog, Input, Textarea, Label, Select, Avatar, Separator, Tooltip, ScrollArea, Sheet, Skeleton, and Table — following the shadcn/ui pattern with `cn()` + Tailwind utilities.
- Design system: `Button` supports `asChild` via Radix Slot for polymorphic rendering (e.g., wrapping `<Link>` without extra DOM).
- Layout: add `Container` component with `narrow` / `default` / `wide` size presets and `Breadcrumb` component for hierarchical navigation.
- Loading: add skeleton loading states (`SkillCardSkeleton`, `SkillDetailSkeleton`, `DashboardSkeleton`) replacing text-based "Loading..." indicators with animated placeholders.
- Errors: add `ErrorBoundary` with `resetKey` prop that auto-resets on route changes, wired into the root layout.
- Errors: surface fallback messages from Convex API error payloads in mutation/action error toasts.
- UX: add `EmptyState` component with icon, headline, description, and optional CTA action used across dashboard, stars, profile, and publish pages.
- Markdown: add `MarkdownPreview` component with `react-markdown`, `remark-gfm`, and `react-syntax-highlighter` for rich rendering of skill/plugin READMEs with syntax-highlighted code blocks, GFM tables, and task lists.
- Markdown: render tables with the new `Table` UI primitive for consistent styling across skill docs.
- Navigation: replace DropdownMenu-based mobile nav with a slide-out `Sheet` panel.
- Validation: add Zod schemas (`src/lib/schemas.ts`) for publish-skill, settings, report, and org forms.
- Management: restore capability-tags UI (crypto, requires-wallet, can-make-purchases, etc.) that was silently removed during the initial refactor.
- Management: add `.catch()` error handling with toast feedback on `setSoftDeleted` calls; prompt for hide/restore reasons.
### Changed
- CSS: migrate from a monolithic 5,161-line `styles.css` to Tailwind utilities on components, pruning CSS to ~1,000 lines (81% reduction). Dark mode now uses Tailwind `dark:` variants via a `@variant dark` directive bridging existing CSS custom properties.
- Pages: modernize all route pages (home, skills browse, skill detail, dashboard, settings, publish-skill, publish-plugin, import, about, CLI auth, stars, souls, user profile, org profile, management, plugins browse, plugin detail) from CSS class selectors to Tailwind + UI primitives.
- Skills browse: widen container to `wide` (1400px) for better use of screen space on desktop; same for plugins browse.
- Skills browse: replace text-based filter toggles with pill chips and modernize toolbar layout.
- Skill detail: migrate tab controls from CSS-styled buttons to Radix `Tabs` primitive with proper `role="tab"` accessibility.
- Skill detail: replace inline CSS class-based install card with `SkillInstallCard` using Card + Button primitives.
- Header/Footer: migrate from CSS classes to Tailwind utilities with responsive Sheet-based mobile navigation.
- Dashboard: replace CSS table layout with `Table` UI primitive; add metric cards and skeleton loading.
- Settings: modernize form inputs with `Input`/`Textarea`/`Label` primitives and structured layout.
- Publish: use `Dialog` primitive for modals; inline validation indicators; modernized file list display.
### Fixed
- Auth: `EmptyState` "Sign in" button on publish page now triggers GitHub OAuth via `useAuthActions` instead of linking to non-existent `/signin` route.
- API: fix plugins page dev-mode `{"error":"Only HTML requests are supported here"}` by routing SSR and localhost API fetches directly to the Convex site URL instead of through TanStack Start's request pipeline.
- API: fix CORS error when `credentials: "include"` conflicts with `Access-Control-Allow-Origin: *` by making credentials conditional on same-origin requests.
- API: fix SSR `packageApiUrl` to always use `VITE_CONVEX_SITE_URL` directly, avoiding `getRequestUrl()` failures when SSR request context is unavailable.
- Management: restore `setSoftDeleted` reason parameter for hide/restore actions.
- Tests: rename `settings.test.tsx` to `-settings.test.tsx` to exclude from TanStack Router's file-based route discovery.
- Tests: add `@convex-dev/auth/react` mock for `useAuthActions` in upload route tests.
- Tests: update skill detail tests for Radix tab roles (`role="tab"` instead of `role="button"`), skeleton loading classes (`animate-pulse`), and capability tag data.
- Tests: update skills index tests for refreshed UI copy (placeholder text, empty state wording, loading indicator patterns).
- Tests: update SkillDiffCard tests for Tailwind active-tab class (`shadow-sm` replacing `.is-active`).
- Tests: update packageApi tests for conditional credentials and SSR URL resolution.
## 0.9.0 - 2026-03-23
### Added
- Packages/Plugins: add a first-class OpenClaw package registry across the web app, CLI, and HTTP API. ClawHub now supports package browse/search/detail/version/file/download flows plus `clawhub package explore`, `clawhub package inspect`, and `clawhub package publish` for `skill`, `code-plugin`, and `bundle-plugin` packages. (#1093)
- Packages/Install: package downloads now ship install-ready archives with a `package/` root, support nested files like `dist/index.js`, and work directly with OpenClaw plugin install flows.
- Skills/Web: server-render public skill pages and OG assets for faster first loads, cleaner sharing previews, and better cache behavior.
### Changed
- Browse/Search: rebuild public browse/search around denormalized digests, one-shot HTTP fetches, and deterministic cursors so the homepage and `/skills` are faster, more cacheable, and less likely to hit stale-tab or pagination dead ends.
- Search: default skill search to relevance, keep load-more retryable after fetch failures, and tighten package/skill catalog query paths to reduce inconsistent results under load.
### Fixed
- Packages/Auth: authenticated owners can now list, search, inspect, download, and read files from their own private packages instead of private packages being direct-URL-only. (#1093)
- Packages/API: stabilize package latest-version pointers, cursor pagination, publish outputs, fallback release resolution, and app-origin auth handling so package publish/search/install flows stay reliable.
- Visibility/API: prevent skills owned by deleted/banned users from showing up in public detail pages, browse/search results, or version API routes.
- Skills/API: sanitize public skill and soul version/file reads so hidden or invalid version data does not leak through direct API access.
- Skills/Web: keep Monaco compare layout toggles reliable while defaulting narrow screens to inline mode (#828) (thanks @geoffrey-xiao).
## 0.8.0 - 2026-03-13
### Added
- Skills/Web: show skill owner avatar + handle on skill cards, lists, and detail pages (#312) (thanks @ianalloway).
- Skills/Web: add file viewer for skill version files on detail page (#44) (thanks @regenrek).
- CLI: add `uninstall` command for skills (#241) (thanks @superlowburn).
- Skills/API/CLI: add ownership transfer workflow with request/list/accept/reject/cancel flows.
- Skills/Web/API: surface platform/architecture labels and security evaluation results in v1 + inspect views (#499, #362).
- API: add structured skill moderation responses plus `GET /api/v1/skills/{slug}/moderation` with redacted public evidence and full owner/staff detail (#334) (thanks @ArthurzKV).
- Moderation: persist structured moderation snapshots (static scan + VT/LLM merged verdict, reason codes, and evidence) on skills and versions (#333) (thanks @ArthurzKV).
- Skills: make published skill licensing explicit and fixed to MIT-0; require publish consent, surface no-attribution messaging in web/CLI/API, and remove per-skill license metadata.
- Skill metadata: support env vars, dependency declarations, author, and links in parsed manifest metadata + install UI (#360) (thanks @mahsumaktas).
- Rate limiting: apply authenticated quotas by user bucket (vs shared IP), emit delay-based reset headers, and improve CLI 429 guidance/retries (#412) (thanks @lc0rp).
- Skills: reserve deleted slugs for prior owners (90-day cooldown) to prevent squatting; add admin reclaim flow (#298) (thanks @autogame-17).
- Moderation: ban flow soft-deletes owned skills (reversible) and removes them from vector search (#298) (thanks @autogame-17).
- Security/moderation: add bounded explainable auto-ban reasons for scam comments and protect moderator/admin accounts from automated bans.
- Moderation: banning users now also soft-deletes their authored comments (skill + soul), including legacy cleanup on re-ban.
- Quality gate: language-aware word counting (`Intl.Segmenter`) and new `cjkChars` signal to reduce false rejects for non-Latin docs.
- Jobs: run skill stat event processing every 5 minutes (was 15).
- Deploy: add frontend/backend drift detection plus hardened production smoke/deploy checks.
- API performance: batch resolve skill/soul tags in v1 list/get endpoints (fewer action->query round-trips) (#112) (thanks @mkrokosz).
- LLM helpers: centralize OpenAI Responses text extraction for changelog/summary/eval flows (#502) (thanks @ianalloway).
- Search/listing performance: cut embedding hydration and badge read bandwidth via `embeddingSkillMap` + denormalized skill badges; shift stat-doc sync to low-frequency cron (#441) (thanks @sethconvex).
- Search/listing performance: move public browse/search hydration onto `skillSearchDigest`, add non-suspicious index paths, and split trending rebuilds to stay under Convex document limits.
### Fixed
- API: accept legacy CLI publish payloads during the v1 migration (#815).
- Auth/UI: surface OAuth callback failures in the web UI instead of swallowing them (#688).
- Skills: allow ownership healing when the previous owner was deleted/banned, and sanitize owner data in public payloads (#689, #793).
- CLI: validate explicit `install --force --version` targets before removing an existing local skill, preventing data loss when the requested version does not exist (#825) (thanks @jonathandeamer).
- Skills/Web: debounce search URL updates on `/skills` to keep typing responsive, and cancel stale pending navigations on external query changes (#587) (thanks @neeravmakwana).
- Upload: keep folder-picking enabled after page refresh by reapplying `webkitdirectory`/`directory` on the file input ref (#551) (thanks @MunemHashmi).
- CLI publish: use a longer multipart upload timeout and normalize abort rejections into proper Errors (#550) (thanks @MunemHashmi).
- CLI: forward optional auth tokens for `search` and `explore` against authenticated registries (#608) (thanks @artdaal).
- CLI: respect `HTTPS_PROXY`/`HTTP_PROXY`/`NO_PROXY` env vars for outbound registry requests, with troubleshooting docs (#363) (thanks @kerrypotter).
- CLI: preserve registry base paths when composing API URLs for search/inspect/moderation commands (#486) (thanks @Liknox).
- CLI: show manual URL guidance when automatic browser opening is unavailable; add regression tests for opener errors (#163) (thanks @aronchick).
- API/CLI: expose skill security status in version inspect output, with schema wiring and CLI regression coverage (#362) (thanks @abutbul).
- Moderation: remove over-broad keyword flags for common auth/payment/crypto terms so legitimate skills stop tripping regex prefilters (#273) (thanks @superlowburn).
- Skills hard-delete: delete `commentReports` rows during moderation cleanup to avoid orphaned report records.
- Comments: hide entries authored by deleted/deactivated users in `comments:listBySkill`.
- Admin API: `POST /api/v1/users/reclaim` now performs non-destructive root-slug owner transfer
(preserves existing skill versions/stats/metadata) and clears active slug reservations.
- VirusTotal: use shared AV-engine fallback verdict mapping for pending/backfill flows and keep undetected-only results pending (#591) (thanks @Shuai-DaiDai).
- Skills/listing: keep non-suspicious browse pagination on one cursor family during `isSuspicious` backfill, and re-sync stale `latestVersionSummary` metadata fields (#572) (thanks @sethconvex).
- PWA: update `manifest.json` branding so installed apps show the correct ClawHub name (#569) (thanks @Glucksberg).
- Search/tests: cover soft-deleted skill filtering in vector hydration and lexical exact-slug fallback (#552) (thanks @MunemHashmi).
- Docs/dev: fix local setup instructions for Node support, Convex env vars, frontend port, and post-seed stats refresh (#584) (thanks @jack-piplabs).
- Docs/CLI: fix `explore` flag list indentation so `--limit` renders correctly in the command reference (#601) (thanks @gandli).
- Skill metadata: parse top-level `requires.*`, `primaryEnv`, and homepage fallbacks for security review accuracy (#548) (thanks @MunemHashmi).
- Users: sync handle on ensure when GitHub login changes (#293) (thanks @christianhpoe).
- Users/Auth: throttle GitHub profile sync on login; also sync avatar when it changes (#312) (thanks @ianalloway).
- Upload gate: fetch GitHub account age by immutable account ID (prevents username swaps) (#116) (thanks @mkrokosz).
- VT fallback: activate only VT-pending hidden skills when scans are unavailable/stale; keep quality/scanner-blocked skills hidden (#300) (thanks @superlowburn).
- API: return proper status codes for delete/undelete errors (#35) (thanks @sergical).
- API: for owners, return clearer status/messages for hidden/soft-deleted skills instead of a generic 404.
- HTTP/CORS: add preflight handler + include CORS headers on API/download errors; CLI: include auth token for owner-visible installs/updates (#146) (thanks @Grenghis-Khan).
- CLI: clarify `logout` only removes the local token; token remains valid until revoked in the web UI (#166) (thanks @aronchick).
- CLI: validate skill slugs used for filesystem operations (prevents path traversal) (#241) (thanks @superlowburn).
- Skills: keep global sorting across pagination on `/skills` (thanks @CodeBBakGoSu, #98).
- Skills: allow updating skill description/summary from frontmatter on subsequent publishes (#312) (thanks @ianalloway).
- Skills/Web: prevent filtered pagination dead-ends and loading-state flicker on `/skills`; move highlighted browse filtering into server list query (#339) (thanks @Marvae).
- Web: align `/skills` total count with public visibility and format header count (thanks @rknoche6, #76).
- Skills/Web: centralize public visibility checks and keep `globalStats` skill counts in sync incrementally; remove duplicate `/skills` default-sort fallback and share browse test mocks (thanks @rknoche6, #76).
- Moderation: clear stale `flagged.suspicious` flags when VirusTotal rescans improve to clean verdicts (#418) (thanks @Phineas1500).
- API tests: lock `Retry-After` behavior to relative-delay semantics for v1 search 429s (#421) (thanks @apoorvdarshan).
- CLI tests: assert 5xx HTTP responses still perform retry attempts before surfacing final error (#457) (thanks @YonghaoZhao722).
- GitHub import: improve storage/publish failure errors with actionable context; add regression tests for error formatting (#512) (thanks @vassiliylakhonin).
## 0.7.0 - 2026-02-16
Reconstructed from the `clawhub@0.7.0` npm publish timestamp (`2026-02-16T05:02:25Z`) and the repo version bump commit (`e352309`).
### Added
- Skills/Web: show owner avatars/handles across cards, lists, and detail pages (#312) (thanks @ianalloway).
- Skills/Web: add version file viewer on skill detail pages (#44) (thanks @regenrek).
- CLI: add `uninstall` for installed skills (#241) (thanks @superlowburn).
- Skills/Web: add non-suspicious browse filter, downloads-first browse defaults, and popular non-suspicious homepage sections.
- Web: compact-format skill and soul stats, plus split page models for skills/detail rendering.
- Skills: auto-generate missing summaries and add a resumable/self-scheduling summary backfill job.
- Moderation/Admin: add anti-spam publish caps, trust-tier quality checks, empty-skill cleanup tooling, and stronger moderator UX.
### Changed
- HTTP/CLI: centralize CORS handling and allow tokenized owner-visible reads through the CLI (#296, #297).
- API performance: batch resolve tags in v1 list/get flows to cut action-to-query round-trips (#112) (thanks @mkrokosz).
- Quality gate: add language-aware word counting and tighten spam/quarantine handling around publish flows.
### Fixed
- Skills/Web: fix initial sort wiring, keep global ordering across pagination, prevent pagination dead-ends/flicker, and harden cursor recovery (#92, #98, #339).
are already present. Reading from `users` adds the entire table to the
reactive read set and wastes bandwidth.
- Use `convex-helpers` Triggers to sync denormalized tables automatically.
Always add change detection — skip the write if no fields actually changed.
- Use compound indexes instead of JS filtering. If you're filtering docs after
the query, you're scanning documents you'll throw away.
- For search results scored by computed values (vector + lexical + popularity),
fetch all results once and paginate client-side. Don't re-run the full search
pipeline on "load more."
- Backfills on reactively-subscribed tables need `delayMs` between batches.
- Mutations that read >8 MB should use the Action → Query → Mutation pattern
to split reads across transactions.
## Convex Conventions
- All mutations import from `convex/functions.ts` (not `convex/_generated/server`)
to get trigger wrapping. Type imports still come from `convex/_generated/server`.
- NEVER use `--typecheck=disable` on `npx convex deploy`.
- Use `npx convex dev --once` to push functions once (not long-running watcher).
## Production Release
- Production deploys are manual-only. Merging to `main` does **not** deploy.
- Start the GitHub Actions `Deploy` workflow from `main` with `gh workflow run deploy.yml --repo openclaw/clawhub --ref main`.
- The workflow supports `full`, `backend`, and `frontend` targets.
-`frontend` currently waits for the Vercel production deploy on the selected `main` SHA and then runs smoke checks. It does not trigger Vercel directly yet.
- The workflow uses the `Production` environment for deploy secrets, but it does not wait for a separate approval.
- Required prod secret: `CONVEX_DEPLOY_KEY` on the `Production` environment. Optional smoke secret: `PLAYWRIGHT_AUTH_STORAGE_STATE_JSON`.
- CLI npm releases are manual-only and tag-based through `ClawHub CLI NPM Release`. Stable tags only: `vX.Y.Z`. Run a `preflight_only=true` pass first, then rerun with the same tag plus `preflight_run_id` for the real publish.
- Real CLI publishes wait at `npm-release` and rely on npm trusted publishing for `openclaw/clawhub` + `clawhub-cli-npm-release.yml` + `npm-release`.
## Testing
- Tests use `._handler` to call mutation handlers directly with mock `db` objects.
- Mock `db` objects MUST include `normalizeId: vi.fn()` for trigger wrapper compatibility.
<!-- convex-ai-start -->
This project uses [Convex](https://convex.dev) as its backend.
When working on Convex code, **always read `convex/_generated/ai/guidelines.md` first** for important guidelines on how to correctly use Convex APIs and patterns. The file contains rules that override what you may have learned about Convex from training data.
Convex agent skills for common tasks can be installed by running `npx convex ai-files install`.
Welcome! ClawHub is the public skill registry for [OpenClaw](https://github.com/openclaw/openclaw). We appreciate bug fixes, documentation improvements, and feature contributions.
- **Questions?** Ask in [#clawhub on Discord](https://discord.gg/clawd).
- **Bug fixes** — PRs are welcome.
- **New features or architectural changes** — please start with a Discord conversation in #clawhub first so we can align on scope.
## Local Development Setup
### Prerequisites
- [Bun](https://bun.sh/) (Convex CLI runs via `bunx`, no global install needed)
- [Node.js](https://nodejs.org/) v18, 20, 22, or 24 (required by the local Convex backend; v25+ is not yet supported)
- [Worktrunk](https://github.com/max-sixty/worktrunk) (`wt`) for `bun run dev:worktree` and disposable/Codex worktrees. On macOS, `brew install worktrunk` is the quickest path; shell integration is optional.
### Install and configure
```bash
bun install
cp .env.local.example .env.local
```
Edit `.env.local` with the following values for **local Convex**:
```bash
# Frontend
VITE_CONVEX_URL=http://127.0.0.1:3210
VITE_CONVEX_SITE_URL=http://127.0.0.1:3211
SITE_URL=http://localhost:3000
# Convex Auth / HTTP routes
CONVEX_SITE_URL=http://127.0.0.1:3211
# Deployment used by `bunx convex dev`
CONVEX_DEPLOYMENT=anonymous:anonymous-clawhub
```
Local Convex serves the function endpoint on port 3210 and HTTP routes (`/api/*` and auth callbacks) through the site proxy on port 3211.
### GitHub OAuth App (for login)
1. Go to [github.com/settings/developers](https://github.com/settings/developers) and create a new OAuth App.
2. Set **Homepage URL** to `http://localhost:3000`.
3. Set **Authorization callback URL** to `http://127.0.0.1:3211/api/auth/callback/github`.
4. Copy the Client ID and generate a Client Secret.
### Run the Convex backend
Start the local Convex backend first — other setup steps depend on it:
```bash
bunx convex dev --typecheck=disable
```
### Set backend environment variables
The Convex backend has its own env var store separate from `.env.local`. With the backend running, open a new terminal and set the required variables:
```bash
bunx convex env set AUTH_GITHUB_ID <your-client-id>
bunx convex env set AUTH_GITHUB_SECRET <your-client-secret>
bunx convex env set SITE_URL http://localhost:3000
```
### JWT keys (for Convex Auth)
With the backend still running, generate the signing keys:
```bash
bunx @convex-dev/auth
```
This sets `JWT_PRIVATE_KEY` and `JWKS` on the Convex backend and outputs values you can also save to `.env.local` for reference.
### Run the frontend
```bash
bun run dev -- --port 3000
```
Change the port if 3000 is already in use, and update `SITE_URL` in both `.env.local` and the Convex backend (`bunx convex env set SITE_URL ...`) to match.
### Worktree/Codex fast path
Use this path for disposable branches, Codex sessions, or parallel worktrees after one source worktree already has a working `.env.local` and `.convex` local Convex setup:
```bash
bun run setup:worktree
bun run dev:worktree
wt --yes url
wt --yes stop
```
`setup:worktree` finds a usable source worktree and symlinks `.env.local` plus `.convex` into the current checkout. If discovery picks the wrong source, pass one explicitly:
```bash
bun run setup:worktree -- --from /path/to/source/worktree
CLAWHUB_WORKTREE_SOURCE=/path/to/source/worktree bun run setup:worktree
```
`dev:worktree` is the Worktrunk entrypoint. It runs the hooks in `.config/wt.toml`, copies ignored dependencies listed in `.worktreeinclude` when possible, falls back to `bun install` if Vite is missing, and starts detached services on a branch-hashed loopback port. Use `wt --yes url` from the same worktree to print the URL.
The detached server writes runtime state under `.codex/runtime/`. Stop it with `wt --yes stop` before removing the worktree.
### Seed the database
Populate local QA fixtures and the committed public corpus so the UI isn't empty:
```bash
bun run seed:dev
```
`seed:dev` runs worktree setup, starts or waits for local Convex, seeds the hand-authored local QA fixtures, imports the committed public corpus, and refreshes cached global stats. It is safe to rerun after fixture or schema changes.
Lower-level seed commands are available for manual recovery or focused fixture work:
```bash
# local moderation/security fixtures only
bunx convex run --no-push devSeed:seedLocalFixtures
# committed public corpus only
bun run seed:public-corpus
# validate the committed public corpus fixture
bun run validate:public-corpus
# 50 extra skills for pagination testing (optional)
bunx convex run --no-push devSeedExtra:seedExtraSkillsInternal
# Refresh cached global stats after manual seeding
bunx convex run --no-push statsMaintenance:updateGlobalStatsAction
```
To reset and re-seed:
```bash
bunx convex run --no-push devSeed:seedLocalFixtures '{"reset": true}'
bun run seed:public-corpus -- --reset
bunx convex run --no-push statsMaintenance:updateGlobalStatsAction
```
Without `OPENAI_API_KEY`, public corpus import still works, but semantic search quality degrades because embeddings fall back to zero vectors.
### Worktree troubleshooting
-`wt: command not found`: install Worktrunk, then rerun `bun run dev:worktree`. Manual `bun run dev` plus `bunx convex dev --typecheck=disable` still works without Worktrunk.
- Missing `.env.local` or `.convex`: run `bun run setup:worktree -- --from /path/to/source/worktree`. The source must contain `.env.local` and, for local Convex deployments, `.convex/local/default/config.json`.
- Wrong local Convex deployment: make sure `CONVEX_DEPLOYMENT` in `.env.local` matches the local Convex deployment in `.convex/local/default/config.json` when using a `local:` deployment.
- Port mismatch: local Convex normally serves cloud functions at `http://127.0.0.1:3210` and HTTP routes/auth callbacks at `http://127.0.0.1:3211`. Keep `VITE_CONVEX_URL`, `VITE_CONVEX_SITE_URL`, and `CONVEX_SITE_URL` aligned with the local config.
-`wt step copy-ignored` reports that `.convex` cannot be copied: this can happen when `.convex` is a symlink to the source worktree. The Worktrunk hook continues; confirm `.env.local`, `.convex`, and `node_modules/.bin/vite` exist before debugging deeper.
- Local Convex functions are not queryable yet during seeding: leave `bunx convex dev --typecheck=disable` running or rerun `bun run seed:dev`; the seed runner retries while Convex finishes pushing functions.
- Local seeding hits a transient Convex write conflict: `seed:public-corpus` retries retryable batch conflicts. If retries are exhausted, stop other local writers and rerun `bun run seed:dev`.
- Stale detached services: run `wt --yes stop`, then inspect `.codex/runtime/dev-worktree.log` if the server still does not restart cleanly.
### Optional environment variables
These features degrade gracefully without their keys:
Run the narrowest meaningful check while iterating, then run the matching CI aliases before handoff:
- All PRs: `bun run ci:static`.
- Source or test changes: focused tests for the touched behavior plus `bun run ci:unit` unless the change is docs/config-only or a maintainer asks to rely on CI.
- App runtime, Convex, or build changes: `bun run ci:types-build`.
- Package changes: `bun run ci:packages`.
- HTTP/API/CLI integration changes: `bun run ci:e2e-http`.
- Browser smoke or visual behavior changes: `bun run ci:playwright-smoke`, `bun run test:pw:local-auth`, and/or `bun run proof:ui` depending on the touched flow.
`bun run ci:pr` is the local aggregate for the non-browser PR gates. See [`specs/ci.md`](specs/ci.md) for the full CI contract.
### Crabbox remote checks
Maintainers can run the same checks in a Crabbox lease instead of spending local
CPU. ClawHub uses Crabbox as the agent-facing command surface; the Testbox
workflow is only the backend for the default Blacksmith provider.
```bash
bun run crabbox:warmup -- --provider blacksmith-testbox
bun run crabbox:run -- --provider blacksmith-testbox --shell -- "bun run lint"
bun run crabbox:run -- --provider blacksmith-testbox --shell -- "bun run test"
bun run crabbox:run -- --provider blacksmith-testbox --shell -- "bun run build"
```
Use `--id <id-or-slug>` with `crabbox:run` when reusing an existing warmed lease,
and stop disposable leases with `bun run crabbox:stop -- --provider <provider>
<id-or-slug>`.
Use `CLAWHUB_LOCAL_CHECK_MODE=throttled` or `CLAWHUB_LOCAL_CHECK_MODE=full` as
the explicit local escape hatch when you intentionally want laptop-side proof.
If Crabbox auth/provider access is missing, report that instead of falling back
to a broad local gate that can bog down a dev machine.
**PR guidelines:**
- Keep PRs focused — one concern per PR.
- Use [Conventional Commits](https://www.conventionalcommits.org/): `feat:`, `fix:`, `chore:`, `docs:`, etc.
- Include test commands and screenshots for UI changes.
- Write a clear description of what changed and why.
## AI-Generated Code
AI-assisted contributions are welcome. When submitting AI-generated or AI-assisted code:
- Note it in the PR description.
- Describe the level of testing you applied.
- Include prompts if useful for reviewers.
- Confirm that you understand and can maintain the code.
## Security Reporting
Report vulnerabilities to **security@openclaw.ai** with:
- Severity assessment
- Technical reproduction steps
- Suggested remediation
See [`docs/security.md`](docs/security.md) for moderation and upload gating details.
## Reading Order for New Contributors
1. This file (local setup)
2. [`docs/clawhub.md`](docs/clawhub.md) — public registry overview
This document outlines the design rules, patterns, and guidelines for the ClawHub platform to ensure consistency, accessibility, and maintainability across all components.
---
## Color System
### Brand Palette (OpenClaw)
ClawHub uses a strict **3-5 color palette** based on the OpenClaw brand:
- Code-plugin manifests must include `openclaw.compat.pluginApi` and `openclaw.build.openclawVersion`; see [`docs/cli.md`](docs/cli.md) for a minimal example.
-`convex/` — schema + queries/mutations/actions + HTTP API routes.
-`packages/schema/` — shared API types/routes for the CLI and app.
-`docs/spec.md` — product + implementation spec (good first read).
-[`docs/`](docs/README.md) — publishable ClawHub public/operator docs for users, publishers, API clients, and deploy operators.
- [`specs/`](specs/README.md) — product specs, plans, regression notes, and design history.
- [`specs/spec.md`](specs/spec.md) — product + implementation spec (good first read for maintainers).
## Local dev
Prereqs: Bun + Convex CLI.
Prereqs: [Bun](https://bun.sh/) (Convex runs via `bunx`, no global install needed). The detached worktree path also requires [Worktrunk](https://github.com/max-sixty/worktrunk) (`wt`).
```bash
bun install
cp .env.local.example .env.local
# edit .env.local — see CONTRIBUTING.md for local Convex values
# terminal A: web app
# terminal A: local Convex backend
bunx convex dev
# terminal B: web app (port 3000)
bun run dev
# terminal B: Convex dev deployment
bunx convex dev
# detached/Codex worktree preview
bun run setup:worktree
bun run dev:worktree
wt --yes url
# seed local QA fixtures and the public corpus
bun run seed:dev
```
## Auth (GitHub OAuth) setup
Create a GitHub OAuth App, set `AUTH_GITHUB_ID` / `AUTH_GITHUB_SECRET`, then:
@@ -134,7 +195,7 @@ To show CLI help (recommended for nix plugins), include the `cli --help` output:
---
name:padel
description:Check padel court availability and manage bookings via Playtomic.
metadata:{"clawdbot":{"cliHelp":"padel --help\\nUsage: padel [command]\\n"}}
metadata:{"clawdbot": { "cliHelp": "padel --help\\nUsage: padel [command]\\n"}}
---
```
@@ -142,7 +203,7 @@ metadata: {"clawdbot":{"cliHelp":"padel --help\\nUsage: padel [command]\\n"}}
## Skill metadata
Skills declare their runtime requirements (env vars, binaries, install specs) in the `SKILL.md` frontmatter. ClawHub's security analysis checks these declarations against actual skill behavior.
Skills declare their runtime requirements (env vars, binaries, install specs) in the `SKILL.md` frontmatter. ClawHub's security analysis checks these declarations against actual skill behavior; medium review findings stay visible, and the suspicious filter is reserved for high-impact or malicious concerns.
Full reference: [`docs/skill-format.md`](docs/skill-format.md#frontmatter-metadata)
- HTTP endpoints are defined in `convex/http.ts` and require an `httpAction` decorator. For example:
```typescript
import{httpRouter}from"convex/server";
import{httpAction}from"./_generated/server";
consthttp=httpRouter();
http.route({
path:"/echo",
method:"POST",
handler: httpAction(async(ctx,req)=>{
constbody=awaitreq.bytes();
returnnewResponse(body,{status: 200});
}),
});
```
- HTTP endpoints are always registered at the exact path you specify in the `path` field. For example, if you specify `/api/someRoute`, the endpoint will be registered at `/api/someRoute`.
| Null | null | `null` | `v.null()` | JavaScript's `undefined` is not a valid Convex value. Functions the return `undefined` or do not return will return `null` when called from a client. Use `null` instead. |
| Int64 | bigint | `3n` | `v.int64()` | Int64s only support BigInts between -2^63 and 2^63-1. Convex supports `bigint`s in most modern browsers. |
| Float64 | number | `3.1` | `v.number()` | Convex supports all IEEE-754 double-precision floating point numbers (such as NaNs). Inf and NaN are JSON serialized as strings. |
| Boolean | boolean | `true` | `v.boolean()` |
| String | string | `"abc"` | `v.string()` | Strings are stored as UTF-8 and must be valid Unicode sequences. Strings must be smaller than the 1MB total size limit when encoded as UTF-8. |
| Bytes | ArrayBuffer | `new ArrayBuffer(8)` | `v.bytes()` | Convex supports first class bytestrings, passed in as `ArrayBuffer`s. Bytestrings must be smaller than the 1MB total size limit for Convex types. |
| Array | Array | `[1, 3.2, "abc"]` | `v.array(values)` | Arrays can have at most 8192 values. |
| Object | Object | `{a: "abc"}` | `v.object({property: value})` | Convex only supports "plain old JavaScript objects" (objects that do not have a custom prototype). Objects can have at most 1024 entries. Field names must be nonempty and not start with "$" or "_". |
| Record | Record | `{"a": "1", "b": "2"}` | `v.record(keys, values)` | Records are objects at runtime, but can have dynamic keys. Keys must be only ASCII characters, nonempty, and not start with "$" or "\_". |
### Function registration
- Use `internalQuery`, `internalMutation`, and `internalAction` to register internal functions. These functions are private and aren't part of an app's API. They can only be called by other Convex functions. These functions are always imported from `./_generated/server`.
- Use `query`, `mutation`, and `action` to register public functions. These functions are part of the public API and are exposed to the public Internet. Do NOT use `query`, `mutation`, or `action` to register sensitive internal functions that should be kept private.
- You CANNOT register a function through the `api` or `internal` objects.
- ALWAYS include argument validators for all Convex functions. This includes all of `query`, `internalQuery`, `mutation`, `internalMutation`, `action`, and `internalAction`.
### Function calling
- Use `ctx.runQuery` to call a query from a query, mutation, or action.
- Use `ctx.runMutation` to call a mutation from a mutation or action.
- Use `ctx.runAction` to call an action from an action.
- ONLY call an action from another action if you need to cross runtimes (e.g. from V8 to Node). Otherwise, pull out the shared code into a helper async function and call that directly instead.
- Try to use as few calls from actions to queries and mutations as possible. Queries and mutations are transactions, so splitting logic up into multiple calls introduces the risk of race conditions.
- All of these calls take in a `FunctionReference`. Do NOT try to pass the callee function directly into one of these calls.
- When using `ctx.runQuery`, `ctx.runMutation`, or `ctx.runAction` to call a function in the same file, specify a type annotation on the return value to work around TypeScript circularity limitations. For example,
- Use the `api` object defined by the framework in `convex/_generated/api.ts` to call public functions registered with `query`, `mutation`, or `action`.
- Use the `internal` object defined by the framework in `convex/_generated/api.ts` to call internal (or private) functions registered with `internalQuery`, `internalMutation`, or `internalAction`.
- Convex uses file-based routing, so a public function defined in `convex/example.ts` named `f` has a function reference of `api.example.f`.
- A private function defined in `convex/example.ts` named `g` has a function reference of `internal.example.g`.
- Functions can also registered within directories nested within the `convex/` folder. For example, a public function `h` defined in `convex/messages/access.ts` has a function reference of `api.messages.access.h`.
Note: `paginationOpts` is an object with the following properties:
-`numItems`: the maximum number of documents to return (the validator is `v.number()`)
-`cursor`: the cursor to use to fetch the next page of documents (the validator is `v.union(v.string(), v.null())`)
- A query that ends in `.paginate()` returns an object that has the following properties:
- page (contains an array of documents that you fetches)
- isDone (a boolean that represents whether or not this is the last page of documents)
- continueCursor (a string that represents the cursor to use to fetch the next page of documents)
## Schema guidelines
- Always define your schema in `convex/schema.ts`.
- Always import the schema definition functions from `convex/server`.
- System fields are automatically added to all documents and are prefixed with an underscore. The two system fields that are automatically added to all documents are `_creationTime` which has the validator `v.number()` and `_id` which has the validator `v.id(tableName)`.
- Always include all index fields in the index name. For example, if an index is defined as `["field1", "field2"]`, the index name should be "by_field1_and_field2".
- Index fields must be queried in the same order they are defined. If you want to be able to query by "field1" then "field2" and by "field2" then "field1", you must create separate indexes.
- Do not store unbounded lists as an array field inside a document (e.g. `v.array(v.object({...}))`). As the array grows it will hit the 1MB document size limit, and every update rewrites the entire document. Instead, create a separate table for the child items with a foreign key back to the parent.
- Separate high-churn operational data (e.g. heartbeats, online status, typing indicators) from stable profile data. Storing frequently updated fields on a shared document forces every write to contend with reads of the entire document. Instead, create a dedicated table for the high-churn data with a foreign key back to the parent record.
## Authentication guidelines
- Convex supports JWT-based authentication through `convex/auth.config.ts`. ALWAYS create this file when using authentication. Without it, `ctx.auth.getUserIdentity()` will always return `null`.
- Example `convex/auth.config.ts`:
```typescript
exportdefault{
providers:[
{
domain:"https://your-auth-provider.com",
applicationID:"convex",
},
],
};
```
The `domain` must be the issuer URL of the JWT provider. Convex fetches `{domain}/.well-known/openid-configuration` to discover the JWKS endpoint. The `applicationID` is checked against the JWT `aud` (audience) claim.
- Use `ctx.auth.getUserIdentity()` to get the authenticated user's identity in any query, mutation, or action. This returns `null` if the user is not authenticated, or a `UserIdentity` object with fields like `subject`, `issuer`, `name`, `email`, etc. The `subject` field is the unique user identifier.
- In Convex `UserIdentity`, `tokenIdentifier` is guaranteed and is the canonical stable identifier for the authenticated identity. For any auth-linked database lookup or ownership check, prefer `identity.tokenIdentifier` over `identity.subject`. Do NOT use `identity.subject` alone as a global identity key.
- NEVER accept a `userId` or any user identifier as a function argument for authorization purposes. Always derive the user identity server-side via `ctx.auth.getUserIdentity()`.
- When using an external auth provider with Convex on the client, use `ConvexProviderWithAuth` instead of `ConvexProvider`:
The `useAuth` prop must return `{ isLoading, isAuthenticated, fetchAccessToken }`. Do NOT use plain `ConvexProvider` when authentication is needed — it will not send tokens with requests.
## Typescript guidelines
- You can use the helper typescript type `Id` imported from './\_generated/dataModel' to get the type of the id for a given table. For example if there is a table called 'users' you can use `Id<'users'>` to get the type of the id for that table.
- Use `Doc<"tableName">` from `./_generated/dataModel` to get the full document type for a table.
- Use `QueryCtx`, `MutationCtx`, `ActionCtx` from `./_generated/server` for typing function contexts. NEVER use `any` for ctx parameters — always use the proper context type.
- If you need to define a `Record` make sure that you correctly provide the type of the key and value in the type. For example a validator `v.record(v.id('users'), v.string())` would have the type `Record<Id<'users'>, string>`. Below is an example of using `Record` with an `Id` type in a query:
```ts
import{query}from"./_generated/server";
import{Doc,Id}from"./_generated/dataModel";
exportconstexampleQuery=query({
args:{userIds: v.array(v.id("users"))},
handler: async(ctx,args)=>{
constidToUsername: Record<Id<"users">,string>={};
for(constuserIdofargs.userIds){
constuser=awaitctx.db.get("users",userId);
if(user){
idToUsername[user._id]=user.username;
}
}
returnidToUsername;
},
});
```
- Be strict with types, particularly around id's of documents. For example, if a function takes in an id for a document in the 'users' table, take in `Id<'users'>` rather than `string`.
## Full text search guidelines
- A query for "10 messages in channel '#general' that best match the query 'hello hi' in their body" would look like:
- Do NOT use `filter` in queries. Instead, define an index in the schema and use `withIndex` instead.
- If the user does not explicitly tell you to return all results from a query you should ALWAYS return a bounded collection instead. So that is instead of using `.collect()` you should use `.take()` or paginate on database queries. This prevents future performance issues when tables grow in an unbounded way.
- Never use `.collect().length` to count rows. Convex has no built-in count operator, so if you need a count that stays efficient at scale, maintain a denormalized counter in a separate document and update it in your mutations.
- Convex queries do NOT support `.delete()`. If you need to delete all documents matching a query, use `.take(n)` to read them in batches, iterate over each batch calling `ctx.db.delete(row._id)`, and repeat until no more results are returned.
- Convex mutations are transactions with limits on the number of documents read and written. If a mutation needs to process more documents than fit in a single transaction (e.g. bulk deletion on a large table), process a batch with `.take(n)` and then call `ctx.scheduler.runAfter(0, api.myModule.myMutation, args)` to schedule itself to continue. This way each invocation stays within transaction limits.
- Use `.unique()` to get a single document from a query. This method will throw an error if there are multiple documents that match the query.
- When using async iteration, don't use `.collect()` or `.take(n)` on the result of a query. Instead, use the `for await (const row of query)` syntax.
### Ordering
- By default Convex always returns documents in ascending `_creationTime` order.
- You can use `.order('asc')` or `.order('desc')` to pick whether a query is in ascending or descending order. If the order isn't specified, it defaults to ascending.
- Document queries that use indexes will be ordered based on the columns in the index and can avoid slow table scans.
## Mutation guidelines
- Use `ctx.db.replace` to fully replace an existing document. This method will throw an error if the document does not exist. Syntax: `await ctx.db.replace('tasks', taskId, { name: 'Buy milk', completed: false })`
- Use `ctx.db.patch` to shallow merge updates into an existing document. This method will throw an error if the document does not exist. Syntax: `await ctx.db.patch('tasks', taskId, { completed: true })`
## Action guidelines
- Always add `"use node";` to the top of files containing actions that use Node.js built-in modules.
- Never add `"use node";` to a file that also exports queries or mutations. Only actions can run in the Node.js runtime; queries and mutations must stay in the default Convex runtime. If you need Node.js built-ins alongside queries or mutations, put the action in a separate file.
-`fetch()` is available in the default Convex runtime. You do NOT need `"use node";` just to use `fetch()`.
- Never use `ctx.db` inside of an action. Actions don't have access to the database.
- Below is an example of the syntax for an action:
```ts
import{action}from"./_generated/server";
exportconstexampleAction=action({
args:{},
handler: async(ctx,args)=>{
console.log("This action does not return anything");
returnnull;
},
});
```
## Scheduling guidelines
### Cron guidelines
- Only use the `crons.interval` or `crons.cron` methods to schedule cron jobs. Do NOT use the `crons.hourly`, `crons.daily`, or `crons.weekly` helpers.
- Both cron methods take in a FunctionReference. Do NOT try to pass the function directly into one of these methods.
- Define crons by declaring the top-level `crons` object, calling some methods on it, and then exporting it as default. For example,
- You can register Convex functions within `crons.ts` just like any other file.
- If a cron calls an internal function, always import the `internal` object from '\_generated/api', even if the internal function is registered in the same file.
## Testing guidelines
- Use `convex-test` with `vitest` and `@edge-runtime/vm` to test Convex functions. Always install the latest versions of these packages. Configure vitest with `environment: "edge-runtime"` in `vitest.config.ts`.
Test files go inside the `convex/` directory. You must pass a module map from `import.meta.glob` to `convexTest`:
The `modules` argument is required so convex-test can discover and load function files. The `/// <reference types="vite/client" />` directive is needed for TypeScript to recognize `import.meta.glob`.
## File storage guidelines
- The `ctx.storage.getUrl()` method returns a signed URL for a given file. It returns `null` if the file doesn't exist.
- Do NOT use the deprecated `ctx.storage.getMetadata` call for loading a file's metadata.
Instead, query the `_storage` system table. For example, you can use `ctx.db.system.get` to get an `Id<"_storage">`.
'Your account has been banned for uploading malicious skills. If you believe this is a mistake, please contact security@openclaw.ai and we will work with you to restore access.'
"This account has been banned and cannot sign in. If you believe this is a mistake, please contact security@openclaw.ai and we will review it.";
exportconstDELETED_ACCOUNT_REAUTH_MESSAGE=
'This account has been permanently deleted and cannot be restored.'
"This account has been permanently deleted and cannot be restored.";
Some files were not shown because too many files have changed in this diff
Show More
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.