Reported issues for Maket

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

Most discussed

Quick wins for paginated authoring: charte size validation, check headroom, state density, cross-page move

Context

Field report from an agent composing a 9.7k-character A4 essay in maket (3 iterations). The agent got to a clean result but burned ~8 round-trips per chapter page on the fill-then-check-then-trim loop. Four small gaps in the current API account for most of that cost. All four are additive (no contract change) and align with the existing architecture.

1. Extend charte validation to sizes / leadings / spacings

Today charte-check.ts rejects literal colors that duplicate a tok

Read the thread · 2026-04-27 · closed · 1 comment

feat(mcp): support session-scoped agent message subscriptions

Summary

Allow an active agent session to subscribe to messages from Maket without broadcasting them to every client connected to the shared server.

This evolution is deferred until MCP subscriptions and agent-host support are sufficiently stable.

Proposed direction

• Represent each subscription as an inbox resource scoped to a workspace or document and an expiring agent-session lease.
• Let compatible clients open subscriptions/listen for that inbox URI.
• Notify the subscribed clien

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

feat(desktop): make Electron the Maket 2.0 distribution

Summary

Make the Electron desktop application the primary Maket 2.0 product for macOS, Windows, and Linux.

Maket 2.0 is desktop-first: users install a signed desktop application that bundles and owns the current Maket server, web client, MCP compatibility bridge, Node runtime, and required rendering capabilities. No external Node.js installation or manual server command is required for the nominal experience.

The existing npm distribution is migrated and renamed to Maket Server, the ex

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

refactor(mcp): migrate the HTTP endpoint to SDK v2

Migrate Maket to the stable MCP TypeScript SDK v2 and delete the hand-written transport code.

Acceptance criteria:

• serve POST /mcp with the v2 Node HTTP handler;
• serve stdio with the v2 stdio server and forward through the v2 HTTP client;
• remove the manual HTTP lifecycle, NDJSON/SSE proxy, v1 SDK, re-exports, and compatibility shims;
• cover legacy and 2026 protocol clients at the public HTTP and stdio boundaries;
• run npm run quality.

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

chore: add LobeHub marketplace manifest

Add the repository-owned lhm.plugin.json required to publish Maket on the LobeHub MCP marketplace.

Scope:

• Maket 1.6.0
• 14 live MCP tools
• no Glama, Smithery, MCPB, or runtime code changes

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

Automate MCP Registry publication

Context

Maket is already active in the official MCP Registry, but the registry currently exposes version 1.4.4 while npm and the repository are at 1.6.0.

The release workflow already uses GitHub OIDC for npm trusted publishing (id-token: write) but does not invoke mcp-publisher.

Scope

• Publish server.json to the official MCP Registry from .github/workflows/publish.yml using GitHub OIDC.
• Keep registry publication aligned with the version already validated and published to

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

fix(export): unify .maket bundle export across HTTP and MCP

Constats vérifiés

Le format .maket v2 sait déjà transporter l'état courant d'un living document :

• le manifeste accepte documentStates;
• l'export HTTP capture le schéma et les données courants;
• l'import les restaure;
• le viewer autonome sait les rendre;
• les anciens bundles restent lisibles.

Le défaut restant est une divergence entre deux surfaces d'export :

• la route HTTP exporte bien les documents state-backed;
• maket_doc action=export refuse encore explicitement ces docum

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

docs: surface data-driven collections in README

Problem

The README barely mentions collections: they are absent from the opening pitch, Features, examples, and tool table. It also says Maket exposes 12 tools while the manifest exposes 13 because maket_collection is missing.

Expected

• Present typed, data-driven collections near the top of the README.
• Explain JSON Schema fields, rows, placeholders, page binding, validation, selected-row preview, and rendering all variants.
• Add a concrete collection workflow example.
• Add maket_co

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

Most recent

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