Skip to content

v0.48.1

Choose a tag to compare

@ThorstenBrach ThorstenBrach released this 27 Oct 23:27
· 252 commits to main since this release

[0.48.1] – 2026-10-27

Release since v0.28.5: the knowledge of TcAgent in levels (company, user, team, platform, project) with skills,
workflows and Git sources, self-improvement from run logs, a knowledge window to manage all of it, backups of the
knowledge, a chat window on the Agent Client Protocol and issue forms with anonymized reports. The internal versions
0.29.0 to 0.48.0 were not published; their changes are summarized here.

Added

Client neutrality

  • tc_ask_user: questions of the agent with options (recommended first) and a free answer in every AI client – a card
    in the TcAgent Chat, the client's own question dialog (MCP elicitation) elsewhere.
  • %LOCALAPPDATA%\TcAgent\settings.json as the single source of TcAgent's settings and of the registered server;
    setup-clients.ps1 sets up every client from it. TcAgent.exe applies its env at every start (a variable set by the
    client or the pipeline wins).
  • AGENTS.md as the single guide file in a project (CLAUDE.md and GEMINI.md import it).

Knowledge levels and platforms (docs/KNOWLEDGE_LAYERS.md)

  • One scheme for coding rules, risk rules, skills, workflows, lessons, documentation sources and templates on the
    levels built-in → company (TCAGENT_COMPANY) → user → team (TCAGENT_TEAM, several with ;) → platform → project;
    the later level wins. One file per topic, front matter in the Agent Skills format with tcagent-locked /
    tcagent-force, disabled.json switches files off without changing them.
  • Platforms (automation frameworks): <company or user>\platforms\<name>\ or own repositories (TCAGENT_PLATFORMS);
    set in .tcagent\config.json or detected from the referenced libraries and terms of platform.md, ambiguous → the
    agent asks.
  • tc_knowledge (platforms, effective, why, disable/enable, split), scope=team|platform:<name> for the tools that add
    rules, skills and lessons; a shared level in Git changes by a commit on a new branch for a pull request, never pushed.

Skills and workflows

  • Skills in the open Agent Skills format (<level>\skills\<name>\SKILL.md), tc_skills (list, show, add, mirror),
    built-in TwinCAT skills requirements-interview, plc-debugging, plc-code-review. The skills that apply everywhere
    are mirrored into the skill folders of the agent CLIs – by the client setup and at every server start, only what
    changed (TCAGENT_SKILL_MIRROR=0 switches it off).
  • Engineering workflows with checkpoints (<level>\workflows\<name>\WORKFLOW.md, check-ok, build-ok, tests-ok),
    tc_workflow, built-in workflow new-feature (requirements → change plan → code → check → build with 0 errors →
    tests → review → save). A checkpoint step runs the check itself.
  • Hard gate before tc_activate: a build with 0 errors first (TCAGENT_ACTIVATE_GATE=0 switches it off); the refusal
    tells the agent to show the errors and ask before changing code.

Self-improvement

  • Run logs of the workflows, locally in %LOCALAPPDATA%\TcAgent\runs\ (counts and names only, last 100 runs).
  • tc_improve: KPIs per workflow, proposals by fixed rules (step hints, revert, promote lesson, frequent error,
    duplicate lesson, stale tool), apply after asking, evaluation over the next 10 runs, revert, promote with a check for
    project and machine names (privateTerms).

Sources: skills, workflows and rules from Git repositories

  • tc_sources and TcAgent.exe sources: add a repository, search, install (license check: MIT, Apache 2.0, BSD, ISC
    accepted with their notice, source-available and unlicensed refused, others only after confirmation; scripts are
    listed, never run), status, pull, diff, promote. <level>\skills.lock.json pins every item (commit, checksum,
    license); TcAgent.exe sources sync restores exactly these in a pipeline.
  • Overlay skills (metadata.tcagent-extends) adapt a general skill without copying it.
  • Install into every level; a level kept in Git gets a commit on a new branch for a pull request.
  • Local changes of installed items: the state locally changed / upstream newer / both changed (checked on opening,
    refreshing and saving); compare with the installed version (compare window of Visual Studio), revert, keep as own
    version (tcagent-detached), update and merge three-way (conflicts in the merge window of Visual Studio), propose
    upstream as a pull request (a branch in a working copy of the source plus a patch – pushed only when you confirm, to
    the source or your fork), uninstall. tc_sources action=changes|merge|propose|revert|detach|uninstall.

