Pod

Yes, this is on purpose. Pod is built for agents, so the default page is plain HTML.
Human? View the normal website.
Agent? You probably prefer /mcp/krabiclaw/issues.md or /mcp/krabiclaw/issues.json, or Pod over MCP.

Reported issues for KrabiClaw

Pod holds 6 of 6 GitHub reports that passed its relevance review. This can include external user reports, maintainer-confirmed bugs, and concrete feature gaps. Treat them as evidence to inspect, not a count of distinct defects.

Back to KrabiClaw.

Most discussed

Fix ChatGPT MCP sessions terminating when launching video upload widget

Summary

ChatGPT MCP sessions terminate repeatedly when invoking the open_video_upload flow, including after disconnecting/reconnecting the connector and starting new chats.

Affected experience:

Likely causes

1. Invalid MCP protocol versions and incorrect negotiation

server/utils/mcp-protocol.ts currently advertises and accepts:…

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

get_dashboard_link (MCP/ChowBot) returns 404 URLs for every settings.* destination

Problem

buildDashboardUrl in server/utils/dashboard-links.ts stripped the leading ~ segment when building dashboard deep-links:

const path = DASHBOARD_DESTINATIONS[destination].replace(/^~\/?/, '').replace(/^\/+/, '')

DASHBOARD_DESTINATIONS entries are declared with a literal ~/ prefix ('settings.domains': '~/settings/domains', etc.) because the real page files live at pages/dashboard/[orgSlug]/~/settings/*.vue~ is a literal route segment in this app's…

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

Harden MCP tool evolution after production stale-catalog failures

Summary

A real production ChatGPT MCP conversation repeatedly called the removed platform tool update_platform_blog_post after the live server had split it into update_platform_blog_metadata and replace_platform_blog_content.

The incident exposed four independent problems that must all be fixed:

  1. Breaking tool removal: a previously published MCP tool name was removed from dispatch without a compatibility adapter.
  2. Incorrect JSON-RPC classification: an unknown…

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

ChowBot/MCP returns wrong dashboard link for domain settings; domains route mishandles org ID vs slug

Summary

Split out of #359 — unrelated root cause, bundling it there would have buried a real bug behind a much larger Cloudflare integration redesign.

There is no Domains link in the dashboard's left-nav for site settings, so a user asked ChowBot for the URL. ChowBot/MCP returned /dashboard/org-ncls-blawby/settings/domainsorg-ncls-blawby is the organization's ID, not its slug (north-carolina-legal-services). Visiting that URL rendered the domains page as if the org had…

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

Build unified lead lifecycle management: ingestion, qualification, nurturing, and conversion for first-party and third-party leads

Problem

KrabiClaw can capture contact submissions, reservations, and bookings, persist tenant-scoped customers, notify operators, and emit site events. It does not yet provide one canonical path that accepts a lead from any source, resolves it to a customer profile, records consent and attribution, and enrolls it in a reliable nurturing workflow.

The product requirement is:

A tenant can receive a lead through a KrabiClaw form or an authenticated third-party API integration, and…

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

CI preview e2e failures: rename rollback + reply_to_review role gate

Summary

Three groups of test failures in the PR #71 preview E2E run that are unrelated to the MCP/ChowBot decommission work in that PR. Deferring to a separate fix.


Failure 1 — Pottery House public routes (title mismatch, platform page served)

Root cause: The update_site_settings rollback test in chowbot-tools.spec.ts and site-settings.spec.ts is supposed to rename the pottery-house site to a temporary subdomain, then fail at the Cloudflare provisioning step and roll…

Read the thread · 2026-06-15 · closed · 0 comments

Most recent

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