swamp extension search consistently returns empty results regardless of the query, even though swamp extension info @swamp/aws/s3 and swamp extension pull work fine with the same registry.

Steps to Reproduce

swamp extension search aws --json
# Returns: {"query": "aws", "results": []}

swamp extension search "" --json
# Returns: {"query": "", "results": []}

# But this works:
swamp extension info @swamp/aws/s3 --json
# Returns full metadata

Expected Behavior

swamp extension search aws should return matching extensions from the registry (at minimum @swamp/aws/s3, @webframp/aws/cost-explorer, etc.).

Actual Behavior

Always returns {"query": "...", "results": []} regardless of query.

Environment

swamp version: 20260530.005533.0-sha.1c117111
Platform: macOS Darwin 24.6.0
Auth: authenticated as webframp
Registry: swamp-club.com

02Bog Flow

Shipped

5/31/2026, 4:59:48 AM

Click a lifecycle step above to view its details.

03Sludge Pulse

keeb assigned keeb5/31/2026, 4:07:37 AM

keeb commented 5/31/2026, 4:16:21 AM

Thanks for the report — I dug into this and currently can't reproduce it, and the registry looks healthy. A few things to help narrow it down:

I checked the server directly:

GET https://swamp-club.com/api/v1/extensions/search?q=aws
→ {"extensions":[…],"meta":{"total":373}}

An empty-query browse returns results too. I also ran the CLI at your exact version (…sha.1c117111) against prod, and both swamp extension search aws --json and swamp extension search "" --json returned full results.

One thing stood out: the output you pasted ({"query":"aws","results":[]}) has a results key, but neither the server response ({"extensions":…,"meta":…}) nor the CLI's --json output (query / extensions / meta) uses that key. That makes me suspect the output came from a different build than the version string suggests.

Could you share:

The raw, unedited output of swamp extension search aws --json (no trimming).
swamp --version and which swamp — to confirm the binary on $PATH matches the reported version (a stale/shimmed binary is a common cause).
The registry host the CLI is actually hitting — any SWAMP_REGISTRY-style env var or config override, and whether you're pointed at swamp-club.com vs a self-hosted/alt registry.
Whether it still happens. If it was a one-time blip, the extensions_search Atlas index may have been rebuilding when you hit it.

With the raw output + version/host confirmation I can pin down whether anything server-side needs fixing.

keeb commented 5/31/2026, 4:59:56 AM

Thanks @webframp for reporting this! The fix has been merged and a release is on its way. We appreciate your contribution to swamp.

Annotate and retain past workflow runs and data after the fact

Publish agent-facing projections of the manual: /llms.txt, .md pages, and llms-full.txt

Leaderboard: top-tier username styling (tier-sovereign-text) reads like core-team styling

User token page (/u/<user>) shows only "swamp_..." for every API key, making leaked-key identification impossible

Redaction regex boundary bug: label_base64 secrets with an unrecognized label pass through unredacted (e.g. swamp_ API keys)

Explore: track release velocity, and let more than one person turn the crank

Document env.* namespace for model-instance globalArguments (host-portable config)

repo upgrade/init hardcode absolute swamp binary path in hook commands, breaking cross-machine portability

Datastore config should support vault expressions or env var references for tokens

Add native support for the Pi coding harness

access token mint: plaintext secret never surfaced to user, vault read-secret cannot access _token-secrets

serve: catalog backfill indexes only session-local data, data query returns wrong results for pre-existing entries

data search: full filesystem walk on every call, bypasses catalog index

swamp serve OOMs on repos with 2000+ model definitions

Feature: user-configurable redaction rules (.swamp/redaction.yaml)

Collective management API for extension-based automation

Collective leaderboard: activity metrics aggregated by identity group

Quality rubric + push gate for version upgrade chain correctness

Explore: CLI binary update integrity lacks independent verification

Explore: reconcile quality rubric's dormant provenance factor

Explore: pull-time signature verification for extensions

Explore: transparency-log integration (Rekor) for extension signatures

Explore: publish-time artifact signing for extensions (cosign keyless)

Expose resource attributes in DataHandle for workflow report stepExecutions

.swamp.yaml rewritten with quote style change + lastSkillMigrationWarning on read-only operations

--quiet mode does not suppress in-process extension logger output

Expose workflow inputs in WorkflowReportContext

Kiro CLI v3 permissions: no capability covers disclose_context (skill loading)

Quest page: all leaderboard usernames show 'Swamp Baby' title

provisioner.provision fails with 'Cannot read properties of undefined (reading trim)' at method_execution_service.ts:852

No retention/prune for .swamp/workflow-runs and .swamp/outputs

Re-publish of an existing extension succeeds but latestVersion/pull never advances to it

Genesis Pass tier 14 (Halogen Saint) shows claimed 260 XP before its own threshold, contradicting the same page's progress tracker

swamp workflow history search OOMs on workflows with large run history

extension pull fails permanently when a pinned exact-version dependency is removed from the registry

Add swamp straitjacket: opt-in, binary-shipped agent guardrail hooks

Add associative info to user profiles: collective membership + collaborative contributions

Extension skill should explicitly prohibit bare 'zod' imports (scorer sandbox fails)

Global skills should auto-sync when binary version advances

serve: V8 out-of-memory crash during catalog init on large repos (regression from #841)

Model method execution overhead: 10s+ per trivial operation, global lock prevents concurrency

serve startup time regression: synchronous catalog init delays WebSocket listener by ~4.5 minutes

Per-model LockTimeoutError at 60s causes cascading failures under concurrent access

`extension quality` false-positive bare-import detection on string literal "flexible"

extension quality fails to resolve bare specifiers — contradicts fmt no-import-prefix rule

swamp-extension adversarial review skill needs mandatory mechanical verification checklist

Workflow engine resolves extension methods against base type, ignoring extension-registered methods

Enforce adversarial review gate before extension push

vault annotate --url fails with query params on @swamp/aws-sm

workflow approve/resume cannot find suspended run when using S3 datastore

datastore compact VACUUM fails with ERR_SQLITE_ERROR

Report type filtering in report search

extension search: empty results from CLI despite known extensions

workflow approve/resume cannot find suspended runs

swamp data gc does not remove physical version directories from disk

Direct execution @type prefix fails for repo-local extension model types

Extension ecosystem: shared utility library, version sync tooling, and HTTP resilience patterns

Add 'swamp issue comment' command for updating existing issues

Close #327 — fixed in 20260511.160514.0-sha.9d03b09a

Nested workflow task fails with 'Bad resource ID' when workflowIdOrName uses @collective/ prefix

forEach self.* in modelIdOrName not resolved in runtime execution path

Resolve self.* expressions in modelIdOrName during forEach expansion

extension quality/fmt fail on pulled extensions (path mismatch)

vault: add read-secret CLI command for agent-driven secret retrieval

performance degrades significantly with large SQLite catalog

summarise: timeout/hang on repos with many workflow runs

Agentic CLI improvements: --json stdout isolation, array inputs, and --repo-dir consistency

data delete fails with "Directory not empty (os error 39)" when concurrent writes are active

data query: stepName and jobName fields always empty in CEL results

redmine extension: adopt state machine patterns from @magistr for agent-driven workflows

Support multi-agent repo initialization (multiple --tool targets)

swamp repo init --tool kiro does not create .kiro/settings/cli.json

Add skills extension type for bundling agent/human guidance documents

Extension skills missing repository initialization and publishing prerequisites

Relationships

#497 extension search: empty results from CLI despite known extensions

Problem

Steps to Reproduce

Expected Behavior

Actual Behavior