Air Jam Devtools

The Node authoring and evaluation toolchain shared by Air Jam CLI, MCP and Studio consumers. Games use @air-jam/sdk; tools use the explicit devtools module that owns their operation. There is no catch-all root import.

Entry points

| Import suffix | Responsibility | | --------------------- | ----------------------------------------------------------------- | | context | Discover and inspect a game or declared workspace | | games | Inspect games and their available capabilities | | dev | Start, inspect, reset and stop managed development | | logs | Read the unified development log stream | | controller | Connect virtual controllers, send input and inspect runtime state | | agent | Inspect semantic game contracts and invoke actions | | game-session | Own a complete semantic playtest session | | game-session-broker | Broker sessions for tool hosts | | visual | List scenarios and capture game visuals | | harness/visual | Define and run visual or prefab capture harnesses | | quality | Run project quality gates and complete evaluations | | mcp-config | Inspect, write and repair project MCP configuration | | platform-auth | Authenticate optional hosted operations | | platform-games | Manage optional hosted game metadata | | platform-game-media | Manage optional hosted game media | | release | Prepare and operate optional hosted releases |

Functions and their public option/result types share an entry point:

import { startDev, type StartDevOptions } from "@air-jam/devtools/dev";

const options: StartDevOptions = { cwd: process.cwd(), mode: "standalone-dev" };
const development = await startDev(options);

CLI and MCP are the normal human/agent front doors. Import these modules when embedding the same operations in another tool host. Packaged executable helpers are implementation details used by that version of devtools, not independent public entry points.

Workspace and package contracts

Ordinary game projects need no workspace declaration. A workspace owns its entrypoint and supported modes through the workspace runtime contract, not through a guessed repository layout or a root SDK dependency.

All six Air Jam packages release together. Upgrade the coordinated family together; documented module exports and their types follow the public support contract. Hosted clients are optional: local development, inspection and evaluation do not require an Air Jam platform account.