Venxuix DCCIDE, pronounced "decide," is a Windows workspace that brings the applications creators already use into one living VNX Workspace — hosting, connecting and orchestrating them rather than replacing them.
The real DCC and IDE applications — 3D suites, game engines, video editors, code editors — run side by side, each in a customizable smart tab. Nothing is emulated and nothing is a viewer: the actual software runs at native speed inside one window.
Every tab connects to the VNX Canvas — a single shared canvas rendered in two perspectives. The 2D perspective is an infinite plane of live application cards, previewed and arranged before full-screening; it is also a diagramming surface where screenshots, text and clipboard content are annotated and connected beside the running tools. The 3D perspective renders the same canvas — identical content, no duplication — as dimensional space: two viewpoints, one canvas. It is additionally a launch surface for agentic orchestrations, VNX plugins and applications. Workspaces park and mount like physical places, and whole multi-app pipelines save as VNX Canvas Workflow Projects that reopen exactly as they were left, in one action.
One keyboard share-splits across every tool with automatic focus arbitration: the workspace elects a single keyboard owner at a time, so typing never lands in the wrong application.
Agents don't visit this workspace — they live in it. A VNX orchestrative agency is a team of specialized agents built against a surface — watchers that see, operators that act, verifiers that prove. The VNX Canvas team makes the workspace self-modifiable — the user, artist or dev decides — and any workflow they run is a surface a custom team can be raised against, shaped by watching and listening to that person's instructions. The agency reaches two worlds and makes them feel like one: web orchestrations call public HTTPS domains and REST APIs from inside the VNX Canvas, while on the desktop side Venxuix builds the shell around each retargeted native tool — MCPs, exposed APIs, native surfaces — with a custom home UI for how they are triggered and stored. One agency; many harnesses; any surface.
The portable extension shell — Venxuix-authored addons for the software it retargets. One extension panel is defined once and mounted twice: inside the Venxuix workspace and natively inside the host application — Blender, Unreal Engine, Autodesk Maya, Houdini, and other DCC applications — the same panel UI in both places, speaking over one command channel, so exact commands, logic and data move between the workspace and the host software. The addon stops being something you operate inside one program's UI and becomes a payload Venxuix carries — built only on the extension surfaces each vendor purchases/publish inside software the user has already purchased or licensed (BYOL). XUIX (Xtended User Interface Xperience) is its face in the workspace, and Agent Xtension is its scholar: an agent that studies each host software's installed addons and writes per-addon analysis and usage knowledge, rendered as a navigable diagram graph — Analysis, the usage-RAG harness, and Xtension Blueprint views — so the user and the agents know what every extension can do before it is driven.
The harness's ground-truth channel: a live line into the running workspace through which an agent reads real state, executes operations, and verifies that what it changed actually changed. The eval socket is open by design — any LLM model, from any IDE, can connect to it and test the code it just wired, and an orchestration of agents can verify that work against the running workspace. Iteration is inlined the same way: asking for further customization is part of the loop itself, so the workspace keeps reshaping toward how the user Dccides.
With the additional probes package, the user starts from a fully customizable OS-managing system — and that is only the base. On top of it, Venxuix integrates the Autonomous Graph Engineer, Eval, the Multi-Purpose DCC/IDE Team Orchestra, and the Xtended User Interface — where the same panel UI that controls the OS is the panel you can portably carry into the various DCC softwares.
Stream the screen directly to an LLM of your choice (BYOK — bring your own key) — and not only one screen: one live session, one stream per monitor, every stream time-aligned into the same take. Monitor count is a configuration decision, not an architectural limit. The orchestration watches through the eval channel, sees the UI pixel by pixel, and lets the model visually self-evaluate the code it probes, wires, stages or researches against what is actually on screen.
Speak, and the workspace listens. Spoken commands are carried out, and everything said while working is transcribed as it is spoken — words separated from audio and time-aligned interval by interval, so a reading LLM knows exactly when in the work each thing was said. An optional agentic layer distills intent and surfaces related concerns in real time.
Draw and annotate over any running application — the markup lives above the tools. Like the voice, every stroke belongs to the moment it was made: ink is a recorded stream of the session.
Screen, voice and ink converge into one living take: frames, text renderings and transcripts an agent can read and act on — instructions, evidence, or a work order, revisitable at any moment rather than only replayed start to end.
Venxuix Dccide is planned for release under an LGPL license at its core, within a multi-split licensing architecture: one product licensed lane by lane, combining MIT, GPL, LGPL and proprietary components by design. Its integration method is likewise split by design, and the split is the legal architecture. Inside each application, Venxuix uses only the extension surfaces the application's own vendor natively publishes for exactly this purpose — scripting and code editors, plugins, published APIs, and MCPs — used as released, in the manner they are offered. Around each application sits everything else: the orchestration that launches, arranges, triggers and coordinates those surfaces operates outside the application, in the workspace that surrounds it — external by design, not externally within the Licensed software but externally around the software. Venxuix does not decide — the standard prohibitions of software license agreements are treated as the boundaries of its design: it does not reverse engineer, decompile, or disassemble hosted applications; does not modify, patch, or inject code into their binaries or memory; does not circumvent license enforcement, activation, or technical protection measures; does not redistribute, sublicense, or bundle any hosted application; does not remove or obscure proprietary notices; and does not access interfaces a vendor has not published. Every hosted application is installed and licensed by the ( User/ Artist/ Dev ) directly under that vendor's own terms, which remain in full effect at all times. Venxuix builds around licensings, never inside them — and the entitlement model is uniform by design: BYOK — bring your own key — governs the LLM models; BYOL — bring your own license — governs the software. Venxuix supplies the workspace, never the entitlements: every LLM key belongs to the ( User/ Artist/Dev ), and every retargeted application arrives under a license they already own. VNX Retargeting begins only where a valid license already exists — the license is the key that unlocks what Venxuix Decides.
Venxuix replaces nothing. It connects everything you create with.