How vikashftw/canary works
Bloodhound is an autonomous QA and bug-remediation system: a browser explorer checks expected versus observed behavior while Sentry captures thrown errors and traces; both feed findings into deduplicating triage, which diagnoses, proposes a fix, and produces a regression test. The dashboard presents runs, traces, fixes, and memory, alongside an instrumented checkout demo and autonomy controls. The README documents the end-to-end handoffs; source excerpts confirm the triage sequence, trace access, memory capabilities, and checkout behavior. Some web and explorer integrations are unsampled, so their internal connections are not expanded.
Main entry points: engine.ts Triage engine · RunController.tsx Run dashboard · finding.ts Finding contract · index.ts Memory services
Components 26
Detection
- Browser explorer
explorer - Headless browser
- Sentry capture
web/instrumentation-client.ts - Finding contract
src/contracts/finding.ts
Triage & Remediation
- Triage engine
src/triage/engine.ts - Trace access
src/sentry/trace-client.ts - Trace data
src/sentry/trace.ts - Root-cause judge
src/triage/judge.ts - LLM client
src/triage/llm.ts - Fix strategies
src/triage/fixer.ts - Regression author
src/triage/regression.ts - Fix verifier
src/triage/verifier.ts - Resolution contract
src/contracts/resolution.ts - Canonical fix cache
src/cache/canonical.ts
Memory
- Memory services
src/memory/index.ts - Finding history
src/memory/finding-store.ts - Semantic recall
src/memory/similar-findings.ts
Dashboard & Demo
- Run dashboard
web/src/app/_components/RunController.tsx - Run API
web/src/app/api/run/route.ts - Autonomy controls
web/src/lib/autonomy-runner.ts - Checkout demo
web/src/app/checkout/page.tsx - Cart and findings
web/src/app/api/checkout/_cart.ts
External Services
- Redis
- Sentry
- Anthropic
Other components
- QA operator
Connections 31
- QA operator → Run dashboard: starts run
web/src/app/_components/RunController.tsx - Run dashboard → Run API: requests run
web/src/app/_components/RunController.tsx - QA operator → Browser explorer: initiates exploration
README.md - Browser explorer → Headless browser: drives actions
README.md - Browser explorer → Finding contract: emits findings
README.md - Sentry capture → Sentry: captures errors
README.md - Sentry → Finding contract: raises findings
README.md - Finding contract → Triage engine: enters triage
README.md - Triage engine → Trace access: fetches trace
src/triage/engine.ts - Trace access → Sentry: requests trace
src/sentry/trace-client.ts - Trace access → Trace data: maps response
src/sentry/trace-client.ts - Triage engine → Root-cause judge: judges finding
src/triage/engine.ts - Root-cause judge → LLM client: requests completion
- Triage engine → Fix strategies: selects fix
src/triage/engine.ts - Fix strategies → LLM client: requests fix
- Triage engine → Canonical fix cache: uses fallback
src/triage/engine.ts - Triage engine → Regression author: creates test
src/triage/engine.ts - Triage engine → Fix verifier: verifies resolution
src/triage/engine.ts - Triage engine → Resolution contract: produces resolution
README.md - Triage engine → Memory services: shares dedup contract
src/memory/index.ts - Memory services → Finding history: exposes history
src/memory/index.ts - Memory services → Semantic recall: exposes recall
src/memory/index.ts - Finding history → Sentry: stores canonical history
- Semantic recall → Redis: searches vectors
- Memory services → Redis: connects optionally
src/memory/index.ts - LLM client → Anthropic: sends completion
src/triage/llm.ts - Run dashboard → Resolution contract: displays outcome
README.md - Run dashboard → Finding contract: shows finding
README.md - Run dashboard → Autonomy controls: offers controls
README.md - Checkout demo → Cart and findings: uses checkout
README.md - Cart and findings → Finding contract: records finding
web/src/app/api/checkout/_cart.ts