The Plant AI Agent

Describe your process, drop in a routing sheet or BOM, and let the AI write and check your plant's files.

Writing a plant by hand means learning a file format before you can describe a single station. In Plant, the AI does that part. Tell it what you want in plain words, or hand it the routing sheets and BOMs you already have. It writes the plantformat files, checks them, and fixes what it breaks before it replies.

#What it is

The AI panel talks to the same Threaded assistant on every page. In Plant, it also works on your plant’s files: it knows which plant and file you have open, edits the files in your workspace, and runs plantformat to check them. It can still answer anything else about your organization.

#Rules

  • It edits only your own workspace. Its changes are drafts until they’re committed, like your own edits.
  • It commits only when you ask it to save. Before it does, it checks the plant, shows you which files it will commit and anything newer from your teammates, and waits for you to agree.
  • It commits to dev, never to main. It never pushes to the floor: a person does that with Push. See Plant Git and Imports.
  • It never force-pushes, so it won’t overwrite your teammates’ work.
  • Before it changes a file that several parts share, such as a routing or a spec, it checks which parts the change affects and names them in its reply.
  • It treats validation errors as its own to fix. Warnings aren’t failures, so it may leave them and tell you.
  • It needs the AI Assistant and the Planning Workspace, which are turned on per organization. See Feature Access and Billing.
  • Owners, Editors and View All members can use it in Plant. Only Owners’ and Editors’ assistants can commit.

#In the app

#Open it

Click AI in the toolbar. The panel opens on the right. Click View as full page for more room, and Dock to sidebar to put it back. The first time it needs your workspace, it shows Starting workspace… while the workspace wakes up.

#Start from what you have

You don’t need to write the files yourself. Give the AI what you already have:

  • A routing sheet, a BOM or photos. Attach them to your message. The AI reads them and turns them into the map, parts, routings and instructions. Spreadsheets work too.
  • A description. Describe your stations, parts and how material moves. The AI asks questions when it needs more.
  • Your Threaded map. The AI can export your published Threaded map and parts into a plant to start from.

There’s no separate import screen for routing sheets or BOMs: attach the file and ask.

#Change your plant

Ask for changes by their effect on the floor, for example “add an inspection after welding” or “the bracket now takes four bolts”. The AI:

  • Edits the files and checks the plant after each change.
  • Tells you which parts a change to a shared file affects.
  • Describes what it changed in plain words.

The preview rebuilds after its changes, so you can check the result in Map, Instructions and Parts.

Sometimes it pauses with Checking in so you can look at its work. Click Continue, or send a message to change direction.

#Save your changes

Ask the AI to save when you’re happy with the result. It commits to dev, the same as clicking Commit, after you agree to the files it lists. If a teammate changed the same lines, it asks whether to keep your version, use theirs, or combine them.

When you click Commit yourself and it conflicts, Ask the assistant to combine hands the merge to the AI. It keeps both sides’ intent, checks the plant and commits.

To send committed changes to Run, click Push yourself.

#From the CLI or API

The assistant uses the same tools you can: plantformat validate, plantformat impact (which parts a file change affects) and threaded task map:export. On your own computer, run plantformat through the CLI, for example threaded plantformat validate <plant-folder>.