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/gnt/issues.md or /mcp/gnt/issues.json, or Pod over MCP.

Reported issues for gnt

Pod holds 17 of 32 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 gnt.

Most discussed

No test coverage for projectToDeclaredFields (apps/cli/src/prebrain/mcp-framework/fields.ts)

fields.ts exports projectToDeclaredFields, the pure function that enforces every MCP-in adapter's declared-fields privacy boundary (see the file's own doc comment, and docs/contributing/adding-a-connector.md, which calls this "the whole privacy boundary"). No I/O, no mocking needed, yet it has no direct test anywhere, only indirect exercise through the larger framework.test.ts integration suite. Add a focused test covering nested objects, arrays, and keys dropped at every depth, not just the top

Read the thread · 2026-08-22 · open · 1 comment

Add a diagram of the check_action request flow to the docs

enforce.mdx and the README's JSON example describe what check_action returns, but there's no visual of the actual path a call takes (MCP call -> apps/api -> apps/store retrieval -> verdict). A single mermaid diagram embedded in enforce.mdx would answer "where does gnt's server fit relative to my agent and my repo" faster than the prose does, and it's a self-contained doc PR needing no code changes.

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

Add a CrewAI example (examples/src)

examples/src has runnable, tested examples for raw Anthropic tool use, LangChain, the Vercel AI SDK, and the OpenAI Agents SDK, all sharing gnt-mcp.ts and guard.ts. CrewAI is one of the most widely used multi-agent frameworks and isn't represented. Add examples/src/crewai-check-action.ts following the existing pattern, wire an example:crewai script into package.json, and add a test in examples/test/ following guard.test.ts's pattern.

Read the thread · 2026-08-22 · open · 0 comments

Add a Warp integration guide (integrations/warp/)

Warp's Agent Mode supports MCP servers and is a common terminal for people already running gnt-guarded agents, but has no integration guide under integrations/. Add integrations/warp/CONNECT.md and TOOLS.md following the existing structure — integrations/zed/ is a reasonable template.

Read the thread · 2026-08-22 · open · 0 comments

Add a Gemini CLI integration guide (integrations/gemini-cli/)

Google's Gemini CLI is a popular open-source terminal agent with MCP client support and no gnt integration guide yet. Add integrations/gemini-cli/CONNECT.md and TOOLS.md following the structure of the existing guides — integrations/goose/ is the closest analog (another terminal-based, config-file-driven MCP client).

Read the thread · 2026-08-22 · open · 0 comments

Add an Aider integration guide (integrations/aider/)

integrations/ has guides for Cline, Cursor, Zed, goose, and OpenClaw, each with a CONNECT.md and TOOLS.md. Aider is a widely used terminal-based AI coding agent with MCP support and no guide here. Add integrations/aider/CONNECT.md and TOOLS.md following the existing structure — integrations/zed/ or integrations/goose/ are the closest templates for a terminal-first tool.

Read the thread · 2026-08-22 · open · 0 comments

Add a Miro connector (board comments)

gnt connect figma + --figma-comments reads a design tool's comment threads today; Miro is a similarly common home for the same kind of decision-adjacent comment threads with no equivalent. Miro's REST API exposes board comments directly (no first-party MCP server for this), so this should follow the Figma-comments shape: a personal access token stored locally, --miro-boards to scope which boards get scanned, reading only comment message text. Confirm the shape with a maintainer via the connector

Read the thread · 2026-08-22 · open · 0 comments

Add a ClickUp connector (task comments + descriptions)

ClickUp is a common project-management tool in the same space as the already-covered Linear/Jira/Monday.com walkers, with no connector today. Shape 1 fits: a personal API token via gnt connect clickup-mcp, then gnt prebrain --mcp-clickup reading task descriptions and comments within scoped lists/spaces through ClickUp's own MCP server, following mcp-linear.ts/mcp-monday.ts. Confirm the shape with a maintainer via the connector-request issue template first; docs/contributing/adding-a-connector.md

