Other formats agents might prefer:
markdownjsonllms.txt

Agent? You probably want markdown or json, or Pod over MCP.

Reported issues for Quickshell MCP

Pod holds 9 of 9 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 Quickshell MCP.

Most discussed

[Feature] Add end-4/dots-hyprland as a third real-world implementation source`

What

Index end-4's dots-hyprland repo alongside Caelestia and Noctalia so quickshell_search_implementations, quickshell_find_pattern, and quickshell_search_all can surface its Quickshell shell (Illogical-Impulse) as reference implementations.

Why

The shell at dots/.config/quickshell/ii/ is one of the largest, most feature-complete real-world Quickshell configs (~586 QML files: bars, control center, lock screen, launchers, services). Agents frequently reach for it as an exampl

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

[Feature] quickshell_coding_assistant

What

Add quickshell_coding_assistant, a high-level tool that takes one plain-language development request and routes it through the existing tools (search, pattern lookup, error diagnosis, compatibility, validation, component generation, migration). It returns a structured, source-grounded result with a terminal grounded_result.

Why

Multi-step Quickshell tasks (build a workspace bar, debug a failing PanelWindow, migrate a shell between versions, adapt an existing pattern) currently fo

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

[Feature] Add quickshell_generate_component tool

What

A tool that generates a minimal Quickshell QML component from a plain-language description and verifies every referenced API against the docs for the requested version.

Why

Agents write QML that references types and properties missing from the target release because they guess from training data. The current workflow (search, find pattern, check compat, validate) gives the right answer but takes several calls. One tool that researches, assembles, and verifies in a single call mea

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

[Feature] Add quickshell_migrate tool to analyze upgrades between versions

What

Add a quickshell_migrate tool that tells you what a QML config must change to keep working when you move from one Quickshell version to another.

Why

When an agent maintains or upgrades a Quickshell config, it has no easy way to see which APIs broke or moved between releases. Today it either guesses from training data or reads the changelog by hand. A tool that scans the config and the changelog range would give a concrete list of renames, removals, and deprecations, with location

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

[Feature] Add quickshell_check_compatibility to check API/version support

What

Add a quickshell_check_compatibility tool that tells an agent whether a Quickshell API, QML property/method/signal, type, or code snippet is compatible with a specific Quickshell version.

Why

Agents frequently need to pin configs to a version (e.g. "is PanelWindow.exclusiveZone available in v0.2.0?") but today they can only guess from partial docs or re-derive availability by hand. Without a version-aware check, they suggest APIs that were introduced, removed, renamed, or depreca

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

[Feature] Static QML validation tool

What

Add a new MCP tool quickshell_validate_qml that statically validates Quickshell/QML source (unknown types, properties, signals, missing imports, type mismatches, version-incompatible APIs) against the live docs index.

Why

The existing tools (quickshell_get_type, quickshell_search, etc.) are all fetch-and-return, none analyze the users own QML source. Validation was the missing piece.

Area

New tool

How it could work

No response

Alternatives considered

_No res

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

[Feature] Add a tool for explaining QML errors

What

A quickshell_explain_error tool that parses QML runtime errors and returns a structured diagnosis grounded in the actual Quickshell and Qt type indexes.

Why

When an agent writes a QML config, runtime errors like "Cannot assign to non-existent property" are opaque without knowing the type's API surface. Today the agent has to guess at fixes or ask the user to paste docs. A tool that looks up the property/method/signal against the type index and suggests corrections would catch mos

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

[Feature] quickshell_find_pattern: find implementations by what you want to build

What

A quickshell_find_pattern MCP tool that takes a plain description of what you want to build ("launcher like Spotlight", "volume OSD") and returns real implementations of it from Caelestia, Noctalia, and the official examples, with the Quickshell/Qt APIs each pattern typically uses.

Why

Today's tools match keywords against file paths and topic phrases. That only works if the agent already guesses the right word: "workspace" hits, "Spotlight" finds nothing, and "power menu" turns

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

Most recent

quickshell_search_all: search every source in one call

Today an agent has to know which tool reaches which source: quickshell_search for docs and types, quickshell_search_implementations for Caelestia/Noctalia, browse tools for Qt types and official examples. A single request like "how do I make a volume OSD" spans several of them, and the agent has to guess where to look first.

What: one tool that takes a natural-language query and searches everything we already index in a single call: Quickshell docs and types, Qt/QML types, official exam

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

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