polyphase-controller

Automates scene authoring via REST calls to the Polyphase editor's scene, nodes, and play endpoints.

49|2|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/Polyphase-Labs/Polyphase-Engine --skill polyphase-controller
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: polyphase-controller
Source: https://github.com/Polyphase-Labs/Polyphase-Engine/tree/main/.claude/skills/polyphase-controller
Command: npx skills add https://github.com/Polyphase-Labs/Polyphase-Engine --skill polyphase-controller

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Drive the running Polyphase editor over its REST controller server to author or modify scenes while the editor is open. This enables creating scenes, spawning nodes, setting transforms and properties, attaching Lua scripts, populating script-exposed fields, and controlling play-in-editor. It responds to requests such as spawn actions, adding lights, attaching scripts, or building a level.

Core Features & Use Cases

  • Automate scene authoring by issuing REST calls to the editor's scene, nodes, and play endpoints.
  • Script end-to-end workflows: create scenes, spawn and configure nodes, attach Lua scripts, fill script properties, and drive play-in-editor without UI interaction.
  • Use when you need repeatable, programmatic scene construction or batch edits from external tools.

Quick Start

Start the Polyphase editor, enable the Controller Server, then issue REST calls to create a scene, spawn nodes, attach scripts, and start play-in-editor.

Frequently Asked Questions about polyphase-controller

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate scene authoring in the Polyphase editor without UI interaction?

You can automate scene authoring by driving the running Polyphase editor through its REST controller server, issuing HTTP requests to create scenes, spawn nodes, and attach Lua scripts without UI interaction.

What do I need to set up before using REST calls to control the Polyphase editor?

You need the Polyphase editor running with the controller server enabled on port 7890. Once active, the server exposes REST routes for queueing scene creation, node spawning, and play-in-editor execution on the main thread.

Can I attach Lua scripts and populate script-exposed fields via the Polyphase REST API?

Yes, the Polyphase REST API supports attaching Lua scripts to nodes and populating their script-exposed fields. This allows programmatic configuration of node behavior alongside transforms and properties.

How do I start play-in-editor programmatically using the Polyphase controller?

You start play-in-editor programmatically by sending a REST request to the /api/play endpoint exposed by the Polyphase controller server, which queues the action for execution on the editor's main thread.

What is the best way to perform repeatable batch edits on Polyphase scenes from external tools?

The best way to perform repeatable batch edits is using the Polyphase REST controller server, which accepts external HTTP requests to programmatically construct scenes, spawn nodes, and apply batch modifications.

Are there limitations to controlling the Polyphase editor through its REST API?

The REST API relies on a queue-on-main-thread execution model, meaning requests are queued and processed sequentially by the running editor, requiring the editor to remain open with the controller server actively listening on port 7890.