14. Settings

For each area — family and size (0 = default): program interface, map table, axis labels, map tree, charts, identity panel. Reset per area and Reset All.

The full list of actions with shortcut editing and reset. The Filter… field above the table hides the rows you do not need. When shortcuts collide, the "Shortcut Conflict" dialog appears and offers to reassign.

Language, theme, colors, fonts, keyboard shortcuts, layout, panel positions, recent projects, fault code sets, disabled catalogs, the checksum recalculation choice and the "show identical maps" preference during comparison. Open maps, flags, notes, scale and charts are stored only in the project (§5.1); crash recovery data — separately (§5.3).

TCEPro can let an AI agent (an artificial intelligence client that supports MCP) read and, if you allow it, edit the maps of the open project. The agent connects through the bridge program tcepro-mcp.exe from the installation folder. Step-by-step client setup is in the file ai\SETUP.en.txt next to the program, together with the skills for the agent (ai\skills). On Linux the bridge is inside the AppImage file: in the AI client's settings, give the path to the AppImage file and the --mcp-bridge parameter.

Turning it on. Settings → Preferences… → the "AI agents (MCP)" tab → "Allow AI agents to connect". It is off by default. Turning it on does not allow anything by itself: you confirm each connection in the "AI agent connection" window after checking that the six-digit pairing code matches the code the agent showed.

What the agent can never do: get the catalog's internal data; change error maps (§7.3); compare files; export the firmware or decide on checksum and RSA recalculation — you do that in the program window.

What you see. In the status bar — the "AI agent: …" indicator and the Disconnect button. Clicking the indicator opens the "Agent journal" panel (View → Agent journal): every agent call with the name of the map or file, your decisions and the table of limits. With "Show the agent's actions on screen" checked (on the same settings tab, on by default), the map the agent reads or changes opens in a window — table, axes, chart — and you see the changes at once.

The agent's edits.

• Before the first edit of a connection, a checkpoint of the whole project "Before the AI agent session HH:MM" is created (§9). If the project already has 50 checkpoints, the edit is refused — delete one you no longer need.
• Each agent edit is a step of the undo history marked "(AI agent)": Ctrl+Z undoes it like your own. The agent undoes only its own edit that you have not worked on top of.
• Values are limited to the map's range and rounded to its step — as when typing into the table.
• While a firmware comparison is open, the agent cannot edit, just like you.
• The agent opens no windows of its own. If its action needs your decision (for example, unsaved changes before another file is opened), the status bar shows "The AI agent is waiting for your decision in TCEPro", and the agent is told to wait for you.
• Before exporting the firmware after agent edits, the program shows how many maps it changed in this session and which. The default button is Cancel; double-clicking a map opens it.

Limits.

Reading or editing the same map again within an hour and opening the same file again are not counted. When an hourly limit is used up, a bar above the work area offers to Extend by one more hourly portion (once an hour) or Do not extend. A daily limit cannot be extended. The counters are kept across restarts of the program.

The permission ends when the agent disconnects, after 30 minutes without calls, when the computer is locked, sleeps or the Windows session changes (on Linux — only on disconnection and after 30 minutes without calls). The next connection is confirmed again, with a new code.

Data. Everything the agent receives — map names, units and values, notes, file names — goes to the AI provider you chose. You are responsible for the edits you allowed the agent to make: check them before exporting. The license server receives only the "access is on" flag and the number of different maps the agent read and changed in 24 hours. The records of the agent's work on disk contain no map names, file names or values.