pod
Other formats agents might prefer:
markdownjsonllms.txt

Agent? You probably want markdown or json, or Pod over MCP.

Reported issues for HitKeep

Pod holds 7 of 7 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 HitKeep.

Most discussed

Customer surfaces for AI Opportunities status and export

Parent

#154

What to build

Complete the customer-visible surfaces around the AI Opportunities feature: non-secret admin status, runtime OpenAPI, takeout/export inclusion, safe MCP final-data exposure decision, docs, and release-note handoff.

Acceptance criteria

  • Start with failing API/admin tests proving AI status reports enabled/configured/mode/provider/model labels/budget state/safe last-error category without secrets.
  • Runtime OpenAPI documents AI status and Opportunities

Read the thread · 2026-05-08 · closed · 1 comment

Add opt-in Core Web Vitals analytics for 2.5.0

Summary

Add opt-in Core Web Vitals analytics for HitKeep 2.5.0 with a dedicated Web Vitals report, page-level breakdowns, timeseries, takeout, MCP reporting, and tracker loading that stays off unless explicitly enabled.

Problem

Site owners need to understand how real visitors experience page performance without adding Google Analytics, Search Console-only workflows, or a separate RUM product. HitKeep already owns the tracker, ingest path, tenant analytics storage, dashboard, exports, and

Read the thread · 2026-05-07 · closed · 1 comment

[Feature]: Build a polished Google Search Performance workspace

Summary

Turn HitKeep's existing Google Search Console settings page and dashboard drilldown into one polished, site-scoped Search Performance workspace for SEO, content, and growth work.

The workspace should combine accurate imported Google Search metrics, previous-period comparisons, Search Appearance reporting, and page-level HitKeep outcomes, while making connection setup, property mapping, sync health, and recovery much clearer.

Problem

The current Search Console surface is useful

Read the thread · 2026-07-16 · open · 0 comments

[Feature]: Define rich, typed webhook payloads for all existing events

Summary

Replace the current inconsistent webhook data maps with documented, event-specific payloads for all 17 existing webhook events. In particular, make goal.converted actionable by including the triggering custom-event properties or a privacy-bounded pageview snapshot.

This is a versioned contract cleanup: the envelope remains stable, while deliveries created under the release containing this change use the new nested data shape without legacy flat aliases.

Problem

Webhook pa

Read the thread · 2026-07-16 · open · 0 comments

Permissioned aggregate tool bridge for Opportunities

Parent

#154

What to build

Add the in-process MCP-style read-only tool bridge used by the Opportunities engine. The bridge should expose focused aggregate tools only, scoped to the triggering actor/team/site/date range, without self-calling HitKeep's public MCP endpoint.

Acceptance criteria

  • Start with failing permission tests for a viewer, an unauthorized actor, and an ai_scheduler actor scoped to one team/site.
  • Tools expose only aggregate site overview, ecommerce summary

Read the thread · 2026-05-08 · closed · 0 comments

Pluggable AI provider gateway for Opportunities

Summary

Add a provider-agnostic AI foundation for HitKeep Opportunities so cloud and self-hosted operators can plug in a supported provider/model while HitKeep keeps deterministic evidence, reusable recommendation contracts, audit controls, budget limits, and translation-friendly customer surfaces.

Product promise

Opportunities should help users decide what to review next. The feature must not promise financial upside, revenue uplift, causal attribution, or generic AI-written advice. The

Read the thread · 2026-05-08 · closed · 0 comments

Fix MCP initialization behind reverse proxies after SDK localhost guard change

Summary

HitKeep MCP initialization can fail behind reverse proxies after the MCP Go SDK localhost-protection behavior change.

Environment

  • Product/Service: HitKeep MCP server
  • Version: 2.4.0
  • Deployment shape: HitKeep bound to loopback and exposed through a reverse proxy

Reproduction Steps

  1. Run HitKeep with MCP enabled and HITKEEP_HTTP_ADDR=127.0.0.1:8080.
  2. Expose HitKeep through a reverse proxy with a public hostname.
  3. Configure an MCP client against the public

Read the thread · 2026-05-07 · closed · 0 comments

Most recent

The remaining reports are on the project's issue tracker.