DevGame

DevGame is a fork of T3 Code, built by T3 Tools, Inc. and MIT-licensed.
Almost everything that makes this application work was written by them — the agent harness, the terminal, checkpointing, source control, device pairing, and all four client apps. We specialised it for game development; we did not build it. Full credit, and what we actually added, in ATTRIBUTION.md.
If you want the general-purpose agent harness rather than the game-dev one, use T3 Code — it is the better tool for that job and it is where this came from.

T3 Code (below) is an "agent harness control surface". It enables control of the agents on your machine with a best-in-class mobile app (iOS, Android), web app and Electron-based desktop app. Those store listings and hosted apps are T3 Code's, not DevGame's — DevGame today ships as a desktop app you download or build yourself; see Installation below.

Works with your subscriptions on Claude Code, Codex, Cursor, Grok Build, and OpenCode. If they're set up on your computer, DevGame can control them.

"Wait, what are you selling me?"

Nothing. We built T3 Code because we wanted the best possible development experience with agents. We were inspired by existing solutions like the Codex desktop app, Conductor, Claude Desktop and Cursor Glass, but none met our bar.

We wanted something performant, remote-ready, and truly open. If we ever go the wrong direction, we want you to have everything you need to fork and build the editor that you want.

Installation

Warning

DevGame currently supports Codex, Claude, Cursor, Grok Build and OpenCode. Install and authenticate at least one provider before use:

Codex: install Codex CLI and run codex login
Claude: install Claude Code and run claude auth login
Cursor: install Cursor CLI and run agent login
Grok Build: install Grok Build CLI and run grok login
OpenCode: install OpenCode and run opencode auth login

Download

Grab the latest build from GitHub Releases.

Note

The released macOS build is code-signed (Developer ID) and notarized by Apple — it opens like any normal download, no security warnings. (Only self-built binaries are unsigned; the build guide covers the one-time right-click-Open for those.)

Build from source

There's no package registry install yet — build the desktop app or run the dev server yourself. See docs/user/build-from-source.md for the full walkthrough (prerequisites, vp i, dev run, and packaging a desktop artifact).

Game features setup (Unity)

The Unity integration (Play/Stop, selection chips, one-click Setup Integrations) needs Unity's own official CLI on your machine, in addition to Unity Editor via Unity Hub:

brew install --cask unity-cli

