Claude Code to Flux

Bring your hardware work from Claude Code to Flux and continue it here. Flux is an AI hardware engineer. It uses the same frontier models, including Claude models from Anthropic, with the schematic and PCB editors, mechanical CAD, parts, simulation, and manufacturing built into one project.

In Claude Code, you connect outside design tools with scripts, and each engineer runs a separate agent. In Flux, the hardware tools are part of the project, and your engineers and Flux work in the same live project in the browser.

Import your design files into Flux

Your repository can contain board files, 3D models, and firmware source. Attach the files, a folder, or a ZIP file of the repository to a message in the Chat panel, and ask Flux to import them. Flux finds the formats and creates the new project or parts.

Import this ZIP of my hardware repository. Create a project from the KiCad files and add the STEP models to it.

Import the attached KiCad schematic and board, then design an enclosure and firmware for the board.

Import the attached symbol and footprint library with its STEP models.

Import electronics projects

To do it in the UI:

Select Flux menu → Import → Project… under the Electronics heading.
In the Import Project to dialog, select your account or an organization in the dialog title.
Select Choose Files or Choose Folder, or drop the files, a folder, or a ZIP file into the dialog. For a KiCad project, upload the .kicad_pro, .kicad_sch, and .kicad_pcb files together, or the whole project folder.
Select the projects to import, then start the import. Each import creates a new project.

Flux imports projects from KiCad, Altium Designer, Eagle, EasyEDA, OrCAD and Allegro, PADS, and other tools. See Import designs and files for all formats.

Import mechanical models

Attach the STEP, STL, or OpenSCAD files that your scripts made, and ask Flux to add them to the project.

Add the attached enclosure STEP file to this project and place the board inside it.

Add the attached OpenSCAD bracket and make it 2 mm thicker.

To do it in the UI:

In the Inspector, open Assets, select Manage Assets, then select Add Item.
Upload the .step, .stp, .iges, .brep, .stl, .obj, .3mf, .glb, or .scad file.

For native SOLIDWORKS, Parasolid, Fusion, and OpenUSD files, select Flux menu → Import → 3D Part or Assembly… under the Mechanical heading. See Import and edit CAD files.

Bring your firmware source

Share a public Git repository link, upload a ZIP of the source, or paste the files into the chat. Ask Flux to read the code structure before you ask for a change.

Use the firmware in this public repository. Map its sensor driver to the I2C pins in this schematic.

Continue from the source in this ZIP. Add a status LED and document its pin assignment.

Flux keeps the source in the project files. Select Files in the project view switcher to read it. See Write firmware.

Move your CLAUDE.md rules to Knowledge

Your CLAUDE.md files hold the rules that Claude Code follows in a repository. In Flux, these rules go into Knowledge. Flux applies them each time it works on the project. Paste the hardware rules from your CLAUDE.md file into the chat, and ask Flux to save them.

Add these rules from my CLAUDE.md file to this project's knowledge: use 0402 passives, keep the USB-C connector on the front edge, and prefix signal nets with SIG_.

Remember for all my projects: use M3 stainless steel screws for enclosure mounts and JST connectors for battery inputs.

To review the entries in the UI, select Add tab in the editor view switcher, then select Knowledge. See Team and project knowledge.

Keep Claude Code connected to Flux

You can keep Claude Code for your software work. Connect it to the Flux MCP server. Claude Code can then read your Flux projects and hand design work to Flux.

Add the Flux server from a terminal:
claude mcp add -t http flux https://app.flux.ai/mcp
Run /mcp in Claude Code.
Complete the Flux sign-in in your browser.

Then ask Claude Code to work with Flux:

Open my Flux project for the air-quality monitor. List the pins and nets of the microcontroller so I can update the firmware pin map.

Ask Flux to add a low-battery indicator to the schematic of my sensor board, then read the updated project.

See Use Flux in your AI tools.

What you can do with your design in Flux

