[ FTC · AI-first autonomous · free to use ]

Weave — the AI autonomous code assistant for FTC

Correct FTC code on the first try.

The AI knows your whole robot — every motor, servo and sensor from your imported config — and your team's modular scripts. Describe the routine and ship a compilable Pedro Pathing OpMode that calls your real code.

Toolkit

From full hardware context to working OpMode — AI in every step.

Built for the way FTC teams actually work: fast iteration during build season, on the field, minutes before a match.

AI-first, always

A Claude-powered copilot writes the OpMode with you. Describe the routine in plain English and it wires motors, servos, sensors, and your scripts into compilable code.

Modular scripts that call each other

Save routines with declared return types and documented meanings — runIntake returns false when it’s empty — and generated code makes real calls and branches on the results.

One-click config import

Scan your Control Hub over USB and pull in the exact motor, servo, and sensor names from your hardware map — no more guessing string keys. One global config per robot, shared by every project.

Version-safe generation

Every OpMode targets the current Pedro Pathing 2.x API and ships with the Gradle install steps in its header. No deprecated calls, no mismatched imports.

Codegen

Describe the routine. Get a copy-paste-ready OpMode.

Every generation is a complete, compilable Java file — standard package, standard imports, registered as an OpMode, calling your scripts and branching on their return values. Paste it into your TeamCode module, build, and push to the hub. Nothing else required.

weave — autonomous-studiogenerating
AutoRoutine.java
RobotConfig.json
README.md
1 
2 
3 
4 
5 
6 
7 
8 
9 
10 
11 
12 
13 
14 
15 

Integration

Built for Pedro Pathing.

One path library, done properly. Every OpMode Weave generates targets the current public Pedro Pathing API and drops straight into your TeamCode folder — with the install steps written into the top of the file.

Pedro Pathing

current 2.x quickstart

Follower-based paths

BezierLine and BezierCurve chains built through follower.pathBuilder(), with per-segment heading interpolation.

Your scripts, wired in

Checked-in scripts are called as real classes in your teamcode package, with control flow built on their documented return values — follower.update() kept running throughout.

Current 2.x API only

com.pedropathing.geometry poses, PathChain, Constants.createFollower(hardwareMap) — no deprecated 1.x calls, no mismatched imports.

pedropathing.com

Pedro Pathing is an independent open-source project — Weave is not affiliated with it.

Control Hub

Your real robot config, imported in one scan.

Plug your Control Hub in over USB and the Weave agent reads the hardware map straight off the hub — every motor, servo, and sensor by its exact configured name. Generated code binds to your device names, so it runs without a single string edit.

  • One small local agent — nothing to install on the robot
  • Works with the standard FTC Robot Controller config
  • Assistant and codegen both use the imported names

Import Robot Config

Control Hub · via local agent

connected
  • leftFrontDcMotorEx · GoBILDA 5203
  • liftMotorDcMotorEx · encoder
  • clawServoServo · port 0
  • colorSensorREV Color Sensor V3

11 devices imported · hardware map synced

Recently shipped

Small details that make it feel like your tool.

Live code streaming

Watch the OpMode write itself token by token in a real syntax-highlighted editor — every chat instruction regenerates the file in front of you.

Scripts with return contracts

Every script declares its return type and what each value means — “false = no more balls” — so other scripts and autos can call it and branch on the result, in real compiled Java.

One config, every project

Import your robot once — motors, servos, sensors, cameras, odometry, dimensions — and select it into any project. Switch between Comp Bot and Practice Bot with one dropdown.

Grouped constants

Drivetrain constants, arm positions, PID values — grouped on your account, checked into a project’s context with one click, and declared as Java fields in the generated file.

Trusted by FTC teams

Officially trusted by the following teams

Real teams shipping real autonomous code with Weave. Tap any team to see their FIRST Tech Challenge profile.