Skip to content

Artek-Designer

Artek-Designer lets an AI assistant build Perspective views and reports live inside your open Ignition Designer. You watch every change land on the canvas, you can undo any of them with Ctrl+Z, and you are the only one who presses Save.

Where Artek-Designer fits An AI client connects to the Artek-Designer endpoint on the gateway. Its policy and relay pass edits to the user's open Designer, where the user has switched Claude on in the Claude panel. Changes land live on the canvas, each undoable, and reach the project only when the user presses Save. AI client Claude Code, Codex, Claude Desktop Ignition Gateway Artek-Designer MCP endpoint one key per person, bound to one Ignition user Policy and relay edits off until enabled; every call audited Project changes only when you press Save Your open Designer Claude panel you switch Claude ON or OFF; Stop at any time Views and reports changes land live on the canvas; every change is one Ctrl+Z You review, undo, then Save edits Save
The assistant edits your open Designer live; nothing reaches the project until you press Save.

It is an Ignition 8.3 module (com.artek.designer). The assistant connects to it over MCP (Model Context Protocol), so any MCP client that can send an Authorization header over HTTP can drive it, including Claude Code, Codex CLI, and Claude Desktop.

Recommended for development and test gateways

Artek-Designer is meant for development and test gateways. We recommend that you do not install it on a production gateway. Build and review your views and reports on a development or test gateway, then move the finished project to production the way you normally do.

What it does

  • Builds and edits Perspective views in the Designer you have open: properties, bindings, events, component scripts, property-change scripts, adding, deleting, wrapping, replacing and reordering components.
  • Builds and edits reports when the Reporting module is installed: report layout, parameters and data sources, plus page previews from the Designer's sample data.
  • Looks before it acts. The assistant can read a view, list component types and their schemas, and take a screenshot of the canvas without changing anything.
  • Warns you about outside changes. If a project you have open changes on the gateway (a disk edit, an import, a gateway API write), the Claude panel shows an amber warning naming the resources, so you can update the project before you save.

Safety model

You stay in control at every step. Several independent switches must all be on before the assistant can change anything.

  • The module ships read-only. Edits stay off until an administrator turns on Enable edits on the gateway settings page. Until then, only the look-only tools work.
  • Claude is off in every Designer until you switch it on. Each Designer has a docked Claude panel. Claude starts switched OFF; you switch it ON for that Designer, and the one-click Stop switches it off again and discards whatever is in flight.
  • Nothing is saved until you save. No view or report layout change reaches the gateway until you press Save in the Designer. Each change is an undo step you can reverse with Ctrl+Z (see what is and is not undoable).
  • Executing content is refused unless allowed. Some content can run before you save: view bindings that query, script or write tags, property-change scripts, and scripted report charts. The module refuses to create this content unless an administrator turns on Allow executing content, which is off by default.
  • Each key is bound to one user. Every API key belongs to one Ignition user and can drive only that user's switched-on Designers, and only on the projects the key is granted.
  • Every call is audited. Each call, whether allowed or refused, writes one line to the gateway log. See Audit and troubleshooting.
  • It checks itself at start-up. Each Designer tests the Perspective features it relies on when it starts. If a test fails, only that feature switches off, with the reason shown in the panel; the rest of the module keeps working.

Report data sources run on the gateway

A report's data sources run on the gateway when they are set, read or previewed, even before you save. Only the report layout waits for Save.

Where to go next

  1. Install the module on your gateway.
  2. Configure it: turn on edits and create an API key.
  3. Connect your AI assistant.
  4. Use it in the Designer.

The tools reference lists everything the assistant can do. Licensing is covered by the license agreement shown at install; see artekis.io for licensing.