1// avoid Pillar → score at Goal2Trajectory auto =3 drive.trajectoryBuilder(A)4 .splineTo(B, toRadians(90))5 .splineTo(C, toRadians(0)) // → Goal6 .build();waiting for the field…
Toolkit
From field sketch 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 paths, motors, servos, and sensors into compilable code.
Context-aware field editing
Field layouts, obstacle and terrain descriptions, barriers, and every path you draw are fed straight into AI generation — so the code understands your field, not just coordinates.
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.
Version-safe generation
Target RoadRunner 1.0 or Pedro Pathing and get idiomatic, compilable Java. No deprecated APIs, no mismatched imports.
Codegen
Draw the path. Get a copy-paste-ready OpMode.
Every generation is a complete, compilable Java file — standard package, standard imports, registered as an OpMode. Paste it into your TeamCode module, build, and push to the hub. Nothing else required.
1
Integrations
Integrated with both major path libraries.
Pick your library per project and switch any time — each framework keeps its own generated file, and both target the current public API. No deprecated calls, no mismatched imports.
RoadRunner
1.0
Trajectory building on the actionBuilder API — strafeTo segments, velocity constraints, and markers wired to your real hardware names.
fully supported
Pedro Pathing
current quickstart
Follower-based paths with BezierLine chains, PathChain callbacks, and the same live zone reactions — generated to the current public API.
fully supported
RoadRunner and Pedro Pathing are independent open-source projects — Weave is not affiliated with either.
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
- 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.
Your script library
Save labeled Java routines — “run the intake”, “spin up the launcher” — to your account once, then reference them by name in any project. The assistant splices your real code in.
Custom mascot marker
Upload your team mascot and it becomes the robot marker in the path preview — scaled to your robot’s true footprint and rotating with its heading.
Per-framework files
RoadRunner and Pedro Pathing outputs live side by side. Switching frameworks never silently overwrites work — you choose to save or discard, every time.
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.