People use the interface
Build the controls and feedback your workflow needs. The SDK connects the page to declared host methods and events.
auroraview.api.*
auroraview.on(...)AURORAVIEW / WEB UI + AGENT CONTRACTS
Web interfaces.
Native workflows.
Build DCC tools with a familiar web stack and AI coding assistants. Connect a useful human interface with explicitly registered agent capabilities.
Familiar web stackHTML, CSS, React, Vue, and your coding assistant
Explicit contractsDeclared calls, events, parameters, and results
DCC firstHost scene APIs, UI threads, and lifecycle
A familiar way to build.
Clear entry points for people and agents.
AuroraView brings modern web development into creative software. Start with frontend skills you already use, refine the interface with a coding agent, and connect declared capabilities to the native host. The goal is a complete DCC ecosystem where a person and an agent can work through the same tool capability.
Agent-friendly by design
Give the tool an explicit discovery and call contract: parameters, results, errors, and host scope. DCC-MCP registers declared capabilities; a UI does not automatically become an agent tool.
Start with familiar development skills
Use HTML, CSS, React, or Vue, then learn a small bridge contract for host calls and events. Runnable examples give developers and coding agents a concrete starting point.
Extend the parts your workflow needs
Compose browser-oriented APIs, extensions, plugins, and packaging around the interface. Keep feature availability and native integration explicit for each target.
Build a practical DCC ecosystem
Connect native UI entry points, host adapters, agent contracts, installation, and examples. The host matrix records scene readback, cleanup, and actual validation separately as this ecosystem grows.
A working foundation, with source you can inspect.
The main project contains the native core, Python package, frontend SDK, CLI, and Gallery app. It also contains browser APIs, an extension compatibility layer, and packing tools. Release assets include wheels, command-line tools, and Gallery builds.
Current source.
Shared contracts and host boundaries.
People use the web interface. Agents enter through an explicitly configured DCC-MCP adapter. Both rely on declared contracts; the native host keeps ownership of its lifecycle and scene API.
People and web interface
HTML / CSS / React / VuePresentation and direct interaction with the tool.
Declared entry points
TypeScript SDK / optional DCC-MCP registrationWeb calls and events; configured agent tools and session identity.
AuroraView core and APIs
Rust · IPC · Python / PyO3 · WebView backendsShared communication, window integration, and backend abstractions.
Optional browser and extension capabilities
Browser APIs · extension host · pluginsOptional capabilities remain separate from scene semantics and host lifecycle.
Native host adapter
Python + Qt / native engine integrationHost API calls, docking, UI-thread dispatch, focus, and shutdown.
One tool for people.
Explicit contracts for agents.
The aim is to make a useful tool available through both a clear interface and a deliberate agent entry point. The current DCC-MCP integration supplies a small, inspectable starting surface.
Agents use registered capabilities
Install the optional dcc-mcp-core dependency, configure AuroraViewAdapter, and start its server. FileRegistry registration makes that running session discoverable.
AuroraViewAdapter(view)
start_server(adapter).start()Current adapter tools
eval_jsscreenshotload_urlload_htmlSession context: window title, URL, PID, CDP port, and detected host. Scene-specific tools and context require additional host or Skill registration; they are not inferred automatically from the UI.
Source implementation describes the available contract. It is separate from a verified agent interaction in a particular host.
Inspect the DCC-MCP integration ↗
Beyond a single embedded panel.
- Browser-like APIs
The SDK exposes browser-oriented surfaces for tabs, windows, storage, runtime messages, and more. Available behavior depends on the backend and enabled features.
packages/auroraview-sdk/src ↗- Extensions and plugins
Dedicated crates manage extension lifecycle, manifests, messaging, and browser API compatibility. Treat compatibility as API-specific, not a promise that every Chrome extension runs unchanged.
crates/auroraview-extensions ↗- Pack and distribute
Packing separates frontend assets, Python services, and native application startup. Choose the deployment strategy for the target environment and validate the resulting artifact.
crates/auroraview-pack ↗
An ecosystem organized around the host.
Choose a host and inspect its native interface, DCC-MCP adapter, declared capabilities, installation, scene readback, cleanup, and actual verification. Completing these together across the ecosystem is the goal.
Host integrations in focus
Expand a host to inspect all seven responsibilities.
Autodesk MayaObserved within stated scope2026-10-09 partial receipt: f1231286 records real UI/MCP/scene/Undo and panel cleanup; 434822e3 covers CSS anchoring only; 96c98546 has controlled-test/source-CI evidence, with no new GUI session. Retained-owner reopen, CSS rename commit, full docking, DPI and remaining input are pending.
- AuroraView native UI / dock
- Preview / acceptance in progress
Partial Outliner GUI evidence at f1231286 shows Vue pixels in Maya 2026's native right dock. Float/redock, resize, native close, DPI and the remaining input matrix are pending.
- DCC-MCP host adapter
- Catalog reference
dcc-mcp-maya. Listed in the dated DCC-MCP snapshot; catalog installation listed. This does not establish AuroraView host support.
Source / installation reference ↗ - Shared capability / Agent contract
- Observed within stated scope
At f1231286, the Outliner UI and actual MCP calls shared declared scene tools using public facade 0.1.0 and Core 0.20.41. MCP rename events appeared in Vue; later lifecycle candidates need separate GUI acceptance.
- Runnable example / installation
- Preview / acceptance in progress
Merged Outliner bc934e7e consumes the public shared preview. Draft PR #53 at 49aa3ae8 documents OutlinerRuntime: attach once, reuse the owner across panel generations, and close at final host unload. GUI reopen remains pending.
Source / installation reference ↗ - Scene readback
- Observed within stated scope
The f1231286 GUI session verified UI/MCP rename, native scene readback and foreground Undo. The CSS-only 434822e3 follow-up verified row anchoring; rename commit at that revision was not accepted.
- Cleanup and ownership
- Observed within stated scope
At f1231286, panel close revoked stale UI calls, removed all 10 callbacks and the view, and kept the borrowed ToolSet/service alive. Retained-owner GUI reopen is pending; Core catalog retention blocks same-name owner replacement after final close.
- Actual verification
- Observed within stated scope
2026-10-09 partial receipt: f1231286 records real UI/MCP/scene/Undo and panel cleanup; 434822e3 covers CSS anchoring only; 96c98546 has controlled-test/source-CI evidence, with no new GUI session. Retained-owner reopen, CSS rename commit, full docking, DPI and remaining input are pending.
Source / installation reference ↗
BlenderObserved within stated scope2026-10-09: both 36/36 fixtures passed on Windows Blender 5.1.1 / Python 3.13.9; the tested tree matches merged revision 1401b6fe. Keyboard, Chinese IME, focus, multiple windows, foreground normal Stop, and user acceptance remain pending.
- AuroraView native UI / dock
- Preview / acceptance in progress
On 2026-10-09, Windows Blender 5.1.1 / Python 3.13.9 passed 36 native HTML/GPU lifecycle checks. Full keyboard, Chinese IME, focus, and multiple-window acceptance remain pending.
- DCC-MCP host adapter
- Catalog reference
dcc-mcp-blender. Listed in the dated DCC-MCP snapshot; catalog installation listed. This does not establish AuroraView host support.
Source / installation reference ↗ - Shared capability / Agent contract
- Observed within stated scope
The public shared Python preview passed 36 ToolSession → SDK → bpy checks on Blender 5.1.1. This establishes the recorded contract path, with full interactive acceptance still open.
- Runnable example / installation
- Preview / acceptance in progress
PR #5 is merged at 1401b6fe and main CI passed. The dated native-web guide documents installation and its limits; no public Blender release is recorded.
Source / installation reference ↗ - Scene readback
- Observed within stated scope
The Blender 5.1.1 shared ToolSession → SDK → bpy fixture passed 36 checks covering its scene contract. Broader interactive scenarios need separate state readback.
- Cleanup and ownership
- Observed within stated scope
The native HTML/GPU lifecycle fixture passed 36 checks. Foreground normal Stop, multiple-window behavior, and user acceptance remain open.
- Actual verification
- Observed within stated scope
2026-10-09: both 36/36 fixtures passed on Windows Blender 5.1.1 / Python 3.13.9; the tested tree matches merged revision 1401b6fe. Keyboard, Chinese IME, focus, multiple windows, foreground normal Stop, and user acceptance remain pending.
Source / installation reference ↗
Unreal EnginePreview / acceptance in progress2026-10-09 snapshot: 7f962b43 passed the Editor shared-tool probe and UE 5.7 Game Runtime CI. The separate refresh candidate, draft PR #8 a6d2e80, passed source CI; its native refresh and interaction acceptance are not established here. Shared-tool scene mutation/Undo, docking, pixels and input remain pending.
- AuroraView native UI / dock
- Acceptance pending
As of 2026-10-09, native dock, pixels, input, and window lifecycle acceptance remain pending. Main revision 03815487 and the open PR #7 candidate are separate baselines.
- DCC-MCP host adapter
- Catalog reference
dcc-mcp-unreal. Listed in the dated DCC-MCP snapshot; catalog installation listed. This does not establish AuroraView host support.
Source / installation reference ↗ - Shared capability / Agent contract
- Preview / acceptance in progress
PR #7 candidate 7f962b43 passed an actual UE 5.7.4 Editor shared ToolSet/SDK/Python/events probe. Reverse calls preserved successful return values false and 0. The receipt records shared version 0.1.0; public wheel provenance and Core consumption are unverified.
Source / installation reference ↗ - Runnable example / installation
- Preview / acceptance in progress
Main remains 03815487. Open PR #7 candidate 7f962b43 passed UE 5.7 native build, Cook/package and Game Runtime CI, with an offline demo retained as a CI artifact. This is separate from a release and Editor interaction acceptance.
Source / installation reference ↗ - Scene readback
- Acceptance pending
The recorded Editor probe made no scene mutation. Shared-tool mutation, scene readback, and Undo remain pending.
- Cleanup and ownership
- Preview / acceptance in progress
The PR #7 candidate passed its Editor client cleanup probe. Native window lifecycle and repeatable close/reopen still need acceptance.
- Actual verification
- Preview / acceptance in progress
2026-10-09 snapshot: 7f962b43 passed the Editor shared-tool probe and UE 5.7 Game Runtime CI. The separate refresh candidate, draft PR #8 a6d2e80, passed source CI; its native refresh and interaction acceptance are not established here. Shared-tool scene mutation/Undo, docking, pixels and input remain pending.
Source / installation reference ↗
Unity EditorObserved within stated scope2026-10-09: public preview 12210315 passed release readback and actual Editor MCP scene/readback, Undo and Stop checks. Separate Core consumer source is ea25683a; Core HTTP/pipe preparation uses controlled fixtures. Actual Editor Core and GUI are not_run; browser roundtrip, docking, input and DPI remain pending.
- AuroraView native UI / dock
- Preview / acceptance in progress
Windows x64 EditorWindow / child-HWND WebView2 source is public. Native WebView smoke passed; non-batch Editor GUI, docking, input, and high-DPI acceptance remain pending.
- DCC-MCP host adapter
- Catalog reference
dcc-mcp-unity. Listed in the dated DCC-MCP snapshot; catalog installation listed. This does not establish AuroraView host support.
Source / installation reference ↗ - Shared capability / Agent contract
- Observed within stated scope
Actual MCP stdio initialization, three registered tools, and current-user pipe calls into the Editor passed for the public preview. Draft PR #1 at ea25683a adds an external-Python Core 0.20.41 / shared wheel 0.1.0 consumer; actual Editor Core and GUI acceptance are not_run.
Source / installation reference ↗ - Runnable example / installation
- Preview / acceptance in progress
Public v0.1.0-preview.1 at source 12210315 provides the Windows Editor preview ZIP. Main/tag/release CI and public ZIP/SHA readback passed.
Source / installation reference ↗ - Scene readback
- Observed within stated scope
Seven Unity 2022.3 Editor tests passed. Actual MCP calls created and selected an object, read Editor state, and verified Undo. Browser-to-scene roundtrip acceptance remains pending.
- Cleanup and ownership
- Observed within stated scope
Native STA shutdown, current-user pipe access, exclusive ownership, and endpoint close/reopen checks passed; the actual MCP run verified endpoint Stop. Interactive docking and lifecycle acceptance remain open.
- Actual verification
- Observed within stated scope
2026-10-09: public preview 12210315 passed release readback and actual Editor MCP scene/readback, Undo and Stop checks. Separate Core consumer source is ea25683a; Core HTTP/pipe preparation uses controlled fixtures. Actual Editor Core and GUI are not_run; browser roundtrip, docking, input and DPI remain pending.
Source / installation reference ↗
SideFX HoudiniSource availableAdapter source is available; real-host interaction and cleanup are not assessed in this review.
- AuroraView native UI / dock
- Source available
Houdini host adapter source is available; native UI and docking need version-specific acceptance.
- DCC-MCP host adapter
- Catalog reference
dcc-mcp-houdini. Listed in the dated DCC-MCP snapshot; catalog installation listed. This does not establish AuroraView host support.
Source / installation reference ↗ - Shared capability / Agent contract
- Ecosystem target
Host-specific page calls, events, and explicit Agent tools remain integration work.
- Runnable example / installation
- Source available
Use the adapter repository for installation and host prerequisites; a runnable-host result is not recorded here.
- Scene readback
- Ecosystem target
No AuroraView scene-state readback is recorded here.
- Cleanup and ownership
- Ecosystem target
Owned and borrowed resource cleanup needs host-specific acceptance.
- Actual verification
- Source available
Adapter source is available; real-host interaction and cleanup are not assessed in this review.
Foundry NukeSource availableAdapter source is available; scene readback and lifecycle acceptance are not assessed in this review.
- AuroraView native UI / dock
- Source available
Nuke host adapter and dispatcher source are available; native UI acceptance is version-specific.
- DCC-MCP host adapter
- Catalog reference
dcc-mcp-nuke. Listed in the dated DCC-MCP snapshot; catalog installation listed. This does not establish AuroraView host support.
Source / installation reference ↗ - Shared capability / Agent contract
- Ecosystem target
Host-specific page calls, events, and explicit Agent tools remain integration work.
- Runnable example / installation
- Source available
Use the adapter repository for installation and dispatcher requirements; a current live-host example is not verified here.
- Scene readback
- Ecosystem target
No AuroraView scene-state readback is recorded here.
- Cleanup and ownership
- Ecosystem target
Owned and borrowed resource cleanup needs host-specific acceptance.
- Actual verification
- Source available
Adapter source is available; scene readback and lifecycle acceptance are not assessed in this review.
Shared foundation and teaching source
| Project | Responsibility | Current evidence |
|---|---|---|
| auroraview | Core, Python API, SDK, CLI, and Gallery | Source and published release assets |
| auroraview-maya-outliner | Independent Maya scene-tree teaching project | Refreshed tutorial merged; scene checks passed; UI acceptance pending |
Start outside the host.
Then bring your tool inside.
First load your frontend in a standalone window. Then select a host adapter, keep host operations behind its API, and validate the full lifecycle in your target application.
1 / Install the Python package
pip install auroraviewUse the Python environment for your intended host. Windows needs the WebView2 Runtime; Linux needs WebKitGTK system dependencies. Qt integration has its own host requirements.
Installation and platform prerequisites ↗2 / Load your local frontend
from auroraview import run_desktop
run_desktop(
title="My pipeline tool",
url="http://localhost:3000",
width=1024,
height=768,
)Learn from a real tool.
Keep small, runnable teaching projects alongside the host adapters. Each example should name its prerequisites, launch command, expected behavior, and validation limits.
Maya Outliner
A separate scene-tree example for Maya. The refreshed tutorial is merged with source archive and Maya 2026 scene checks; interactive WebView acceptance is pending.
Explore the teaching project ↗Core examples
Standalone windows, calls, events, and Qt integration patterns.
Browse examples ↗Gallery
Explore the existing demo app and the code behind its interface.
Open Gallery source ↗Building a host integration?
Keep the shared protocol small. Put host lifecycle and packaging in the adapter, and include a runnable example with explicit validation evidence.
Contribute on GitHub ↗