Configure¶
All settings live on one gateway page. A fresh install has no API keys and refuses every request, so you need at least one key before an assistant can connect.
Open the settings page¶
In the gateway web page, open Home → Artek Designer → Designer Bridge (the page is at /app/artek-designer). You must be logged in to the gateway.
Settings¶
| Setting | What it does | Default |
|---|---|---|
| Enable edits | The master switch. While it is off, every edit tool is refused with edits_disabled, and the look-only tools still work. |
Off |
| Requests per minute, per key | How many calls one key may make in a sliding 60-second window. | 120 |
| Requests per minute, all keys | How many calls all keys together may make in a sliding 60-second window. | 600 |
| Relay timeout | How long a command may wait for the Designer to answer, from 5 to 120 seconds. | 20 seconds |
| Allowed browser origins | Only for browser-based MCP clients that send an Origin header. |
Empty |
| API keys | One key per person. See API keys. | None |
Rate limits¶
A caller over its budget gets HTTP 429 with a Retry-After header saying how many seconds to wait. Raise the limits here if your team needs more.
Relay timeout¶
A view_apply batch gets the relay timeout plus 1.25 seconds for each operation in the batch, up to a maximum of 5 minutes.
Allowed browser origins¶
Claude Code, Codex CLI and the Claude Desktop bridge send no Origin header, so you can leave this empty for them. When it is empty, the gateway accepts its own host name and localhost.
Allow executing content¶
Some view and report 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 ticks Allow executing content on this settings page. It is off by default, and the page shows the current state as ALLOWED or REFUSED. Turn it on only when your team needs the assistant to build that kind of content.
API keys¶
Create one key per person. For each key you set:
- Name: identifies the key in the audit log.
- Ignition user: the one user the key is bound to. The key can drive only this user's Designers, and only while that user has switched Claude on.
- Projects: the projects the key may drive. Use
*for any project.
The secret is shown exactly once, when you create the key. Copy it then. The gateway keeps only a salted SHA-256 hash and the last four characters, so it cannot show the secret again.
You can disable or delete a key on the same page. A disabled or deleted key gets HTTP 401.
Create a key without the web page¶
For scripted setup, you can create a key by writing a file on the gateway:
config/resources/core/com.artek.designer/api-key/<name>/config.json
Put the secret in a cleartext secret field. On the next config scan or gateway restart, the module replaces the cleartext with its hash and writes one WARN line to the gateway log naming the key.
Next step¶
Connect your AI assistant with the key name and secret.