> fusionctl: a Bun CLI that drives a running Autodesk Fusion session through the FusionBridge
> add-in (127.0.0.1:18765, token in ~/.config/fusionctl/token). Install with
> `bun install -g github:pieralukasz/fusionctl`, then `fusionctl install`, restart Fusion, `fusionctl doctor`.
> Rules for coding agents: https://fusionctl.lucaspiera.com/docs/agents
> (raw: https://github.com/pieralukasz/fusionctl/blob/main/AGENTS.md).
> All docs in one file: https://fusionctl.lucaspiera.com/llms-full.txt

# fusionctl

- [Introduction](/docs): fusionctl drives a running Autodesk Fusion session from the terminal, for people who prefer a shell and for coding agents that need to check their own geometry.
- [Installation](/docs/installation): Install the CLI with Bun, copy the FusionBridge add-in into Fusion, restart Fusion and check the setup with fusionctl doctor.
- [Quickstart](/docs/quickstart): Build the example L-bracket in a running Fusion, read it back as numbers, change one parameter and export it. Every output on this page is a real transcript.
- [For agents](/docs/agents): How a coding agent (Claude Code, Codex, OpenCode) should use fusionctl, the rules in AGENTS.md, and the plain-text versions of these docs.

- **Reference**
- [Commands](/docs/commands): Every fusionctl command with its usage line, what it prints and the options it takes. Usage lines are copied from fusionctl <command> --help.
- [Scripting in Fusion](/docs/scripting): The globals a fusionctl script gets, the API's centimetres, which way each sketch plane points, user parameters, and recipes taken from examples/bracket.py.
- [Verifying a part](/docs/verifying): A script that ran without an exception is not proof that the geometry is right. Check the timeline, the bodies, interference and screenshots after every step, and print a test piece.
- [Assemblies and joints](/docs/assemblies): Components, rigid and revolute joints, driving a joint, and interference and clearance checks, with the code of the recorded wristwatch in examples/watch.

- **Background**
- [How it works & security](/docs/how-it-works): The CLI sends one HTTP request per command to the FusionBridge add-in on 127.0.0.1, with a token. The add-in runs it on Fusion's main thread. exec runs arbitrary Python as your user.
- [fusionctl and MCP](/docs/mcp): How fusionctl compares with Autodesk's Fusion MCP Server and community MCP servers, when each is the better choice, and how to use both.
- [Troubleshooting](/docs/troubleshooting): What fusionctl doctor checks, and what to do about each error message, from a missing or outdated add-in, an unreachable bridge, a token mismatch, a modal dialog.