Reported issues for Voila Groceries MCP

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 Voila Groceries MCP.

Most discussed

Migrate Voila SDK, MCP, and CLI to Effect 4 with contract parity

What to build

Migrate the complete Voila workspace from Effect 3 to the exact Effect 4 release-candidate cohort while preserving externally observable SDK, MCP, CLI, session, and package behavior.

Treat this as one wide migration on a dedicated integration branch. A controlled-red interval is allowed after the dependency cutover, but every internal checkpoint must have focused verification and the ticket is complete only when the unchanged project quality gates are green. Do not split routi

Read the thread · 2026-08-18 · closed · 3 comments

Make the Voila transport and MCP server Effect-native

What to build

Effect where Effect makes sense: the SDK's transport and operations expose Effect rather than promises of eithers, the MCP server is Effect-native too, and the promise boundary survives only where something outside the codebase is promise-shaped.

The store, the session file cycle, and the session port are already Effect. The SDK underneath them is not, and neither is the MCP edge above them, so every operation run crosses from Effect into a promise and back twice. Two reasons

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

MCP and CLI source are excluded from the coverage gate

Context

vitest.config.ts excludes packages/voila-mcp/src/** and packages/voila-cli/src/** from coverage. The 99% thresholds therefore say nothing about the MCP session port, the operation registry, or the CLI command layer.

This is not theoretical: the session port shipped in #7 initially dropped a refreshed guest session in memory, and the coverage gate could not have caught it — makeSessionPort and its guest/file branches sit outside the measured set.

What to build

Bring both

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

Route all session persistence through the session file store

Parent

Follows #6, which builds the session file store wrapper. This ticket makes it the only path to a session file.

What to build

A re-login survives a long-running process.

Concretely: a user starts the MCP server, logs in again from another terminal hours later, and the server neither reverts that login nor keeps using the session it read at boot. Today it does both — the server caches the snapshot it loaded at startup and writes that cached value back after operations, and the log

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

Session file lock serializes tool calls around an untimed request

Context

Since #7, an operation runs inside the session file store's read-modify-write cycle (packages/voila-mcp/src/node-env.ts → updateSessionFileCarrying → locks.withPermit). Keeping the request inside the guarded window is deliberate: a response's Set-Cookie is folded into the snapshot that is written, and requesting before the cycle reopens the read-decide gap the store exists to close (ADR-0003).

The cost is that every tool call sharing one session path is serialized in-process

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

Harden configurable user-agent and WAF diagnostics

Parent

Follow-up to #1.

What to build

Make Voila HTTP identity and WAF-block detection configurable, predictable, testable, and safely diagnosable while preserving the current first-entry desktop user-agent as the default.

The effective user-agent precedence should be:

1. An explicit per-request User-Agent.
2. A configured user-agent.
3. The first entry in the desktop user-agent dataset.

Acceptance criteria

• Configuration accepts an optional, non-empty user-agent value thr

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

Most recent

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