butteredstardust/twaco

---

ThingWorx keeps a solution’s code inside entity XML, with every service script in a CDATA section. That is hard to edit, review, diff or hand to an AI agent. twaco makes your repository the source of truth: edit scripts as plain files, check them offline, and deploy without overwriting anyone else’s work. It is one binary for Windows, Linux and macOS, with no runtime to install.

What you can do

• Edit scripts as files. extract writes service scripts, DataShape fields, mashups and DataTable settings to files under src/; sync puts them back, changing nothing else.
• Start from what you have. init sets up a repository from a folder of exports, or with --from-server from projects on a server; entity pull takes in later server changes.
• Build without Composer. new creates Things, templates, shapes, DataShapes, DataTables, timers, styles, menus and more; thing edits services, properties and subscriptions; mashup builds mashups from templates, with widgets, bindings and events.
• Refactor safely. rename, move and copy follow every reference through entities, scripts and mashups, and show the plan first.
• Understand before you change. catalog shows a service’s signature and script, impact what a change reaches, trace how callers use a service, unused what nothing uses, and docs writes the solution up as Markdown.
• Catch problems before the server does. check runs every gate in one pass: sidecars in sync, formatting, script traps, mashup bindings, localization tokens, structure against ThingWorx’s export schema, and your own hooks. types --check type-checks scripts.
• Deploy without clobbering. deploy has the server parse every script, refuses when someone changed an entity since your last deploy, and reads back what it imported.
• Take in a designer’s work. adopt compares a Composer export with the repository and shows only what really changed.