After the import, your design is a Flux project. Ask Flux to work on it. Flux works on the electronics, the mechanical parts, the firmware, and the manufacturing in the same project.

Turn the imported project into a complete device

Ask Flux to add what the device needs. An imported board gets an enclosure and firmware. An imported mechanical model gets a PCB that fits it, and firmware for that board.

Using the imported board, design an enclosure that fits its outline and aligns with its mounting holes and connectors.

Write firmware for the microcontroller in the imported schematic. Use its pin assignments to initialize the connected peripherals.

Using the imported STEP assembly as the fit reference, design a PCB that fits inside it and aligns with its mounting points.

Ask Flux to design the missing mechanical parts or the missing board. Use the outline, the mounting holes, and the connectors of the imported design.
Ask Flux to write firmware for the microcontroller and the peripherals in the schematic.
If the device has off-board sensors or actuators, ask Flux to design a wire harness between them and the board. See Design wire harnesses.

Design the schematic and the PCB

Ask Flux for the requirements, the parts, the schematic, and the PCB layout. Flux selects parts from a library with live stock and pricing from distributors. Flux places and routes the board in the PCB editor.

Design a 3.3 V buck converter from a 12 V input for this board. Select parts that are in stock.

Place the components and route the board on 4 layers.

Review the schematic and check each IC against its datasheet.

See Route with Flux.

Design mechanical parts and assemblies

Ask Flux for enclosures, brackets, mounts, mechanisms, and complete assemblies. Flux builds them around the 3D models of your boards and parts. Each part has editable CAD code that you and Flux can change.

Design a wall mount for the enclosure with two keyhole slots.

Make the case 8 mm longer and move the USB-C opening with the board.

Build a pan-tilt camera mount with two servos and place the board in the base.

See Mechanical Design and Editable CAD Code.

Build and test the firmware

Ask Flux to build the firmware, run host unit tests, and report the memory footprint.

Build this project's firmware and report the image files and memory footprint.

Add a unit test for the sensor conversion and report the test result and coverage.

See Build and test firmware.

Simulate and check the design

Ask Flux to simulate circuits, check the board temperature, and analyze the stress, the heat, and the air flow of the mechanical parts.

Simulate the startup of the buck converter and plot the output voltage.

Simulate the air flow through the enclosure vents with 3 W from the regulator.

See Simulation.

Work on several tasks at the same time

Ask Flux to run separate workstreams in parallel, for example the main board, a daughterboard, and the enclosure. Each workstream has its own thread.

Design the main board, the display board, and the enclosure in parallel. Keep the board outlines and connector positions aligned.

To follow the threads, select Show All Threads in the Chat panel. See Parallel threads.

Choose the model

Flux uses frontier models from OpenAI, Anthropic, and Google. Choose Adaptive to let Flux select a model for each step, or choose a Claude model from the list.

Open the chat composer.
Select the model control, or type /model.
Select Adaptive, Max, Lite, or a model from the list.

See Model selection.

Get quotes and order

Ask Flux for the fabrication files, PCB quotes and orders, and quotes for 3D-printed and sheet-metal parts.

Get quotes for 10 assembled boards.

Get 3D-printing quotes for the enclosure in PETG.

See Manufacturing.

Claude Code concepts in Flux

In Claude Code	In Flux
Prompts in the terminal or code editor	Prompts in the Chat panel of the project, in the browser.
Scripts that drive outside design tools	The schematic and PCB editors, mechanical CAD, parts, and simulation in the project.
`CLAUDE.md` files	Knowledge for you, a project, or your organization.
Subagents and agent teams	Parallel threads for separate workstreams.
Repository files	The project design, its assets, and its project files.
Git commits and history	Change History. Flux saves each change.
MCP servers	AI Integrations in the chat composer. See Integrations and secrets.
`/model`	`/model` in the chat composer. See Model selection.
One agent for each engineer	One live project that your engineers and Flux work in at the same time.

Last updated on

Was this page helpful?