Skip to content
Neutrome
Magento 2 coding companion

MerchantDuo

Domain knowledge served as a model, not as a framework

Visit merchantduo.comPrompt and tool packagingAttached toolsClient integrationPer-tool metering

What they do

MerchantDuo is a Magento-native coding companion. Its Magento expertise lives in a Neutrome model with attached knowledge tools, so the CLI stays a thin client. You can see it live at merchantduo.com.

The problem

  • Magento 2 guidance depends on the version, edition, and theme. A general coding model can give the wrong answer with confidence.
  • The expertise had to be updatable without shipping a new CLI release to every developer.
  • The agent CLI should not have needed forking to gain domain knowledge.

What they built

  • A dev/coder-1 model with the MerchantDuo persona and Magento instructions over a fast upstream model.
  • Attached knowledge tools that retrieve Magento context during generation.
  • A workspace runtime the CLI points at with its scoped access key.

The model catalog

dev/coder-1

The MerchantDuo coding model uses a system prompt and tool set over a fast upstream model under one model id.

Attached tools

magento_core_knowledge

Retrieval over Magento 2 core documentation and conventions.

magento_knockout_knowledge

Retrieval over Knockout.js frontend patterns that general models often get wrong in Magento storefronts.

What changed

  • Updating the deployed model updates the knowledge available to developers on their next request.
  • The CLI uses a base URL and API key without an SDK, fork, or agent framework.
  • Tool invocations are metered separately from inference, so the knowledge layer has a visible cost.
Visit merchantduo.com

Build a workspace for your product

Create a workspace, choose a namespace, and deploy the first model.

Open the platformBack to showcases