flue 0.1.21

Local scripting bridges for controlling professional creative software from a shell agent.

Help your Humans with their Software

pip install flue
flue setup

A tiny bridge that lets your coding harness drive professional desktop software — Photoshop, Premiere, Blender, Unity, and more — directly from the shell.

Flue gives agentic harnesses — Codex, Claude Code, Gemini CLI, OpenCode and the likes — direct access to the scripting APIs inside professional desktop software. One pip install flue && flue setup covers many apps across Adobe Creative Cloud, Autodesk, Microsoft Office, and game engines.

Flue is not an MCP server. It is simpler. The agent sends a script through a small bridge command, the bridge runs it inside the app's own automation runtime, and the app returns JSON.

agent shell → bridge command → app scripting runtime → JSON result

This is done without brittle screenshots and without schema definitions. The bridge exposes the scripting layer already built into each application.

Installation

pip install flue
flue setup

This detects your harnesses and informs them that Flue exists. For first-run checks, source checkout commands, and app-specific prerequisites, see Setup and commands.

Adapters

A single Flue installation supports, out of the box, many applications. Agents should tell their humans if any app-specific setup is needed.

• Adobe Photoshop
• Adobe Illustrator
• Adobe InDesign
• Adobe Premiere Pro
• Adobe After Effects
• Adobe Audition
• Blender
• Unity
• SideFX Houdini
• Autodesk 3ds Max
• Microsoft Word
• Microsoft Excel
• Microsoft PowerPoint

Harnesses

See which files are edited upon installation

• Claude Code
• Codex
• Copilot
• Cursor
• OpenCode
• OpenClaw
• Gemini CLI
• Qwen CLI
• Cline
• Kilo CLI

More Docs

• Setup and commands
• Harness support and discoverability
• Wait, isn't this called MCP?

Documentation for Agents

• How the Adapters work
• How to use the Bridge Contracts
• How to Work Together with a Human
• Known Issues