Settings

Theme

Match system follows your machine, including when it switches at sunset.

Pet

The creature along the bottom of the window, on wide screens.

Reduce motion

Stops the background drift, the logo row and the scroll animations.

Terms

The terms you accepted on your first visit.

Read the full terms →
Runs inside Studio · graph on your disk

ROTEX parses your Studio project with Tree-sitter and keeps the result as a library graph on your disk. Questions about your code are answered from that file.

Get startedInstallation guide

ROTEX

explorer

client / studio plugin

boundary (command queue)

server / command queue

  • 14:02:11Reparsed 46 changed scripts310ms
  • 13:47:03Docs cache for the API reference is 17m stale1.4s
  • 13:31:56Module graph rebuilt, 9,610 edges1.2s
  • 13:12:40Ambiguous reference: captureNote() to scanTree()n/a
  • 12:58:09Context snapshot written88ms
  • 12:44:22Full scan, 1,284 files2.1s

inspector

No node selected. Pick one on the canvas, or a file in the explorer.

Connected

Graph nodes

Twenty-nine nodes across the boundary. Fourteen run inside Studio, two are the command queue itself, and thirteen are reached through it. Every edge that crosses the divider is a queue message; nothing else does. Select a node to read its metadata and its connections.

A live force-directed graph of the ROTEX system, settled into two zones either side of a dashed boundary. Inside Studio: the plugin, its state, the extension registry, three extensions (SmartNotes, StaticAnalysis and LibraryFinder), the user interface, the methods those expose, the plugin guide and the current release. On the boundary: the queue's enqueue and poll methods. Beyond it: the MCP server, the command queue and its worker, the context engine, the library graph, the graph store and embed index, two repositories, the API reference and the published version. Line style is evidence: solid means the parser read it, fine dashes mean it was inferred or is ambiguous. Selecting a node dims everything more than one hop away.

Tree-sitter parsein place
Static analysistypes, requires
Library grapha file on disk
Context enginereads the file

Your project source is never enqueued. What crosses the gate is a scoped context, and one cached documentation lookup.

The boundary

Four facts about what leaves this machine.

  1. 01

    Your scripts are read where they sit.

    Tree-sitter parses the open place on this machine. What it produces is a library graph: a file on your disk, next to the project it describes.

  2. 02

    Questions are answered from that file.

    Intent analysis, graph traversal, relevance ranking and context packing all run locally against the graph. The answer to “what does this script depend on” never needed the network.

  3. 03

    One input comes from outside.

    Library documentation, cached for fourteen days. The pipeline diagram marks it as the single off-machine input, and it is the only arrow that enters from beyond the boundary.

  4. 04

    Your project source never crosses.

    A scoped generation context goes to the model that writes the code. The source itself is never enqueued, because that path stops at the boundary, and what comes back is parsed and type-checked before it reaches Studio.

Each of these is drawn in the diagrams further down the page, and can be checked against them.

The library graph

The whole system as one settled picture. Drag to pan, scroll to zoom, and pick any node to read what it is and walk its connections. The dashed line is the boundary, and every edge that crosses it is a queue message.

Graph legend

  • Library5
  • Method7
  • Script9
  • Repository4
  • Documentation2
  • Version2

  • DEPENDS_ON

    structural ◆

  • HAS_METHOD

    structural ◆

  • REFERENCED_BY

    informational ◆

  • DOCUMENTED_BY

    informational ◆

  • INFERRED_USE

    inferred evidence ◇

  • AMBIGUOUS_REF

    ambiguous evidence ◌

  • QUEUE_MSG

    crosses the boundary ◆

80% zoom

Graph nodes

Twenty-nine nodes across the boundary. Fourteen run inside Studio, two are the command queue itself, and thirteen are reached through it. Every edge that crosses the divider is a queue message; nothing else does. Select a node to read its metadata and its connections.

A live force-directed graph of the ROTEX system, settled into two zones either side of a dashed boundary. Inside Studio: the plugin, its state, the extension registry, three extensions (SmartNotes, StaticAnalysis and LibraryFinder), the user interface, the methods those expose, the plugin guide and the current release. On the boundary: the queue's enqueue and poll methods. Beyond it: the MCP server, the command queue and its worker, the context engine, the library graph, the graph store and embed index, two repositories, the API reference and the published version. Line style is evidence: solid means the parser read it, fine dashes mean it was inferred or is ambiguous. Selecting a node dims everything more than one hop away.

Featured Libraries

Where each piece runs, and what crosses the boundary: how it fits together.

