Reported issues for hunch
Pod holds 6 of 6 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 hunch.
Most discussed
Windows: hunch mcp does not exit with the team.json remote-mismatch refusal within 10s (test times out)
Severity: medium — hunch mcp does not exit with the expected refusal within 10s on a mismatched team.json fixture (Windows)
Location: test/team-workflow-failure-regressions.test.ts:505-535
Observed behavior
✖ MCP refuses an existing shared overlay whose remote differs from committed team.json (95084.6ms)
Error: spawnSync C:\Program Files\nodejs\node.exe ETIMEDOUT
[Read the thread](https://github.com/davesheffer/hunch/issues/56) · 2026-08-04 · closed · 2 comments
### mismatch: hunch_context parameter named 'target' but documented as 'target_or_task' in claudemd generator
In `@davesheffer/hunch` (tested on version `1.19.0` and earlier), there is a mismatch between the schema parameter name and the generated instructions for `hunch_context`.
Specifically, in `package/dist/mcp/server.js`, the `hunch_context` tool is registered with the following `inputSchema`:
```typescript
inputSchema: {
target: z.string().describe("A file path, symbol, or task phrase you're about to work on."),
budget_tokens: z.number().optional().describe("Rough
[Read the thread](https://github.com/davesheffer/hunch/issues/95) · 2026-08-28 · closed · external user · 1 comment
### MCP roots: Windows drive-letter case difference treated as a different root
**Severity:** low/medium — Windows drive-letter case difference treated as a different root
**Location:** [`src/mcp/server.ts:311-313`](https://github.com/davesheffer/hunch/blob/5f14e1a/src/mcp/server.ts#L311-L313), [`src/mcp/roots.ts:44-45`](https://github.com/davesheffer/hunch/blob/5f14e1a/src/mcp/roots.ts#L44-L45)
### Defect
Root comparison is raw string equality on `findRoot` output, and `findRoot` (`core/paths.ts`) does `resolve()` only — no realpath/case normalization — while `git.ts:174
[Read the thread](https://github.com/davesheffer/hunch/issues/54) · 2026-08-04 · closed · 1 comment
### MCP: index refresh is gated to shared mode; public-mode server serves a stale SQLite index
**Severity:** medium/high — public-mode MCP server serves a permanently stale SQLite index (split-brain answers)
**Location:** [`src/mcp/server.ts:425-437`](https://github.com/davesheffer/hunch/blob/5f14e1a/src/mcp/server.ts#L425-L437)
### Defect
The request-boundary source-stamp check and `refreshIndex()` run only inside the shared-mode branch:
```ts
if (store.mode === "shared" && store.privateDir) {
...
if (store.sourceStamp() !== indexedSourceStamp) refreshIndex();
}
`refreshIndex
Read the thread · 2026-08-04 · closed · 1 comment
Provider/config writers rewrite merged user files non-atomically
Severity: low/medium — merged user config files are rewritten non-atomically
Location: src/integrations/providers.ts:110-114 (writeJson, used for .cursor/mcp.json, .vscode/mcp.json, .windsurf/mcp_config.json, global configs, all hook configs), src/integrations/scaffold.ts:35 (.mcp.json), [`src/int
Read the thread · 2026-08-04 · closed · 1 comment
Single-file index put/delete race across processes silently loses records
Severity: medium — lost update between the MCP server and the CLI
Location: src/store/jsonStore.ts:448-451 (put), src/store/jsonStore.ts:521-525 (delete)
Defect
For single-file kinds, put/delete are read-modify-write on index.json with no cross-process locking:
const arr = this.readRawArray(k
[Read the thread](https://github.com/davesheffer/hunch/issues/35) · 2026-08-04 · closed · 1 comment
## Most recent
The remaining reports are on [the project's issue tracker](https://github.com/davesheffer/hunch/issues).