Open source · Apache 2.0 · Xbox Developer Mode
XCP is an open source development platform for indie developers, creators and tool builders. Create prototypes, adapt supported project behaviour and iterate on real Xbox hardware in Developer Mode, using Windows tools with or without an AI agent.
The quick overview
From development tools and AI-assisted workflows to playable prototypes on Xbox Developer Mode. This short animation introduces the idea, the workflow, and the boundaries of XCP.
XCP Studio
Work on an idea or an existing project, prepare a supported Xbox prototype, inspect the result and keep improving it. Guided, Expert and agent workflows share the same project throughout.
One authoritative project. Three interfaces onto it.
What has been built
Procedural prototypes and adaptations of existing games show two ways to work with XCP. These recorded Xbox runs demonstrate specific experiences and give contributors concrete starting points.
Create
Forge uses WorldLoop's procedural generation on the PC to prepare material for Xbox execution. Core Siege is an early interactive prototype from that creative programme, built with a human-directed AI workflow.
WorldLoop supplies procedural generation; Xbox executes the prepared result. XCP brings creation, observation and iteration into one project lifecycle.
Adapt
XCP observed an existing Godot project, derived its structure and semantics, and produced an ordinary XCP project that completed the Xbox lifecycle.
Adapted from authorized Godot 2 source; completed the Xbox lifecycle as a playable behavioural subset with declared degradation. Full source equivalence is not claimed. Minilens is the work of its authors, used under GPL-3.0-or-later.
More recorded adaptation cases: Blokki, Minedot and Open RTS also reached bounded playable reconstruction on Xbox with physical-controller checks. Each result includes declared substitutions and applies to its measured scenario; full source equivalence is not claimed. Read the three-project results.
Whether created or adapted, an XCP project can continue to evolve across new source revisions and local decisions. See how evolution works.
The lifecycle
AI builds. Xbox executes. XCP verifies. The same project continues through validation, execution, observation, correction, versioning and rollback, so each experiment can inform the next iteration.
The loop closes. What the console reports becomes the input to the next correction, and the correction is machine-readable, so an agent can act on it without a human translating a stack trace first.
Proof
XCP does not treat evidence as documentation written after the run. The lifecycle produces the evidence while the work is executed.
Where the work happens
The AI plans, creates and corrects from the PC side. Project files, adaptation, semantic diff and build all happen here, where they can be inspected and re-run.
Xbox executes bounded, validated artifacts through the measured XCP runtime. No model-provider credentials are stored on the console.
A model provider may be remote. The project lifecycle and the Xbox execution are local; the AI itself is not necessarily local, and this page does not claim otherwise.
Build with XCP
Bring an idea, an existing project or a tool you want to connect. Explore the portable core, build Studio on Windows, or try the development stack on your own Xbox. Proposals, examples and new approaches are welcome alongside verification work.
Explore XVM, project contracts, conformance vectors and the Python test suite without an Xbox.
Start with the repositoryBuild the Windows development stack from source and explore project creation, source adaptation and iteration in one workspace.
Read the build guideTest newly built development packages on an owned console in Developer Mode and report a new, separately identified result.
Follow the device protocolFirst run / no Xbox required
With a supported Python development environment, you can run the portable tests and conformance suite, then verify and execute a bundled XVM vector.
Expected: the tests and conformance suite pass; the bundled vector verifies and runs locally. This is a PC-side check, not an Xbox hardware result.
Read the full quick startgit clone https://github.com/Daniele-Cangi/xcp-xbox.git
cd xcp-xbox
python -m pip install -e '.[test]'
python -m pytest -q
xcp conformance all
xcp xvm verify src/xcp/conformance/vectors/xvm-v2-call-chain.json
xcp xvm run src/xcp/conformance/vectors/xvm-v2-call-chain.jsonHelp extend adapters, developer tools, runtimes and agent integrations, or propose a new direction. The goal is to connect more frameworks, engines and execution targets over time. New development packages remain NOT_TESTED_ON_XBOX until independently reproduced.
Build an example, improve a tool, propose an adapter or explore a new workflow. Help make Xbox development more accessible to other developers through an open platform whose results can be inspected and reproduced.