Repository navigation
Releases
1.18.0
A feature release adding Mistral Vibe and OpenAI Codex agent support, a
Magewire 3 skill suite contributed by the Magewire author, a Hyvä Checkout
architecture skill, and nested sub-skill resources — plus reinitialize fixes
that make modules created mid-session visible and stop stale-registry cache
poisoning. No breaking changes.
New
- Mistral Vibe agent support — install --agents=mistral-vibe writes the MCP
server config to .vibe/config.toml (idempotent; user-managed settings are
kept) and compiles AGENTS.md guidelines. - OpenAI Codex agent support — install --agents=codex writes the MCP server
config to .codex/config.toml (idempotent) and compiles AGENTS.md
guidelines. Gemini, Codex and Mistral Vibe share AGENTS.md; its footer
lists every agent it serves.
Fixes
- Modules created mid-session are now visible after reinitialize —
registration globs re-run on every (re)init and Composer's
autoload_files.php is re-scanned, so a fresh ObjectManager no longer
reuses a stale ComponentRegistrar registry or writes merged-config caches
without the new module. - reinitialize aborts before touching shared caches when the registry is
irrecoverably stale (enabled-but-unregistered module, or an enabled
module's directory deleted), refusing with an actionable restart error
instead of silently poisoning caches. - reinitialize response is honest about registry state — reports
registered_components and newly_registered_files, surfaces a failed
module-count read as modules_loaded_error, and warns about
enabled-but-unregistered modules and components removed from disk. - MagentoBootstrap::reset() clears the sentinel-mtime snapshot and reinit
stats, not just the ObjectManager and root path.
Skills
- Magewire 3 development suite (magewire-three) — greenfield components,
V1→V3 migration, Livewire V3-style directives and events, resolvers,
snapshots, synthesizers, Alpine CSP integration; nested sub-skills for
architecture internals, the backwards-compatibility layer, best
practices, CSP-compatible JavaScript, theming, and the Portman
framework-maintainer workflow. Contributed by Magewire author Willem
Poortman. - Hyvä Checkout architecture and development — Evaluation results, primary
navigation, Place Order Services, frontend payment methods and backports,
and a mandatory compatibility profile: Magewire V1 for checkout 1.0-1.3.*,
native Magewire 3 for new components on 1.4+, or the migration track for
existing V1 components.
Improvements
- Nested sub-skill resources served via the magento://skills/{name}/{topic}
resource template. - YAML frontmatter stripped from skill resources before serving; path
segments containing .. are rejected.
Contributors
1.17.0
A feature release adding an order-creation tool, plus code-runner correctness
fixes, a canonical .phtml template convention, and community/contribution docs.
No breaking changes.
New tools (hidden, discover via search-tools)
- order-create — build and place an order: line items by SKU, one
billing/shipping address, chosen shipping and payment method. Supports all
default product types (configurable, grouped, bundle, downloadable),
product custom options, existing-customer orders via customerId (0 = guest),
and virtual/downloadable-only orders. Disabled by default and blocked in
production; enable via tools.order-create.enabled=true in .bricklayer.json.
Fixes
- code-runner: a timeout no longer kills the MCP server — enforced by a
catchable wall-clock SIGALRM (where pcntl is available); on timeout the
transaction rolls back and a normal error (timed_out: true) is returned,
session state survives. - code-runner: fatals now report instead of silently dropping the connection —
a shutdown hook answers the in-flight request with a JSON-RPC error naming
the fatal. - code-runner: define-mode helpers no longer fatal on the second use
(Cannot redeclare); functions declared once behind a function_exists guard,
redefining returns a warning. - code-runner: timeout=0 no longer disables the execution limit — effective
timeout floored at 1s. - database-query: SELECT(...) is no longer rejected — SELECT guard uses a word
boundary instead of requiring whitespace. - code-runner: state reset now clears repository identity maps (product,
category, CustomerRegistry), so external changes are no longer hidden by
stale cached entities. - code-runner: clearer message when writes are blocked by config
(write_blocked_by_config: true, names the config key to enable).
Guidelines & generated code
- Standard .phtml template convention (Luma and Hyvä): required header order
(declare → use → var) and clear escaping rules; generate-controller output
and all guideline examples now follow it.
Docs
- Added CONTRIBUTING.md, CODE_OF_CONDUCT.md, and SECURITY.md.
Contributors
- Tihomir Vranjes (@tvranjes)
- Andreas von Studnitz (@avstudnitz) — order-create tool (#2)
- Josip Oužecky (@ouzecky) — .phtml template structure and escaping fix (#6)
1.16.0
A feature release adding runtime introspection for the view layer and message-queue wiring — three read-only tools that surface resolved/merged state no single source file shows. No breaking changes.
New tools (hidden, discover via search-tools)
layout-inspect— resolve a layout handle into its runtime-merged block/container tree (merged across every module and the active theme), showing appliedreferenceBlock/referenceContainer/move/removedirectives, declared and theme-resolved.phtmltemplate paths, and the page layout. Omit the handle to list every registered handle for an area (frontend/adminhtml). Config-gated, enabled by default.ui-component-inspect— resolve an admin grid/form UI component's runtime-merged configuration, showing the component tree, data source, and child components merged across modules. Config-gated, enabled by default.message-queue-inspect— the runtime-merged consumer → topic → queue → exchange topology with publisher and handler bindings, assembled acrosscommunication.xml,queue_consumer.xml,queue_topology.xml, andqueue_publisher.xml. Each section degrades independently when a sub-config is absent. Ungated.
Removed
- The static
layouts_referenceMCP resource (a hand-maintained handle catalogue) is retired in favour oflayout-inspect's runtime list mode — the registered handles are now read from the live install and cannot drift.
Internal (no behavior change)
AreaEmulator::emulateAreaCode()added — a restoring area-code swap (viaState::emulateAreaCode) so view tools can resolve frontend layout while the MCP server process is locked to the adminhtml area.
Contributors
1.15.1
1.15.0
A code-audit release: fixes a batch of correctness and security bugs, makes code-runner use PsySH as intended, and consolidates duplicated internal logic. No breaking changes.
Security & safety
Environment-variable tool overrides now work for every tool. BRICKLAYER_TOOLS_* settings were silently ignored for hyphenated tools (e.g. code-runner, product-delete), so disabling a tool via an env var had no effect. Use the full-path form, e.g. BRICKLAYER_TOOLS_CODE_RUNNER_ENABLED=false.
code-runner is now reliably blocked in production even when the deploy mode can't be read (fails closed instead of open).
Fixes
code-runner actually runs through PsySH when it's installed — it previously fell back to a basic eval engine on every call while wrongly reporting "PsySH not available". Responses now report the active runtime.
diagnose-error counts error history from the log the error was actually found in, instead of always exception.log.
GraphQL introspection labels input types correctly and returns type descriptions (both were broken).
database-schema now respects its own enable/disable setting (it was tied to database-query).
The mcp command honors --magento-root on systems without pcntl.
Many smaller fixes: safer log-file handling, accurate text truncation, recursive module validation, correct config-write success reporting, dynamic (non-hardcoded) tool/category counts, data-URI image type detection, and more.
Internal (no behavior change)
Consolidated duplicated logic — error responses, pagination, sensitive-value masking, time parsing, command setup, and log/markdown scanning — into shared traits and helpers.
Removed dead code and wired up the previously-orphaned PhpStorm config writer, so install now generates .idea/mcp.json.
Contributors
1.14.2
- New guideline: Pool pattern (
patterns/pool.md) — DI-based strategy resolution with extensible array injection, replacing if/else branching on type identifiers. Covers implementation, third-party extensibility, and chain of responsibility with sortOrder. - New guideline: Value Object / DTO (
patterns/value-object.md) — Immutable data carriers withpublic readonlyproperties,fromJson()/toJson()serialization for JSON columns, and comparison with Data Interfaces. - New guideline: Context Object (
patterns/context-object.md) — Bundling repeated request-scoped parameters (customerId, storeId, currencyCode) into a single immutable object with a Builder. - Updated: Plugin pattern (
patterns/plugin.md) — Added "Plugin Chain on Repositories" section showing how to chain multiplebeforeSaveplugins with sortOrder for cross-cutting concerns (validation, timestamps, encryption). - Updated: Coding Standards (
core/coding-standards-quality.md) — Added "Constants as Final Classes" section for grouping enum-like constants infinal classinstead of interfaces.
Contributors
1.14.1
1.14.0
Project-local overrides — A new .bricklayer/ directory at the Magento root lets projects add or replace bundled content without forking the package. The path is the contract; no registration in .bricklayer.json required.
.bricklayer/project-context.md — free-form markdown appended to every generated agent file under a ## Project-Specific Context heading
.bricklayer/decision-matrix.md — extra rows merged into the "Before Modifying Magento Code" table; malformed lines skipped
.bricklayer/guidelines/{path}.md — files matching a bundled path override it; files with no bundled counterpart are compiled as new sections with headings derived from the directory and filename
.bricklayer/skills/{category}/SKILL.md — overrides by category, or new local-only categories directly callable via development-context category={directory-name} and listed under a Project-specific row in the CLAUDE.md categories table
Optional YAML frontmatter (name: and description:) for SKILL.md files — stripped before content is returned to agents, used as display metadata in search-docs and the categories table
Local entries tagged [Project] in search-docs results; override entries replace bundled ones in the merged index, no duplicates
bricklayer update reports local changes — after regenerating agent files, the command lists every applied local override/addition and the number of local docs-index entries
bricklayer init creates .bricklayer/ — the project override directory is created automatically so developers know where to drop local content; subdirectories are created on first use, no placeholder files generated
New Inchoo\MagentoBricklayer\Guidelines\LocalOverrideHelper — shared static helpers for parsing SKILL.md YAML frontmatter and stripping it from content. Used by GuidelinesCompiler, ContextTools, and SearchTools (no duplicated parser code)
GuidelinesCompiler, ContextTools, and SearchTools constructors now accept optional $magentoRoot and $packageRoot arguments for testability (defaults preserve previous behavior)
Added vendor/bricklayer config:set interactive command to easily set and change config values in .bricklayer.json
Added Bricklayer SKILL.md file for agents to understand how Bricklayer works
Contributors