XCP

Open source · Apache 2.0 · Xbox Developer Mode

AI builds. Xbox executes.XCP verifies.

XCP is now open source. Explore the Windows-to-Xbox development stack, reproduce its portable workflows, and help turn measured results into independently verified execution on Xbox Developer Mode.

Explore the source on GitHub How to contribute

Build with XCP

The source is open. The next proof is shared.

Start with the portable toolchain, reproduce the Windows development build, or test a new package on your own Xbox Series X in Developer Mode. Each path has a documented entry point.

01 / ANY DEVELOPMENT MACHINE

Run the portable core

Explore XVM, project contracts, conformance vectors and the Python test suite without an Xbox.

Start with the repository
02 / WINDOWS

Rebuild the development stack

Build Studio, the worker and supporting components from source; compare the produced distribution with its verification manifests.

Read the build guide
03 / XBOX SERIES X

Reproduce on hardware

Test newly built development packages on an owned console in Developer Mode and report a new, separately identified result.

Follow the device protocol

First run / no Xbox required

Try XCP on your computer.

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 start 
git 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.json

The historical Xbox result is recorded. New development packages remain NOT_TESTED_ON_XBOX until independently reproduced.

Read the contribution guide

XCP Studio

From an idea to real execution — in one workspace.

XCP Studio brings creation, source adaptation, project evolution, Xbox playtesting and structured evidence into one coherent development environment.

XCP Studio project library and guided workspace operating on one authoritative project.
One project authority across Guided, Expert and agent workflows. Click to enlarge
  • Guided Visual tools over the declared project contract
  • Expert Detailed access to the authoritative project
  • Agent External AI through the same portable toolchain
Authoritative project One authority · integrity-checked on save

One authoritative project. Three interfaces onto it.

Explore XCP Studio

The lifecycle

Generation was only the first step.

Most AI coding tools stop when the files are written. XCP continues through validation, execution, observation, correction, versioning and rollback on real hardware.

  1. 01Idea or repository
  2. 02AI agent + XCP Studio
  3. 03Editable XCP project
  4. 04Deterministic build
  5. 05Real Xbox execution
  6. 06Observation + evidence
  7. 07Correct · adapt · evolve

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 of the platform

Two ways in. One verified lifecycle.

Software can start as an idea or as an existing codebase. Either way it becomes an ordinary XCP project, and every project takes the same path from there.

  • IdeaCreateXbox execution
  • SourceAdaptXbox execution

Create

Created from an idea

An AI-driven, human-directed workflow created an interactive arena shooter from zero and brought it to real execution on Xbox.

Core Siege, an arena defense shooter built through an AI-driven workflow, running on Xbox.
Core Siege — an early AI-driven Xbox prototype.

Core Siege was an early AI-driven Xbox prototype. XCP now turns that creation path into a repeatable, observable and verifiable lifecycle.

Adapt

Adapted from real source

XCP observed an existing Godot project, derived its structure and semantics, and produced an ordinary XCP project that completed the Xbox lifecycle.

Minilens adapted from Godot 2 source and executed through the XCP Xbox lifecycle.
Minilens v1.2 — adapted from authorized Godot 2 source and executed through XCP.

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.

Whether created or adapted, an XCP project can continue to evolve across new source revisions and local decisions. See how evolution works.

Proof

Measured, not implied.

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

Reasoning on the PC.
Deterministic execution on Xbox.

PC side Studio · agent · toolchain

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 side Creative host · worker

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.

Open source development

Help make the next run independently verifiable.

Explore the source, pick a reproducible task and bring back evidence from the machine where it ran.

Contribute on GitHub Read the architecture