# Reported issues for Argus Retrieval Pod holds 12 of 12 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user. Back to [Argus Retrieval](/mcp/argus-retrieval). ## Most discussed ### Implement S3 extraction finalization and retrieval composition ## Wayfinder slice Implement Task 4 / S3 from `docs/superpowers/plans/2026-07-27-retrieval-evidence-mechanical-port.md`. Scope: - immutable extraction plans/outcomes and closed truth tables - privacy-safe bounded attempt traces and durable atomic acceptance - separate archive lookup from externally authorized archive creation - compose accepted retrieval clusters with proven extraction artifacts - preserve temporary narrow retrieval evidence protocol until S7 Acceptance and verification are e [Read the thread](https://github.com/Khamel83/argus/issues/88) · 2026-07-27 · closed · 4 comments ### Implement S2 provider batch normalization and private failure evidence ## Wayfinder slice Implement Task 3 / S2 from `docs/superpowers/plans/2026-07-27-retrieval-evidence-mechanical-port.md`. Scope: - normalize all 14 provider adapters behind immutable evidence batches - freeze fixture applicability for success, empty, malformed, auth, exhaustion, policy, timeout, rate limit, and 5xx behavior - enforce privacy/bounds, retry/redirect/deadline semantics, typed controls, and extractor fixture compatibility - preserve the legacy broker tuple via the temporary adapter [Read the thread](https://github.com/Khamel83/argus/issues/86) · 2026-07-27 · closed · 4 comments ### Cut over private homelab production and retire duplicate authorities ## Parent [Wayfinder: make Argus a reliable homelab retrieval platform for Maya](https://github.com/Khamel83/argus/issues/23) ## What to build Complete the production transition as one reversible cutover: publish only private Tailscale ingress, move Maya and agent clients to the authoritative homelab stack, prove the accepted paths, and retire every OCI, Mac-production, LAN, and host-worker duplicate. ## Acceptance criteria - [ ] API and MCP Docker backends bind host loopback only; PostgreS [Read the thread](https://github.com/Khamel83/argus/issues/42) · 2026-07-23 · closed · 3 comments ### Audit Argus documentation against current contracts and production ## Parent [Wayfinder: make Argus stable and competitively optimized without a rewrite](https://github.com/Khamel83/argus/issues/58) ## Question Which Argus documentation surfaces are stale, contradictory, incomplete, or unsafe when compared with the current code, generated/public metadata, deployed homelab runtime, provider profile, HTTP/MCP contracts, PostgreSQL recovery evidence, and release/deployment workflow? Audit the Argus repository's internal and public-facing documentation, includi [Read the thread](https://github.com/Khamel83/argus/issues/69) · 2026-07-25 · closed · 2 comments ### Choose the HTTP and MCP compatibility target for evidence-rich results ## Parent [#58 — Wayfinder: make Argus stable and competitively optimized without a rewrite](https://github.com/Khamel83/argus/issues/58) ## Blocked by - [#59 — Define the Argus stability and competitive evidence scorecard](https://github.com/Khamel83/argus/issues/59) - [#60 — Inventory Argus provider and extraction contract drift](https://github.com/Khamel83/argus/issues/60) ## Question What stable HTTP and MCP compatibility contract should Argus promise while adding richer provenance, evi [Read the thread](https://github.com/Khamel83/argus/issues/66) · 2026-07-25 · closed · 2 comments ### Integrate structured extraction rejection evidence with the retrieval contract ## Parent [#58 — Wayfinder: make Argus stable and competitively optimized without a rewrite](https://github.com/Khamel83/argus/issues/58) ## Blocked by - [#59 — Define the Argus stability and competitive evidence scorecard](https://github.com/Khamel83/argus/issues/59) - [#60 — Inventory Argus provider and extraction contract drift](https://github.com/Khamel83/argus/issues/60) ## Related - [#57 — Persist structured extraction rejection reasons for Atlas callers](https://github.com/Khamel83/a [Read the thread](https://github.com/Khamel83/argus/issues/63) · 2026-07-25 · closed · 2 comments ### Add AGENTS.md: MCP + HTTP usage contract for agents AGENTS.md stub committed. Needs: example MCP call patterns for 'topic research' vs 'URL extraction', example POST /api/search payload per mode, and link validation to khamel83/maya docs/CONTEXT-CONTRACT.md. [Read the thread](https://github.com/Khamel83/argus/issues/18) · 2026-07-04 · closed · 2 comments ### Implement negotiated MCP and CLI client transports Part of #58. ## Wayfinder slice Implement the serial client-transport phase (S9a through S9d) from `docs/superpowers/plans/2026-07-27-retrieval-evidence-mechanical-port.md`. Predecessor [Implement consolidated HTTP accepted-operation authority and secure v2 transport](https://github.com/Khamel83/argus/issues/97) is terminal on `main` at `a4df7d25618674d976a29c3f0865c5f7bca5bf19`. ## Scope - fail-closed HTTP capability negotiation with a bounded origin/deployment-scoped cache and zero specul [Read the thread](https://github.com/Khamel83/argus/issues/99) · 2026-07-29 · closed · 1 comment ## Most recent ### Inventory Argus provider and extraction contract drift ## Parent [#58 — Wayfinder: make Argus stable and competitively optimized without a rewrite](https://github.com/Khamel83/argus/issues/58) ## Question Against the current Argus adapters, schemas, fixtures, and live free-path behavior, plus current official provider documentation, which provider and extraction capabilities, fields, error semantics, freshness controls, and evidence signals are missing or stale? Identify the smallest compatibility shims or normalization rules that preserve existi [Read the thread](https://github.com/Khamel83/argus/issues/60) · 2026-07-25 · closed · 1 comment ### Expose truthful readiness, runtime identity, and bounded operational evidence ## Parent [Wayfinder: make Argus a reliable homelab retrieval platform for Maya](https://github.com/Khamel83/argus/issues/23) ## What to build Give callers and operators truthful answers about whether Argus is live, initialized, ready, or degraded, which exact release is loaded, and which dependencies and capabilities were recently observed—without turning dependency failure into a restart storm or retaining exhaustive logs. ## Acceptance criteria - [ ] Separate liveness, startup, readiness [Read the thread](https://github.com/Khamel83/argus/issues/39) · 2026-07-23 · closed · 0 comments ### Make HTTP the sole Argus execution authority and MCP stateless ## Parent [Wayfinder: make Argus a reliable homelab retrieval platform for Maya](https://github.com/Khamel83/argus/issues/23) ## What to build Collapse production execution into one deep HTTP module. The API process alone owns the broker, providers, browser, budgets, health transitions, persistence, and Maya dispatcher; MCP becomes a stateless protocol adapter over authenticated internal HTTP. ## Acceptance criteria - [ ] Only the API process constructs the production SearchBroker or owns p [Read the thread](https://github.com/Khamel83/argus/issues/37) · 2026-07-23 · closed · 0 comments ### Expose build-research-pack as MCP tool Wrap the existing build-research-pack workflow as an MCP tool so agents in harnesses can trigger pack creation and pipe output to Maya POST /ingest/file via Hermes without a shell escape. [Read the thread](https://github.com/Khamel83/argus/issues/19) · 2026-07-04 · closed · 1 comment The remaining reports are on [the project's issue tracker](https://github.com/Khamel83/argus/issues).