FAQ#
Short answers to common questions. Each answer links to the deeper section when relevant.
Q: What is a .urp file?#
A .urp is a Universal Robots program file. PolyScope on the robot pendant loads .urp files; ChatURP imports them, edits them through prompts, and exports a .urp you can copy back to the robot (source). Each .urp is paired by name with a .installation file (its TCP, payload, safety, I/O and mounting settings); ChatURP can export the matching .installation alongside the program so it loads with the right setup. PolyScope X uses a single .urpx bundle instead, which carries the program and its application settings together.
Q: Which UR firmware versions are supported?#
ChatURP imports .urp files from CB-series (PolyScope 3.x) and e-Series (PolyScope 5.x), and .urpx files from PolyScope X (10.x, on UR20 / UR30 and recent e-Series controllers). Diagnostics reads support files from CB-series and e-Series (source).
Programs saved by PolyScope older than 3.2 use a different file layout and are refused on import, with a message asking you to re-save the program in a newer PolyScope or URSim first.
Q: Can ChatURP work with PolyScope X?#
Yes. Import, read, build and edit .urpx programs the same way as PolyScope 5. One thing to know: a conversation is tied to one robot generation, chosen with the PolyScope 5 / PolyScope X toggle before the first prompt, and it cannot be changed later — dropping a .urpx into a PolyScope 5 chat (or the other way round) is refused, so start a new conversation for the other format (source).
Q: Why does my exported .urp fail to load on the robot?#
The most common cause is a PolyScope version mismatch — a program edited against e-Series structures will not load on an older CB-series controller. Check the robot's PolyScope version against the file you imported, and re-import the original .urp if you have made unrelated structural edits (source). If the program loads but a node shows an error, open it on the pendant to see which field PolyScope rejected, then adjust via prompt.
If an installation is attached to the conversation, the export is a .zip: copy every file in it to the robot, not just the .urp — the robot pairs the two by name.
Q: Is my data uploaded to your servers?#
It depends on the page.
Chat: yes — your prompt and the current program are sent to our AI provider so it can generate the next edit (source).
Diagnostics: the support file itself is never uploaded — browsing its logs, events and telemetry happens in your browser. Two things do leave it. Generating a Performance report or opening Advanced Analytics sends the program, installation and telemetry the report is built from to our service, which builds the result itself without an AI provider. An AI analysis sends the log rows you selected — timestamps, event codes, messages and the component that raised them — plus the robot's identity and the problem description you typed, on to our AI provider; the program and installation are deliberately not included. The analysis it produces is stored on your account so you can re-open something you paid for from any device, and is deleted when you delete your account (source).
The full detail, including who our AI provider is and how long it keeps what we send, is in the Privacy Policy.
Q: Which AI model do you use? Can I pick?#
ChatURP picks the model on the server. There is no user-facing model selector and no reasoning knob, and every request costs the same flat 1 credit (source). Which provider runs that model, where it is hosted, and what we send it are named in the Privacy Policy.
Q: What does a request cost?#
One credit per message you send the AI — question or edit, simple or complex — and one credit to import a program. A new account starts with 30 credits; they are a one-time allowance and do not refill. Paid plans add a monthly allowance (Starter 100, Pro 250), and Diagnostics has its own prices for uploads, reports and AI analyses (source).
Q: How accurate is the generated program?#
The AI is reliable on common operations (Move, Loop, If, Wait, Set, palletizers). Treat every generation as a draft: read the program tree, verify each node, and run it in simulation on the pendant before production use (source). Nothing is saved as your program until you press Accept on the proposal banner (source). Use the feedback dialog if a generation is wrong so we can improve the prompts (source).
Q: How do I save a conversation?#
Conversations save automatically — every prompt and every accepted program version is persisted to your account as soon as it completes. Use the sidebar to rename or delete them; there is no manual save step (source).
Q: How do I cancel my subscription?#
Open /account, go to the Billing tab, and click Manage subscription — this opens our payment provider's portal where you can cancel, change payment method, or download invoices (source). Cancellation takes effect at the end of the current billing period; you keep your plan and your credits until then, and the remaining balance is set to zero when it takes effect.
Changed your mind? Undo it in the app, not the portal — the Billing tab shows a Resume subscription button while the cancellation is still pending, and the portal has no way to reverse one (source).
Q: Can I self-host?#
Not at this time. The hosted version is the only supported deployment.
Q: Where do I report a bug?#
Use the Feedback button in the bottom-right corner of any page while signed in. Pick a category, describe what happened, and — for a bad generation — tick Include debug data to help us investigate, which attaches the current conversation and program. That checkbox is off by default, so nothing about your program is sent unless you tick it; Show debug data preview shows exactly what would go. You can also attach up to three files (screenshots, a .urp, logs) with Add files (source).
For anything that is not about a specific conversation — billing, account or diagnostics problems — use the contact form and include steps to reproduce.