Any model. Same shortcuts. Slash commands are in Flux

Lena is a hardware engineer at a robotics startup. She spends her mornings in a coding agent, and her hands know the shortcuts. / opens the commands, and the agent does the rest.

In the afternoon she opens the arm controller in Flux. It is a motor-driver board inside a machined aluminum housing. She asks the Flux agent to route the board, and the agent starts. Halfway through, the mechanical lead sends her a message: "Do the new connectors still clear the housing lid?"

Before, she had two bad choices. She could wait for the routing job to finish, or she could ask in the same chat and pull the agent off its job.

Now she types /aside do the J3 and J4 connectors clear the lid? The answer comes back in a small card above the chat box. It is read-only and based on the project. The routing job continues. She closes the card and replies to her lead.

Then she types /agent and asks it to check the board before she orders it. The whole afternoon took a few hours.

Your shortcuts, in Flux

Engineers already use AI agents every day, and those agents taught us a pattern: type / and the tool shows you what it can do. Flux now does the same. Type / at the start of the chat box and a short list opens. Keep typing to filter it. Use the arrow keys to move and Enter to run.

Every model, one set of commands

Flux is model-agnostic. It uses models from labs such as OpenAI, Anthropic, and Google, plus specialized models and engines built for hardware work. With Adaptive, the Flux agent plans the job and gives each task to the model that does it best for the price.

Coding agents usually tie their shortcuts to one model family. In Flux, the shortcuts belong to you. Change the model with /model, and /aside, /stop and /new work the same as before. Your habits move with you, whichever model is best this month.

One team, many shortcuts

• The mechanical engineer. While the agent rebuilds the enclosure with thicker screw bosses, she types /aside what wall thickness is left around the USB-C cutout? She gets the answer at once, and the agent keeps going.
• The hardware lead. He types /chat to plan the next revision with the agent, then /agent to make the changes. Chat is free.
• The firmware engineer. She uses /attach to add the driver datasheet, and the agent wires the fault output to the right pin.
• The whole team. /mcp connects the tools the team already uses, so the agent can read their requirements and tickets.
• A new product. /new starts a clean conversation for the next device. /agent then turns a one-paragraph brief into a board and its enclosure in hours, not weeks.

Prompts to try

• /aside does the battery fit under the board with 2 mm of clearance?
• /aside which regulator feeds the motor drivers?
• Type /chat, then ask: what changes would cut the BOM cost by 10%?
• /attach
• /model

Type / in Flux and try it today.