Settings

Global settings

Reached from the Settings row at the bottom of the sidebar, from the user menu, or from the header gear button on a backend with no sign-in. Four labelled groups, so a card's position says what it holds. Save stays disabled until something changes, and leaving with unsaved edits asks first. The key cards are separate: generating a key takes effect immediately and needs no Save.

Identity

• Mainframe user: one TSO/USS login, typed once. AtomIQ, CoreIQ and every host connection inherit it unless they override it. Inherited by lists what actually reads it and names the connections that override it, and under which user.
• Committer identity: name and email on commits across every application, plus an optional default remote URL prefilled when configuring new applications. It is not a credential: Git passwords are asked for when a remote operation needs them.

Gateways

• CoreIQ: the platform URL and a Default host picked from the hosts CoreIQ reports. It takes the mainframe user by default; untick Use the mainframe user to give it its own account. New host connections start from this URL and host, and a saved host name is kept even when CoreIQ is unreachable.

Integrations

• AtomIQ: the URL operations are pulled from, with the same credentials control CoreIQ has.
• AI provider: LLM provider (OpenAI, Anthropic, Ollama), model name, API key and custom URL, for AI modernization and flow generation.

Access out

• MCP access: generate, rotate or remove the key remote callers send to /api/mcp. Shown only when no identity provider is configured. A deployment can set OL_MCP_API_KEY instead, which overrides the generated key and makes this card read-only.
• API access: an OpenLegacy Hub key a script or agent sends as x-api-key on any /api request.
• Host connections: a count and a link; the connections live on their own page.

Application settings

A dialog from the application row's ⋯ menu → Settings…. It opens over whatever you were doing and closes back onto it, and it edits the active application, so choosing Settings… on another row switches to that application first. Three groups and one Save, written in order (General, then Data source, then Git), stopping at the first that fails and reporting under the group that refused. The footer names the groups holding unsaved edits, and while any of them does, clicking the backdrop or pressing Escape will not dismiss the dialog.

• General: rename or describe the workspace.
• Data source: Sample data or Live host, for SQL programs, IMS DL/I and VSAM during play. Choosing a connection prints its engine, reach and endpoint by the names CoreIQ reported when it was saved, so the readout stands even when CoreIQ is unreachable. With no connections yet, the dialog offers to create one. What the body then asks for follows the engine: a schema for DB2, nothing for IMS DL/I, and the CICS FILE-to-dataset map for VSAM. See Live host data through CoreIQ.
• Git: remote URL, default branch, Init / Clone / Disconnect, and connection status.

Operation settings

The ⋯ menu beside the application selector, or the sidebar edit icon, renames or deletes an individual operation and its files.

Source control

Each application can have its own Git working tree, holding its original sources, generated code, flows and tests.

1. In the application's Settings… → Git, enter an HTTPS remote URL and a default branch, then Save.
2. Click Init to create an empty repository, or Clone to pull an existing remote.
3. On the first push, pull or clone, enter your Git host credentials when prompted.

The Source Control panel at the bottom of the sidebar shows the current branch, ahead/behind counts, and Staged, Changes and Untracked lists. Use Stage all, enter a message, then Commit or Commit & Push. Push publishes the branch that is checked out; the default branch only seeds Init and Clone. The panel's ⋯ menu has Pull, Pull rebase, Push, Refresh, New branch, Credentials and Disconnect, which removes the application's .git directory. The panel refreshes on its own after imports, builds, flow saves and AI modernization, and can pop out into a floating window.

Use HTTPS with a personal access token; SSH remotes are not supported. Your username is saved in this browser per Git host, and the token is kept for the current browser session only.