(macOS; see Unity's own CLI docs for other platforms.) No Unity sign-in is needed for this — Setup Integrations works with a signed-out CLI (verified against a clean identity). Without the CLI installed, the Setup Integrations button in the engine toolbar does not appear. With it installed, open a Unity project as your DevGame project and click Setup Integrations — it installs Unity's own com.unity.pipeline package plus our bundled com.devgame.editor-presence package into the project and pairs them automatically.

Some notes

We are very very early in this project. Expect bugs.

We are (mostly) not accepting contributions yet. Small fixes may be considered. Big features will not be.

Documentation

Full docs live in docs/. There's no docs site yet.

Install and first run
Permission modes
Keyboard shortcuts
Remote access from a phone or another machine
Keeping app and server in sync
Source control integrations
Multiple accounts: Codex · Claude
Linux: run T3 Code as a background service

Building from source? Start at docs/user/build-from-source.md. For the architecture behind it, see docs/internals/overview.md.

If you REALLY want to contribute still.... read this first

The canonical build walkthrough lives at docs/user/build-from-source.md; the steps below are the short version.

Install `vp`

DevGame uses Vite+ so you'll need to install the global vp command-line tool.

macOS / Linux

curl -fsSL https://vite.plus | bash

Windows

irm https://vite.plus/ps1 | iex

Checkout their getting started guide for more information: https://viteplus.dev/guide/

Install dependencies

vp i

Read CONTRIBUTING.md before opening an issue or PR.

Need support? Join the Discord.

DevGame

DevGame is a fork of T3 Code, built by T3 Tools, Inc. and MIT-licensed.
Almost everything that makes this application work was written by them — the agent harness, the terminal, checkpointing, source control, device pairing, and all four client apps. We specialised it for game development; we did not build it. Full credit, and what we actually added, in ATTRIBUTION.md.
If you want the general-purpose agent harness rather than the game-dev one, use T3 Code — it is the better tool for that job and it is where this came from.

T3 Code (below) is an "agent harness control surface". It enables control of the agents on your machine with a best-in-class mobile app (iOS, Android), web app and Electron-based desktop app. Those store listings and hosted apps are T3 Code's, not DevGame's — DevGame today ships as a desktop app you download or build yourself; see Installation below.

Works with your subscriptions on Claude Code, Codex, Cursor, Grok Build, and OpenCode. If they're set up on your computer, DevGame can control them.

"Wait, what are you selling me?"

Nothing. We built T3 Code because we wanted the best possible development experience with agents. We were inspired by existing solutions like the Codex desktop app, Conductor, Claude Desktop and Cursor Glass, but none met our bar.

We wanted something performant, remote-ready, and truly open. If we ever go the wrong direction, we want you to have everything you need to fork and build the editor that you want.

Installation

Warning

DevGame currently supports Codex, Claude, Cursor, Grok Build and OpenCode. Install and authenticate at least one provider before use:

Codex: install Codex CLI and run codex login
Claude: install Claude Code and run claude auth login
Cursor: install Cursor CLI and run agent login
Grok Build: install Grok Build CLI and run grok login
OpenCode: install OpenCode and run opencode auth login

Download

Grab the latest build from GitHub Releases.

Note

The released macOS build is code-signed (Developer ID) and notarized by Apple — it opens like any normal download, no security warnings. (Only self-built binaries are unsigned; the build guide covers the one-time right-click-Open for those.)

Build from source

There's no package registry install yet — build the desktop app or run the dev server yourself. See docs/user/build-from-source.md for the full walkthrough (prerequisites, vp i, dev run, and packaging a desktop artifact).

Game features setup (Unity)

The Unity integration (Play/Stop, selection chips, one-click Setup Integrations) needs Unity's own official CLI on your machine, in addition to Unity Editor via Unity Hub:

brew install --cask unity-cli

(macOS; see Unity's own CLI docs for other platforms.) No Unity sign-in is needed for this — Setup Integrations works with a signed-out CLI (verified against a clean identity). Without the CLI installed, the Setup Integrations button in the engine toolbar does not appear. With it installed, open a Unity project as your DevGame project and click Setup Integrations — it installs Unity's own com.unity.pipeline package plus our bundled com.devgame.editor-presence package into the project and pairs them automatically.

Some notes

We are very very early in this project. Expect bugs.

We are (mostly) not accepting contributions yet. Small fixes may be considered. Big features will not be.

Documentation

Full docs live in docs/. There's no docs site yet.

Install and first run
Permission modes
Keyboard shortcuts
Remote access from a phone or another machine
Keeping app and server in sync
Source control integrations
Multiple accounts: Codex · Claude
Linux: run T3 Code as a background service

Building from source? Start at docs/user/build-from-source.md. For the architecture behind it, see docs/internals/overview.md.

If you REALLY want to contribute still.... read this first

The canonical build walkthrough lives at docs/user/build-from-source.md; the steps below are the short version.

Install `vp`

DevGame uses Vite+ so you'll need to install the global vp command-line tool.

macOS / Linux

curl -fsSL https://vite.plus | bash

Windows

irm https://vite.plus/ps1 | iex

Checkout their getting started guide for more information: https://viteplus.dev/guide/

Install dependencies

vp i

Read CONTRIBUTING.md before opening an issue or PR.

Need support? Join the Discord.

DevGame

DevGame is a fork of T3 Code, built by T3 Tools, Inc. and MIT-licensed.
Almost everything that makes this application work was written by them — the agent harness, the terminal, checkpointing, source control, device pairing, and all four client apps. We specialised it for game development; we did not build it. Full credit, and what we actually added, in ATTRIBUTION.md.
If you want the general-purpose agent harness rather than the game-dev one, use T3 Code — it is the better tool for that job and it is where this came from.

T3 Code (below) is an "agent harness control surface". It enables control of the agents on your machine with a best-in-class mobile app (iOS, Android), web app and Electron-based desktop app. Those store listings and hosted apps are T3 Code's, not DevGame's — DevGame today ships as a desktop app you download or build yourself; see Installation below.

Works with your subscriptions on Claude Code, Codex, Cursor, Grok Build, and OpenCode. If they're set up on your computer, DevGame can control them.

"Wait, what are you selling me?"

Nothing. We built T3 Code because we wanted the best possible development experience with agents. We were inspired by existing solutions like the Codex desktop app, Conductor, Claude Desktop and Cursor Glass, but none met our bar.

We wanted something performant, remote-ready, and truly open. If we ever go the wrong direction, we want you to have everything you need to fork and build the editor that you want.

Installation

Warning

DevGame currently supports Codex, Claude, Cursor, Grok Build and OpenCode. Install and authenticate at least one provider before use:

Codex: install Codex CLI and run codex login
Claude: install Claude Code and run claude auth login
Cursor: install Cursor CLI and run agent login
Grok Build: install Grok Build CLI and run grok login
OpenCode: install OpenCode and run opencode auth login

Download

Grab the latest build from GitHub Releases.

Note

The released macOS build is code-signed (Developer ID) and notarized by Apple — it opens like any normal download, no security warnings. (Only self-built binaries are unsigned; the build guide covers the one-time right-click-Open for those.)

Build from source

There's no package registry install yet — build the desktop app or run the dev server yourself. See docs/user/build-from-source.md for the full walkthrough (prerequisites, vp i, dev run, and packaging a desktop artifact).

Game features setup (Unity)

The Unity integration (Play/Stop, selection chips, one-click Setup Integrations) needs Unity's own official CLI on your machine, in addition to Unity Editor via Unity Hub:

brew install --cask unity-cli

(macOS; see Unity's own CLI docs for other platforms.) No Unity sign-in is needed for this — Setup Integrations works with a signed-out CLI (verified against a clean identity). Without the CLI installed, the Setup Integrations button in the engine toolbar does not appear. With it installed, open a Unity project as your DevGame project and click Setup Integrations — it installs Unity's own com.unity.pipeline package plus our bundled com.devgame.editor-presence package into the project and pairs them automatically.

Some notes

We are very very early in this project. Expect bugs.

We are (mostly) not accepting contributions yet. Small fixes may be considered. Big features will not be.

Documentation

Full docs live in docs/. There's no docs site yet.

Install and first run
Permission modes
Keyboard shortcuts
Remote access from a phone or another machine
Keeping app and server in sync
Source control integrations
Multiple accounts: Codex · Claude
Linux: run T3 Code as a background service

Building from source? Start at docs/user/build-from-source.md. For the architecture behind it, see docs/internals/overview.md.

If you REALLY want to contribute still.... read this first

The canonical build walkthrough lives at docs/user/build-from-source.md; the steps below are the short version.

Install `vp`

DevGame uses Vite+ so you'll need to install the global vp command-line tool.

macOS / Linux

curl -fsSL https://vite.plus | bash

Windows

irm https://vite.plus/ps1 | iex

Checkout their getting started guide for more information: https://viteplus.dev/guide/

Install dependencies

vp i

Read CONTRIBUTING.md before opening an issue or PR.

Need support? Join the Discord.

DevGame

DevGame is a fork of T3 Code, built by T3 Tools, Inc. and MIT-licensed.
Almost everything that makes this application work was written by them — the agent harness, the terminal, checkpointing, source control, device pairing, and all four client apps. We specialised it for game development; we did not build it. Full credit, and what we actually added, in ATTRIBUTION.md.
If you want the general-purpose agent harness rather than the game-dev one, use T3 Code — it is the better tool for that job and it is where this came from.

T3 Code (below) is an "agent harness control surface". It enables control of the agents on your machine with a best-in-class mobile app (iOS, Android), web app and Electron-based desktop app. Those store listings and hosted apps are T3 Code's, not DevGame's — DevGame today ships as a desktop app you download or build yourself; see Installation below.

Works with your subscriptions on Claude Code, Codex, Cursor, Grok Build, and OpenCode. If they're set up on your computer, DevGame can control them.

"Wait, what are you selling me?"

Nothing. We built T3 Code because we wanted the best possible development experience with agents. We were inspired by existing solutions like the Codex desktop app, Conductor, Claude Desktop and Cursor Glass, but none met our bar.

We wanted something performant, remote-ready, and truly open. If we ever go the wrong direction, we want you to have everything you need to fork and build the editor that you want.

Installation

Warning

DevGame currently supports Codex, Claude, Cursor, Grok Build and OpenCode. Install and authenticate at least one provider before use:

Codex: install Codex CLI and run codex login
Claude: install Claude Code and run claude auth login
Cursor: install Cursor CLI and run agent login
Grok Build: install Grok Build CLI and run grok login
OpenCode: install OpenCode and run opencode auth login

Download

Grab the latest build from GitHub Releases.

Note

The released macOS build is code-signed (Developer ID) and notarized by Apple — it opens like any normal download, no security warnings. (Only self-built binaries are unsigned; the build guide covers the one-time right-click-Open for those.)

Build from source

There's no package registry install yet — build the desktop app or run the dev server yourself. See docs/user/build-from-source.md for the full walkthrough (prerequisites, vp i, dev run, and packaging a desktop artifact).

Game features setup (Unity)

The Unity integration (Play/Stop, selection chips, one-click Setup Integrations) needs Unity's own official CLI on your machine, in addition to Unity Editor via Unity Hub:

brew install --cask unity-cli

(macOS; see Unity's own CLI docs for other platforms.) No Unity sign-in is needed for this — Setup Integrations works with a signed-out CLI (verified against a clean identity). Without the CLI installed, the Setup Integrations button in the engine toolbar does not appear. With it installed, open a Unity project as your DevGame project and click Setup Integrations — it installs Unity's own com.unity.pipeline package plus our bundled com.devgame.editor-presence package into the project and pairs them automatically.

Some notes

We are very very early in this project. Expect bugs.

We are (mostly) not accepting contributions yet. Small fixes may be considered. Big features will not be.

Documentation

Full docs live in docs/. There's no docs site yet.

Install and first run
Permission modes
Keyboard shortcuts
Remote access from a phone or another machine
Keeping app and server in sync
Source control integrations
Multiple accounts: Codex · Claude
Linux: run T3 Code as a background service

Building from source? Start at docs/user/build-from-source.md. For the architecture behind it, see docs/internals/overview.md.

If you REALLY want to contribute still.... read this first

The canonical build walkthrough lives at docs/user/build-from-source.md; the steps below are the short version.

Install `vp`

DevGame uses Vite+ so you'll need to install the global vp command-line tool.

macOS / Linux

curl -fsSL https://vite.plus | bash

Windows

irm https://vite.plus/ps1 | iex

Checkout their getting started guide for more information: https://viteplus.dev/guide/

Install dependencies

vp i

Read CONTRIBUTING.md before opening an issue or PR.

Need support? Join the Discord.

DevGame

DevGame is a fork of T3 Code, built by T3 Tools, Inc. and MIT-licensed.
Almost everything that makes this application work was written by them — the agent harness, the terminal, checkpointing, source control, device pairing, and all four client apps. We specialised it for game development; we did not build it. Full credit, and what we actually added, in ATTRIBUTION.md.
If you want the general-purpose agent harness rather than the game-dev one, use T3 Code — it is the better tool for that job and it is where this came from.

T3 Code (below) is an "agent harness control surface". It enables control of the agents on your machine with a best-in-class mobile app (iOS, Android), web app and Electron-based desktop app. Those store listings and hosted apps are T3 Code's, not DevGame's — DevGame today ships as a desktop app you download or build yourself; see Installation below.

Works with your subscriptions on Claude Code, Codex, Cursor, Grok Build, and OpenCode. If they're set up on your computer, DevGame can control them.

"Wait, what are you selling me?"

Nothing. We built T3 Code because we wanted the best possible development experience with agents. We were inspired by existing solutions like the Codex desktop app, Conductor, Claude Desktop and Cursor Glass, but none met our bar.

We wanted something performant, remote-ready, and truly open. If we ever go the wrong direction, we want you to have everything you need to fork and build the editor that you want.

Installation

Warning

DevGame currently supports Codex, Claude, Cursor, Grok Build and OpenCode. Install and authenticate at least one provider before use:

Codex: install Codex CLI and run codex login
Claude: install Claude Code and run claude auth login
Cursor: install Cursor CLI and run agent login
Grok Build: install Grok Build CLI and run grok login
OpenCode: install OpenCode and run opencode auth login

Download

Grab the latest build from GitHub Releases.

Note

The released macOS build is code-signed (Developer ID) and notarized by Apple — it opens like any normal download, no security warnings. (Only self-built binaries are unsigned; the build guide covers the one-time right-click-Open for those.)

Build from source

There's no package registry install yet — build the desktop app or run the dev server yourself. See docs/user/build-from-source.md for the full walkthrough (prerequisites, vp i, dev run, and packaging a desktop artifact).

Game features setup (Unity)

The Unity integration (Play/Stop, selection chips, one-click Setup Integrations) needs Unity's own official CLI on your machine, in addition to Unity Editor via Unity Hub:

brew install --cask unity-cli

(macOS; see Unity's own CLI docs for other platforms.) No Unity sign-in is needed for this — Setup Integrations works with a signed-out CLI (verified against a clean identity). Without the CLI installed, the Setup Integrations button in the engine toolbar does not appear. With it installed, open a Unity project as your DevGame project and click Setup Integrations — it installs Unity's own com.unity.pipeline package plus our bundled com.devgame.editor-presence package into the project and pairs them automatically.

Some notes

We are very very early in this project. Expect bugs.

We are (mostly) not accepting contributions yet. Small fixes may be considered. Big features will not be.

Documentation

Full docs live in docs/. There's no docs site yet.

Install and first run
Permission modes
Keyboard shortcuts
Remote access from a phone or another machine
Keeping app and server in sync
Source control integrations
Multiple accounts: Codex · Claude
Linux: run T3 Code as a background service

Building from source? Start at docs/user/build-from-source.md. For the architecture behind it, see docs/internals/overview.md.

If you REALLY want to contribute still.... read this first

The canonical build walkthrough lives at docs/user/build-from-source.md; the steps below are the short version.

Install `vp`

DevGame uses Vite+ so you'll need to install the global vp command-line tool.

macOS / Linux

curl -fsSL https://vite.plus | bash

Windows

irm https://vite.plus/ps1 | iex

Checkout their getting started guide for more information: https://viteplus.dev/guide/

Install dependencies

vp i

Read CONTRIBUTING.md before opening an issue or PR.

Need support? Join the Discord.

DevGame

DevGame is a fork of T3 Code, built by T3 Tools, Inc. and MIT-licensed.
Almost everything that makes this application work was written by them — the agent harness, the terminal, checkpointing, source control, device pairing, and all four client apps. We specialised it for game development; we did not build it. Full credit, and what we actually added, in ATTRIBUTION.md.
If you want the general-purpose agent harness rather than the game-dev one, use T3 Code — it is the better tool for that job and it is where this came from.

T3 Code (below) is an "agent harness control surface". It enables control of the agents on your machine with a best-in-class mobile app (iOS, Android), web app and Electron-based desktop app. Those store listings and hosted apps are T3 Code's, not DevGame's — DevGame today ships as a desktop app you download or build yourself; see Installation below.

Works with your subscriptions on Claude Code, Codex, Cursor, Grok Build, and OpenCode. If they're set up on your computer, DevGame can control them.

"Wait, what are you selling me?"

Nothing. We built T3 Code because we wanted the best possible development experience with agents. We were inspired by existing solutions like the Codex desktop app, Conductor, Claude Desktop and Cursor Glass, but none met our bar.

We wanted something performant, remote-ready, and truly open. If we ever go the wrong direction, we want you to have everything you need to fork and build the editor that you want.

Installation

Warning

DevGame currently supports Codex, Claude, Cursor, Grok Build and OpenCode. Install and authenticate at least one provider before use:

Codex: install Codex CLI and run codex login
Claude: install Claude Code and run claude auth login
Cursor: install Cursor CLI and run agent login
Grok Build: install Grok Build CLI and run grok login
OpenCode: install OpenCode and run opencode auth login

Download

Grab the latest build from GitHub Releases.

Note

The released macOS build is code-signed (Developer ID) and notarized by Apple — it opens like any normal download, no security warnings. (Only self-built binaries are unsigned; the build guide covers the one-time right-click-Open for those.)

Build from source

There's no package registry install yet — build the desktop app or run the dev server yourself. See docs/user/build-from-source.md for the full walkthrough (prerequisites, vp i, dev run, and packaging a desktop artifact).

Game features setup (Unity)

The Unity integration (Play/Stop, selection chips, one-click Setup Integrations) needs Unity's own official CLI on your machine, in addition to Unity Editor via Unity Hub:

brew install --cask unity-cli

(macOS; see Unity's own CLI docs for other platforms.) No Unity sign-in is needed for this — Setup Integrations works with a signed-out CLI (verified against a clean identity). Without the CLI installed, the Setup Integrations button in the engine toolbar does not appear. With it installed, open a Unity project as your DevGame project and click Setup Integrations — it installs Unity's own com.unity.pipeline package plus our bundled com.devgame.editor-presence package into the project and pairs them automatically.

Some notes

We are very very early in this project. Expect bugs.

We are (mostly) not accepting contributions yet. Small fixes may be considered. Big features will not be.

Documentation

Full docs live in docs/. There's no docs site yet.

Install and first run
Permission modes
Keyboard shortcuts
Remote access from a phone or another machine
Keeping app and server in sync
Source control integrations
Multiple accounts: Codex · Claude
Linux: run T3 Code as a background service

Building from source? Start at docs/user/build-from-source.md. For the architecture behind it, see docs/internals/overview.md.

If you REALLY want to contribute still.... read this first

The canonical build walkthrough lives at docs/user/build-from-source.md; the steps below are the short version.

Install `vp`

DevGame uses Vite+ so you'll need to install the global vp command-line tool.

macOS / Linux

curl -fsSL https://vite.plus | bash

Windows

irm https://vite.plus/ps1 | iex

Checkout their getting started guide for more information: https://viteplus.dev/guide/

Install dependencies

vp i

Read CONTRIBUTING.md before opening an issue or PR.

Need support? Join the Discord.

DevGame

DevGame is a fork of T3 Code, built by T3 Tools, Inc. and MIT-licensed.
Almost everything that makes this application work was written by them — the agent harness, the terminal, checkpointing, source control, device pairing, and all four client apps. We specialised it for game development; we did not build it. Full credit, and what we actually added, in ATTRIBUTION.md.
If you want the general-purpose agent harness rather than the game-dev one, use T3 Code — it is the better tool for that job and it is where this came from.

T3 Code (below) is an "agent harness control surface". It enables control of the agents on your machine with a best-in-class mobile app (iOS, Android), web app and Electron-based desktop app. Those store listings and hosted apps are T3 Code's, not DevGame's — DevGame today ships as a desktop app you download or build yourself; see Installation below.

Works with your subscriptions on Claude Code, Codex, Cursor, Grok Build, and OpenCode. If they're set up on your computer, DevGame can control them.

"Wait, what are you selling me?"

Nothing. We built T3 Code because we wanted the best possible development experience with agents. We were inspired by existing solutions like the Codex desktop app, Conductor, Claude Desktop and Cursor Glass, but none met our bar.

We wanted something performant, remote-ready, and truly open. If we ever go the wrong direction, we want you to have everything you need to fork and build the editor that you want.

Installation

Warning

DevGame currently supports Codex, Claude, Cursor, Grok Build and OpenCode. Install and authenticate at least one provider before use:

Codex: install Codex CLI and run codex login
Claude: install Claude Code and run claude auth login
Cursor: install Cursor CLI and run agent login
Grok Build: install Grok Build CLI and run grok login
OpenCode: install OpenCode and run opencode auth login

Download

Grab the latest build from GitHub Releases.

Note

The released macOS build is code-signed (Developer ID) and notarized by Apple — it opens like any normal download, no security warnings. (Only self-built binaries are unsigned; the build guide covers the one-time right-click-Open for those.)

Build from source

There's no package registry install yet — build the desktop app or run the dev server yourself. See docs/user/build-from-source.md for the full walkthrough (prerequisites, vp i, dev run, and packaging a desktop artifact).

Game features setup (Unity)

The Unity integration (Play/Stop, selection chips, one-click Setup Integrations) needs Unity's own official CLI on your machine, in addition to Unity Editor via Unity Hub:

brew install --cask unity-cli

(macOS; see Unity's own CLI docs for other platforms.) No Unity sign-in is needed for this — Setup Integrations works with a signed-out CLI (verified against a clean identity). Without the CLI installed, the Setup Integrations button in the engine toolbar does not appear. With it installed, open a Unity project as your DevGame project and click Setup Integrations — it installs Unity's own com.unity.pipeline package plus our bundled com.devgame.editor-presence package into the project and pairs them automatically.

Some notes

We are very very early in this project. Expect bugs.

We are (mostly) not accepting contributions yet. Small fixes may be considered. Big features will not be.

Documentation

Full docs live in docs/. There's no docs site yet.

Install and first run
Permission modes
Keyboard shortcuts
Remote access from a phone or another machine
Keeping app and server in sync
Source control integrations
Multiple accounts: Codex · Claude
Linux: run T3 Code as a background service

Building from source? Start at docs/user/build-from-source.md. For the architecture behind it, see docs/internals/overview.md.

If you REALLY want to contribute still.... read this first

The canonical build walkthrough lives at docs/user/build-from-source.md; the steps below are the short version.

Install `vp`

DevGame uses Vite+ so you'll need to install the global vp command-line tool.

macOS / Linux

curl -fsSL https://vite.plus | bash

Windows

irm https://vite.plus/ps1 | iex

Checkout their getting started guide for more information: https://viteplus.dev/guide/

Install dependencies

vp i

Read CONTRIBUTING.md before opening an issue or PR.

Need support? Join the Discord.

DevGame

DevGame is a fork of T3 Code, built by T3 Tools, Inc. and MIT-licensed.
Almost everything that makes this application work was written by them — the agent harness, the terminal, checkpointing, source control, device pairing, and all four client apps. We specialised it for game development; we did not build it. Full credit, and what we actually added, in ATTRIBUTION.md.
If you want the general-purpose agent harness rather than the game-dev one, use T3 Code — it is the better tool for that job and it is where this came from.

T3 Code (below) is an "agent harness control surface". It enables control of the agents on your machine with a best-in-class mobile app (iOS, Android), web app and Electron-based desktop app. Those store listings and hosted apps are T3 Code's, not DevGame's — DevGame today ships as a desktop app you download or build yourself; see Installation below.

Works with your subscriptions on Claude Code, Codex, Cursor, Grok Build, and OpenCode. If they're set up on your computer, DevGame can control them.

"Wait, what are you selling me?"

Nothing. We built T3 Code because we wanted the best possible development experience with agents. We were inspired by existing solutions like the Codex desktop app, Conductor, Claude Desktop and Cursor Glass, but none met our bar.

We wanted something performant, remote-ready, and truly open. If we ever go the wrong direction, we want you to have everything you need to fork and build the editor that you want.

Installation

Warning

DevGame currently supports Codex, Claude, Cursor, Grok Build and OpenCode. Install and authenticate at least one provider before use:

Codex: install Codex CLI and run codex login
Claude: install Claude Code and run claude auth login
Cursor: install Cursor CLI and run agent login
Grok Build: install Grok Build CLI and run grok login
OpenCode: install OpenCode and run opencode auth login

Download

Grab the latest build from GitHub Releases.

Note

The released macOS build is code-signed (Developer ID) and notarized by Apple — it opens like any normal download, no security warnings. (Only self-built binaries are unsigned; the build guide covers the one-time right-click-Open for those.)

Build from source

There's no package registry install yet — build the desktop app or run the dev server yourself. See docs/user/build-from-source.md for the full walkthrough (prerequisites, vp i, dev run, and packaging a desktop artifact).

Game features setup (Unity)

The Unity integration (Play/Stop, selection chips, one-click Setup Integrations) needs Unity's own official CLI on your machine, in addition to Unity Editor via Unity Hub:

brew install --cask unity-cli

(macOS; see Unity's own CLI docs for other platforms.) No Unity sign-in is needed for this — Setup Integrations works with a signed-out CLI (verified against a clean identity). Without the CLI installed, the Setup Integrations button in the engine toolbar does not appear. With it installed, open a Unity project as your DevGame project and click Setup Integrations — it installs Unity's own com.unity.pipeline package plus our bundled com.devgame.editor-presence package into the project and pairs them automatically.

Some notes

We are very very early in this project. Expect bugs.

We are (mostly) not accepting contributions yet. Small fixes may be considered. Big features will not be.

Documentation

Full docs live in docs/. There's no docs site yet.

Install and first run
Permission modes
Keyboard shortcuts
Remote access from a phone or another machine
Keeping app and server in sync
Source control integrations
Multiple accounts: Codex · Claude
Linux: run T3 Code as a background service

Building from source? Start at docs/user/build-from-source.md. For the architecture behind it, see docs/internals/overview.md.

If you REALLY want to contribute still.... read this first

The canonical build walkthrough lives at docs/user/build-from-source.md; the steps below are the short version.

Install `vp`

DevGame uses Vite+ so you'll need to install the global vp command-line tool.

macOS / Linux

curl -fsSL https://vite.plus | bash

Windows

irm https://vite.plus/ps1 | iex

Checkout their getting started guide for more information: https://viteplus.dev/guide/

Install dependencies

vp i

Read CONTRIBUTING.md before opening an issue or PR.

Need support? Join the Discord.

Name		Name	Last commit message	Last commit date
.agents/skills		.agents/skills
.claude		.claude
.codex		.codex
.cursor		.cursor
.devcontainer		.devcontainer
.github		.github
.macroscope/check-run-agents		.macroscope/check-run-agents
.plans		.plans
.repos		.repos
.vite-hooks		.vite-hooks
.vscode		.vscode
apps		apps
assets		assets
docs		docs
evidence		evidence
experiments/messages-glass-lab		experiments/messages-glass-lab
godot		godot
infra/relay		infra/relay
native		native
oxlint-plugin-t3code		oxlint-plugin-t3code
packages		packages
patches		patches
scripts		scripts
site		site
unity		unity
unreal		unreal
.env.example		.env.example
.gitattributes		.gitattributes
.gitignore		.gitignore
.mcp.json		.mcp.json
AGENTS.md		AGENTS.md
ATTRIBUTION.md		ATTRIBUTION.md
CLAUDE.md		CLAUDE.md
CONTRIBUTING.md		CONTRIBUTING.md
LICENSE		LICENSE
README.md		README.md
app.json		app.json
devgame.json		devgame.json
package.json		package.json
pnpm-lock.yaml		pnpm-lock.yaml
pnpm-workspace.yaml		pnpm-workspace.yaml
tsconfig.base.json		tsconfig.base.json
vite.config.ts		vite.config.ts

Name		Name	Last commit message	Last commit date
.agents/skills		.agents/skills
.claude		.claude
.codex		.codex
.cursor		.cursor
.devcontainer		.devcontainer
.github		.github
.macroscope/check-run-agents		.macroscope/check-run-agents
.plans		.plans
.repos		.repos
.vite-hooks		.vite-hooks
.vscode		.vscode
apps		apps
assets		assets
docs		docs
evidence		evidence
experiments/messages-glass-lab		experiments/messages-glass-lab
godot		godot
infra/relay		infra/relay
native		native
oxlint-plugin-t3code		oxlint-plugin-t3code
packages		packages
patches		patches
scripts		scripts
site		site
unity		unity
unreal		unreal
.env.example		.env.example
.gitattributes		.gitattributes
.gitignore		.gitignore
.mcp.json		.mcp.json
AGENTS.md		AGENTS.md
ATTRIBUTION.md		ATTRIBUTION.md
CLAUDE.md		CLAUDE.md
CONTRIBUTING.md		CONTRIBUTING.md
LICENSE		LICENSE
README.md		README.md
app.json		app.json
devgame.json		devgame.json
package.json		package.json
pnpm-lock.yaml		pnpm-lock.yaml
pnpm-workspace.yaml		pnpm-workspace.yaml
tsconfig.base.json		tsconfig.base.json
vite.config.ts		vite.config.ts

Name		Name	Last commit message	Last commit date
.agents/skills		.agents/skills
.claude		.claude
.codex		.codex
.cursor		.cursor
.devcontainer		.devcontainer
.github		.github
.macroscope/check-run-agents		.macroscope/check-run-agents
.plans		.plans
.repos		.repos
.vite-hooks		.vite-hooks
.vscode		.vscode
apps		apps
assets		assets
docs		docs
evidence		evidence
experiments/messages-glass-lab		experiments/messages-glass-lab
godot		godot
infra/relay		infra/relay
native		native
oxlint-plugin-t3code		oxlint-plugin-t3code
packages		packages
patches		patches
scripts		scripts
site		site
unity		unity
unreal		unreal
.env.example		.env.example
.gitattributes		.gitattributes
.gitignore		.gitignore
.mcp.json		.mcp.json
AGENTS.md		AGENTS.md
ATTRIBUTION.md		ATTRIBUTION.md
CLAUDE.md		CLAUDE.md
CONTRIBUTING.md		CONTRIBUTING.md
LICENSE		LICENSE
README.md		README.md
app.json		app.json
devgame.json		devgame.json
package.json		package.json
pnpm-lock.yaml		pnpm-lock.yaml
pnpm-workspace.yaml		pnpm-workspace.yaml
tsconfig.base.json		tsconfig.base.json
vite.config.ts		vite.config.ts

Name		Name	Last commit message	Last commit date
.agents/skills		.agents/skills
.claude		.claude
.codex		.codex
.cursor		.cursor
.devcontainer		.devcontainer
.github		.github
.macroscope/check-run-agents		.macroscope/check-run-agents
.plans		.plans
.repos		.repos
.vite-hooks		.vite-hooks
.vscode		.vscode
apps		apps
assets		assets
docs		docs
evidence		evidence
experiments/messages-glass-lab		experiments/messages-glass-lab
godot		godot
infra/relay		infra/relay
native		native
oxlint-plugin-t3code		oxlint-plugin-t3code
packages		packages
patches		patches
scripts		scripts
site		site
unity		unity
unreal		unreal
.env.example		.env.example
.gitattributes		.gitattributes
.gitignore		.gitignore
.mcp.json		.mcp.json
AGENTS.md		AGENTS.md
ATTRIBUTION.md		ATTRIBUTION.md
CLAUDE.md		CLAUDE.md
CONTRIBUTING.md		CONTRIBUTING.md
LICENSE		LICENSE
README.md		README.md
app.json		app.json
devgame.json		devgame.json
package.json		package.json
pnpm-lock.yaml		pnpm-lock.yaml
pnpm-workspace.yaml		pnpm-workspace.yaml
tsconfig.base.json		tsconfig.base.json
vite.config.ts		vite.config.ts

Name		Name	Last commit message	Last commit date
.agents/skills		.agents/skills
.claude		.claude
.codex		.codex
.cursor		.cursor
.devcontainer		.devcontainer
.github		.github
.macroscope/check-run-agents		.macroscope/check-run-agents
.plans		.plans
.repos		.repos
.vite-hooks		.vite-hooks
.vscode		.vscode
apps		apps
assets		assets
docs		docs
evidence		evidence
experiments/messages-glass-lab		experiments/messages-glass-lab
godot		godot
infra/relay		infra/relay
native		native
oxlint-plugin-t3code		oxlint-plugin-t3code
packages		packages
patches		patches
scripts		scripts
site		site
unity		unity
unreal		unreal
.env.example		.env.example
.gitattributes		.gitattributes
.gitignore		.gitignore
.mcp.json		.mcp.json
AGENTS.md		AGENTS.md
ATTRIBUTION.md		ATTRIBUTION.md
CLAUDE.md		CLAUDE.md
CONTRIBUTING.md		CONTRIBUTING.md
LICENSE		LICENSE
README.md		README.md
app.json		app.json
devgame.json		devgame.json
package.json		package.json
pnpm-lock.yaml		pnpm-lock.yaml
pnpm-workspace.yaml		pnpm-workspace.yaml
tsconfig.base.json		tsconfig.base.json
vite.config.ts		vite.config.ts

Latest commit

History

Folders and files

Repository files navigation

DevGame

"Wait, what are you selling me?"

Installation

Download

Build from source

Game features setup (Unity)

Some notes

Documentation

If you REALLY want to contribute still.... read this first

Install vp

macOS / Linux

Windows

Install dependencies

About

Resources

Contributing

Stars

Watchers

Forks

Releases

Packages

Contributors

Languages

Latest commit

History

Folders and files

Repository files navigation

DevGame

"Wait, what are you selling me?"

Installation

Download

Build from source

Game features setup (Unity)

Some notes

Documentation

If you REALLY want to contribute still.... read this first

Install vp

macOS / Linux

Windows

Install dependencies

About

Resources

Contributing

Stars

Watchers

Forks

Releases

Packages

Contributors

Languages

Latest commit

History

Folders and files

Repository files navigation

DevGame

"Wait, what are you selling me?"

Installation

Download

Build from source

Game features setup (Unity)

Some notes

Documentation

If you REALLY want to contribute still.... read this first

Install vp

macOS / Linux

Windows

Install dependencies

About

Resources

Contributing

Stars

Watchers

Forks

Releases

Packages

Contributors

Install `vp`

Install `vp`

Install `vp`

Install `vp`

Install `vp`