What it does

  • Tree-sitter parses your place into a library graph, and that graph is a file on your disk.
  • Intent analysis, traversal and ranking all read that file, so a question about your code is answered from your code.
  • Generated Luau is parsed and type-checked before it reaches Studio; what fails the check goes back to the model.

Try Pro free for 14 days.

Cancel before it ends and you pay nothing. See pricing

Before you continue

The ROTEX terms of service

Version 2026-09-30Effective 30 September 2026

The terms and licence for this site, the ROTEX app and the Studio plugin, including how paid plans renew and how to cancel at any time.

01

About these terms

These terms are an agreement between you and the operator of ROTEX. They cover this website, your ROTEX account, the ROTEX desktop app and the ROTEX Roblox Studio plugin (together, “ROTEX”). They are also the end-user licence for the app and the plugin.

ROTEX is operated by its operator (“we”, “us”).

Contact us through the requests page.

By creating an account, installing the app or plugin, or buying a plan, you agree to these terms and confirm you have read the Privacy Policy. If you don't agree, don't use ROTEX.

02

Who can use ROTEX

You must be at least 13 to create an account. We don't knowingly create accounts for, or collect personal data from, anyone younger. If we find an account belongs to someone under 13, we close it and delete its data.

If you are under 18 you can use the Free plan, which costs nothing and has no payment details. You should read these terms with a parent or guardian. A paid plan for your account has to be bought by your parent or legal guardian. They confirm at checkout that they have read these terms, agree to them on your behalf, and are responsible for the payments.

To buy a paid plan for yourself you must be 18 or over and able to enter a binding contract. If you buy for a company or organisation, you confirm that you are authorised to bind it to these terms, and “you” includes it.

03

Your account

Give accurate details, keep your password to yourself, and tell us through the requests page if you think someone else has used your account. You are responsible for what happens in your account unless it happened because of our failure.

You can delete your account at any time from Settings. Deleting it also cancels any paid plan.

04

Your licence to use ROTEX

While you follow these terms, we give you a personal, non-exclusive, non-transferable, revocable licence to use ROTEX for your own projects, within the limits of your plan. On Teams, the licence covers the members on the plan.

You may not:

  • copy, sell, rent, sublicense or redistribute the app, the plugin or access to your account;
  • decompile, reverse engineer or disassemble them, except where the law allows it despite this restriction;
  • get round plan limits, usage limits or security measures, or share one paid seat between several people;
  • use automated means to scrape the site or the service, or use ROTEX's output to build a competing product.

ROTEX, including its software, design and name, stays ours or our licensors'. Open-source components are licensed under their own licences, which take priority for those components.

05

Your code, your data and generated code

Your project source is parsed on your machine and is not uploaded. What does leave your machine, like a scoped generation context and cached documentation lookups, is described in the Privacy Policy and the Docs.

You keep all rights in your code. Code ROTEX generates for you is yours to use, as far as we have any rights in it. Generated code is produced automatically: it can be wrong, insecure, or similar to code others receive. It is type-checked before it reaches Studio, but reviewing and testing it before you ship it is your responsibility.

06

Acceptable use

Don't use ROTEX to:

  • break the law, or the Roblox Terms of Use and community standards;
  • build experiences that exploit, harm or target children, or that scam players;
  • infringe anyone's intellectual property or privacy;
  • create malware, exploits or cheats, or attack, overload or probe the service.
07

Roblox

ROTEX is an independent tool. It is not made, endorsed, sponsored or approved by Roblox Corporation. “Roblox” and “Roblox Studio” are trademarks of Roblox Corporation. Your use of Roblox is governed by Roblox's own terms, and we are not responsible for Roblox's platform, its changes or its decisions about your experiences.

08

The Free plan

The Free plan costs nothing and needs no payment details. Its limits are shown on the pricing page. We may change them or end the Free plan. If we reduce what the Free plan includes, we will tell account holders at least 30 days before.

09

Paid plans, trials and automatic renewal

Prices. Prices are in USD and are shown on the pricing page and at checkout before you pay. Unless checkout says otherwise, they exclude sales tax or VAT, which is worked out from your billing location and shown before you confirm. Annual plans are charged as one payment for the year.

Free trial. Paid plans start with a 14-day free trial. You enter a payment card to start it, but nothing is charged during the trial. At checkout we show the date of the first charge and its amount. If you cancel before that date, you are never charged. One trial per person or organisation.

Automatic renewal. Unless you cancel, the plan renews automatically at the end of the trial and at the end of each billing period (monthly or yearly), and the price then in effect is charged to your payment method at the start of each period. It continues until you cancel.

Price changes. We will tell you at least 30 days before a price change applies to your plan. The new price only applies from your next renewal after that notice, and you can cancel before then without paying it.

