Install¶
You install Artek-Designer on the gateway once; every Designer that opens afterwards gets the Claude panel automatically.
Recommended for development and test gateways
Install Artek-Designer on a development or test gateway, not a production gateway.
Requirements¶
- Ignition 8.3.4 or later with the Perspective module. Tested on Ignition 8.3.8. If your Ignition version is not on the tested list, the Designer flags it in the Claude panel and in the
designer_statustool. - The Reporting module (optional). Without it, the module still loads and only the report features switch off.
- Trust in the Artek module-signing certificate. If Artek-MCP is already installed, the gateway already trusts it. Otherwise the first install asks you once to accept it on the gateway's welcome page.
- An MCP client that can send an
Authorizationheader over HTTP: Claude Code, Codex CLI, or Claude Desktop through themcp-remotebridge. See Connect.
Release facts¶
| Module ID | com.artek.designer |
| Version | 1.0.0 |
| Signing certificate (SHA-1) | 99e472815b3417abab93e1c744c76699c73375d2 (Artek, LLC) |
licenseAgreementHash |
3030118439 |
| Minimum Ignition | 8.3.4, with Perspective; tested on 8.3.8 |
The license agreement is shown when you install the module. See artekis.io for licensing.
Web install¶
- In the gateway web page, open Config → Modules → Install or Upgrade a Module.
- Upload
Artek-Designer.modl. - Accept the certificate and the license agreement.
Disk install (unattended)¶
Use this method when you script gateway setup and cannot click through the web page.
- Copy
Artek-Designer.modlinto the gateway'sdata/var/ignition/modl/folder. - Add an entry for the module to
data/modules.jsonwith:certFingerprint:99e472815b3417abab93e1c744c76699c73375d2licenseAgreementHash:3030118439(the CRC32 of the module's embedded license agreement)
- Restart the gateway.
Check the install¶
After either method, the gateway log shows:
Artek-Designer <version> gateway hook started
Every Designer that opens from then on carries the Claude panel, docked on the right.
Relaunch open Designers¶
Relaunch every Designer that was open during the install
A Designer that was already open while you installed or upgraded the module keeps running the old version. Close it and launch it again. Until you do, designer_status reports jarMatchesGateway:false for that Designer.
Next step¶
Configure the module: turn on edits and create an API key. A fresh install has no keys and refuses every request.