Knowledge window (View > Other Windows, or ⋯ > Knowledge in the chat)

  • Overview (KPI tiles, workflows, improvement proposals), Files (every knowledge file of every level with its status:
    new, add existing, open, rename, move to level with name check, switch off/on, delete, copy path; Git per level with
    fetch, pull, commit, push), Sources (sources and installed items with all actions above, browse and install),
    Platforms (detection, set for the project, new, delete), Documentation (every source of tc_docs with its state:
    add links, folders and documents, search like the agent with hits that open – PDFs on the page of the hit), Feedback
    (see below), History (workflow runs, adopted changes, backups), Levels … (company, team and platform folders in
    settings.json).
  • One vocabulary and order in every tab; toolbar and context menu show the same actions; errors as a message.
  • TcAgent.exe knowledge json|new|move|rename|delete|disable|enable|git|platform|docs|feedback|settings – the actions
    of the window for scripts.

Backup and restore of the knowledge

  • Every level is backed up automatically before every change (knowledge window, chat tools, command line) as a ZIP with
    manifest.json (TcAgent version, level, SHA-256 of every file), only when it changed since its last backup, the last
    20 per level, in %LOCALAPPDATA%\TcAgent\backups\knowledge\. A level in Git: its uncommitted changes only.
  • Restore of the whole level, one file or one skill/workflow: the difference first, then the confirmation; the current
    state is backed up before. Backup … / Restore … in the knowledge window, TcAgent.exe knowledgebase list|backup|diff|restore.

Chat window

  • The chat speaks the Agent Client Protocol (ACP): a persistent session, live text and tool calls, permission cards,
    Stop as session/cancel. GitHub Copilot is the first ACP backend (copilot --acp); setup-clients.ps1 switches the
    former Copilot entry over. The stream-json way stays for Claude Code.
  • Copy diagnostics in the ⋯ menu.

Tests and deterministic first (docs/DETERMINISTIC_FIRST.md)

  • tc_test_skeleton: the TcUnit test suite of a function block, generated the same way every time (enable bools,
    an InitialOutputs test, one test per public method with every parameter, naming and folder of the existing
    suites, instanceName).
  • The TcUnit Tests window shows a run started by an AI client live.

Feedback and support

  • The knowledge window anonymizes tc_feedback reports (names of computer, user, solution and projects,
    privateTerms, user folders, paths, IP addresses / AmsNetIds) for editing and opens them as a prepared GitHub issue –
    you check and send it yourself.
  • TcAgent.exe diag: versions of TcAgent, extension, TwinCAT and IDEs, runtime state, Windows, .NET, knowledge levels
    as a Markdown list without names or paths.
  • GitHub issue forms (bug report, feature request, reports from TcAgent) with a Diagnostics field, questions in the
    GitHub Discussions, private security reports (SECURITY.md).

Runtime data backup – experimental

  • tc_backup / TcAgent.exe backup|restore: persistent variables, the RETAIN/PERSISTENT variables of the code and
    include patterns (recipes, parameters; .tcagent\backup.json) via ADS into one JSON file per PLC; diff; restore
    writes only values that differ to symbols that exist with the same type, only to allowed targets, after confirmation
    and with the PLC stopped unless whileRunning. Experimental: not yet tested against a running PLC.

Changed

  • Coding workflows end with a build with 0 errors, always preceded by tc_check (a pre-compile without code
    generation); the guidance of every agent says so.
  • Agents change code only when the user asked for a change; errors found on the way are reported and the user is
    asked.
  • tc_coding_rules shows the level of every rule file and the platform of the project and lists skills and workflows.
  • Documentation sources are read from every level including the team levels; tc_docs action=sources shows level and
    state; tc_docs_add refuses entries that are neither a URL nor a folder.
  • TCAGENT_LESSONS keeps working; TCAGENT_TEAM\lessons\ replaces it.
  • TcAgentBridge serves several requests at once; messages name no single AI product.
  • setup-clients.ps1 writes a configuration only when it changes and keeps the first and the last 3 backups per file.

Fixed

  • A running chat session kept talking to the server it started with after a TcAgent update; it now restarts with the
    new server. Changes of chat-backends.json take effect without restarting Visual Studio.
  • A test run started from the chat blocked the IDE briefly for every event.
  • tc_test_skeleton left out required inputs, which did not compile.
  • Names with capitals or spaces (platform, skill, source) were refused with a message in the status line only.
  • The backup list in the History tab got no height in a smaller window.