Read the thread · 2026-08-22 · open · 0 comments

Most recent

gnt webhook has no rotate subcommand (unlike gnt keys)

gnt keys supports list, create, revoke, and rotate (rotateKey hits POST /v1/settings/mcp-keys/{id}/rotate). gnt webhook only supports list, create, and revoke — there's no rotate, and apps/api/src/gnt/routers/settings.py has no POST /v1/settings/webhook-tokens/{id}/rotate either, unlike the mirrored mcp-keys/cli-keys rotate routes it does have. Needs a new API endpoint (mirroring rotate_mcp_key) plus a CLI subcommand wired the same way keys rotate is.

Read the thread · 2026-08-22 · open · 0 comments

Add a Continue.dev integration guide (integrations/continue-dev/)

What & why

examples/src has runnable, tested examples for raw Anthropic tool use, LangChain, and the Vercel AI SDK — all sharing gnt-mcp.ts (MCP client helper) and guard.ts (verdict-branching helper). OpenAI's TypeScript Agents SDK (@openai/agents) isn't represented as one of them — the closest thing today is a Python snippet embedded in apps/docs/pages/docs/connect.mdx's docs, which isn't runnable or tested.

Where to look

Read the thread · 2026-08-12 · open · 0 comments

Add an OpenAI Agents SDK example (examples/src)

What & why

Mastra is a popular TS-native agent framework with a createTool pattern that maps directly onto the existing LangChain/Vercel AI SDK examples in examples/src. It isn't represented yet.

Where to look

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

Add a Windsurf integration guide (integrations/windsurf/)

What & why

Continue.dev supports MCP servers via its config.yaml, but there's no integrations/continue-dev/ guide the way OpenClaw and Goose get one. Same gap, different client.

Where to look

Done looks like

A new `integrations/continu

Read the thread · 2026-08-12 · open · 0 comments

Add a Cline integration guide (integrations/cline/)

What & why

Windsurf (Codeium's editor) supports MCP via its own mcp_config.json, but there's no integrations/windsurf/ guide the way OpenClaw and Goose get one. Same gap, different client.

Where to look

Done looks like

A new `integrati

Read the thread · 2026-08-12 · open · 0 comments

Add a Cursor integration guide (integrations/cursor/)

What & why

Cline (the VS Code extension, formerly Claude Dev) has first-class MCP support with its own cline_mcp_settings.json, but there's no integrations/cline/ guide the way OpenClaw and Goose get one. Same gap, different client.

Where to look

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

Add a root .editorconfig

What & why

apps/docs/pages/docs/mcp-clients.mdx explicitly calls Cursor out as under-served today: "Point Cursor, or anything else that speaks MCP, at the same endpoint" — there's no dedicated setup guide the way OpenClaw and Goose get one under integrations/. Cursor has first-class MCP support via a .cursor/mcp.json config file, which fits the exact pattern this repo already documents twice.

Where to look

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

CONTRIBUTING.md's turbo command comment is stale

What & why

apps/docs/pages/docs/sources.mdx documents, per connector, exactly what gnt reads and never reads (Linear/Jira/Sentry get inline paragraphs; Figma/Datadog/GitLab/HubSpot/Airtable/Zendesk/Intercom/Monday.com get <details> blocks). Notion is only ever named in the flag list — it never gets its own "what it reads / never reads" writeup, even though docs/contributing/adding-a-connector.md uses Notion as its own worked example for how to document a connector, and even though `app

Read the thread · 2026-08-12 · open · 0 comments

Issue templates reference a non-existent apps/web area

What & why

apps/api/README.md's "Scope" section says the MCP server exposes four tools: search_rules, get_rule, list_skill_packs, get_skill_pack. That's missing check_action — there are actually five, and check_action is arguably the most important one (it's the whole "before you act, check the rule" verb the product is built around). The root README.md's own tool table already lists all five correctly, so apps/api/README.md has drifted out of sync.

You can verify the real

Read the thread · 2026-08-12 · open · 0 comments

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