Failed payments. If a payment fails we will tell you and try again. If it still fails, the plan may move to Free. You won't lose your account.

10

Cancelling at any time

You can cancel a paid plan at any time, for any reason, in Settings › Billing. It takes no more steps than signing up did. You don't need to contact us, and there is no cancellation fee.

  • During the trial: the plan ends and you are never charged.
  • After the trial: nothing more is charged. You keep the paid features until the end of the period you have already paid for. Then the account moves to Free.
  • Your account, your settings and anything on your own machine stay as they are. Only paid features stop.

If you can't get to Settings, file a cancellation request on the requests page. It takes effect from the date you file it.

11

Refunds

If you are not happy with your first paid charge, you can have a full refund if you ask within 14 days of it, wherever you live. You don't have to give a reason. The Refund & Cancellation Policy explains this and other refunds, and how to ask. Nothing in it or here reduces your legal rights.

12

Your right to withdraw (EU and UK consumers)

If you are a consumer in the EU or the UK, you have the legal right to withdraw from a paid plan within 14 days of the day you buy it, without giving a reason.

To withdraw, use the Withdraw from contract page, linked from the foot of every page, or send us any clear statement. We confirm receipt straight away. We refund every payment under the contract within 14 days, to the original payment method, at no cost to you.

Your plan starts with a 14-day free trial, so the withdrawal period normally ends before you pay anything. If you withdraw after being charged, you get a full refund.

13

Changes to ROTEX and availability

We improve ROTEX over time and may change or remove features. If a change significantly reduces what a paid plan gives you, we will tell you in advance. You can cancel and get a pro-rata refund of any unused period you have paid for. We aim to keep ROTEX available, but it can be interrupted for maintenance or by things outside our control.

14

Third-party services

ROTEX works with services we don't control, such as Roblox Studio, coding agents you choose to connect, and open-source libraries. Your use of them is under their own terms, and we aren't responsible for them.

15

Warranties

We provide ROTEX with reasonable care and skill. Beyond that, and as far as the law allows, ROTEX is provided “as is”. We don't promise it will be error-free or uninterrupted, or that generated code will be correct or fit for your purpose.

If you are a consumer, you keep the rights the law gives you. In the UK that includes your rights under the Consumer Rights Act 2015 that digital content is of satisfactory quality, fit for purpose and as described. Nothing in these terms limits those rights.

16

Our liability

Nothing in these terms limits or excludes liability for death or personal injury caused by negligence, for fraud, or for anything else the law does not allow to be limited.

Otherwise, and as far as the law allows, we are not liable for losses that were not foreseeable. We are not liable for loss of profit, revenue, business or data you could have backed up. Our total liability for everything connected with ROTEX in any 12 months is limited to the greater of what you paid us in that period and USD 100.

If you are a consumer, we are responsible for foreseeable loss and damage we cause by breaking these terms or failing to use reasonable care and skill. We only supply ROTEX for domestic and private use and development. If you use it for business, we aren't liable for business losses, subject to the paragraph above.

17

Business users

If you use ROTEX for a business, you will cover our reasonable losses from claims by others that arise from your breach of these terms or from experiences or code you publish. This section does not apply to consumers.

18

Suspension and ending these terms

You can stop using ROTEX and delete your account at any time.

We may suspend or close an account that seriously or repeatedly breaks these terms, or where the law requires it. Except where it would be unlawful or unsafe, we will tell you why first and give you a chance to fix it. If we close a paid account without it breaking these terms, we refund the unused part of the period you paid for.

The sections on liability, business users and governing law continue after the terms end.

19

Changes to these terms

We may update these terms. The version and date at the top change when we do. Next time you visit, the site asks you to accept the new version. If a change affects a paid plan to your disadvantage, we tell you at least 30 days before it applies. You can cancel before then, and the old terms apply until the end of your current period.

20

Governing law and disputes

These terms are governed by the law of England and Wales, and its courts have jurisdiction. Please contact us first. Most problems are solved quickly that way.

If you are a consumer, you also keep the protection of the mandatory laws of the country you live in. You can bring a claim in your local courts. In Scotland or Northern Ireland, you may use the courts there.

21

General

These terms, with the Privacy Policy and the Refund & Cancellation Policy, are the whole agreement between us about ROTEX. If a court finds part of them invalid, the rest still applies. If we don't enforce a term straight away, we can still enforce it later. We may transfer this agreement to another organisation that takes over ROTEX, and we will tell you if we do. Your rights are not affected. You may not transfer it without our agreement.

Open as a page →Privacy Policy