import {defineConfig} from 'vite';
import {iwsdkDev} from '@iwsdk/vite-plugin-dev';
export default defineConfig({
plugins: [iwsdkDev()],
});
iwsdk.config.json. Select the development session at the command line.npx iwsdk adapter sync
npx iwsdk adapter sync --tools claude,cursor
| AI tool | MCP configuration | Additional behavior |
|---|---|---|
Claude Code | .mcp.json | Creates a CLAUDE.md shim when no supported Claude instruction file exists. |
Cursor | .cursor/mcp.json | Adds only IWSDK-managed server and permission entries. |
GitHub Copilot | .vscode/mcp.json | Requires you to approve the MCP server in Visual Studio Code. A repository file cannot grant that approval. |
Codex | .codex/config.toml | Sets approval mode for the managed IWSDK server entry. |
OpenCode | opencode.json | Adds the managed MCP server and IWSDK skill permissions. |
AGENTS.md only when that file is absent and can create the Claude shim, but it does not overwrite existing instruction files or install or refresh the generated skill directories. New projects receive their complete guidance and skills from the project generator.npx iwsdk adapter status
npx iwsdk adapter prune to remove only IWSDK-managed MCP and permission entries. For an unsupported MCP client, run npx iwsdk adapter prompt and follow the generated integration instructions.npx iwsdk dev up --foreground
npx iwsdk dev up --ai-mode collaborate --foreground
npx iwsdk dev up --ai-mode agent --foreground
--no-open only when you deliberately want the development server without a managed browser. All iwsdk-runtime tool calls are unavailable in that state, including scene, UI, XR, browser, and ECS tools; schema inspection with iwsdk mcp inspect still works.npm run dev.npx iwsdk dev status
true:state.browserCommandReadystate.session.browser.commandReadynpx iwsdk mcp inspect npx iwsdk mcp inspect --tool scene_render_file
iwsdk-runtime server and use its reported schemas.Use the IWSDK runtime tools to check the XR session, capture the application runtime, and report any console errors.
xr_get_session_status, browser_screenshot, and browser_get_console_logs. browser_screenshot always captures the application runtime, even when the Editor view is visible.Inspect the native scene capabilities, update the scene files, render every changed file, flatten the composed root, open the flattened file, and capture both editor and runtime evidence.
Inspect the current app, click the Settings button, and verify the result.
browser_snapshot, uses the returned element ref with browser_interact, and then captures another snapshot or screenshot. Browser tools target the current application automatically, including its runtime frame in the managed workspace. There is no target selector or arbitrary navigation tool.Profile the next interaction and report frame timing, long tasks, and event timing.
browser_profile, performs the interaction, and stops the profile. The result is an uncalibrated host-browser diagnostic, not target-device performance.npx iwsdk dev up --ai-mode agent \ --screenshot-width 1280 \ --screenshot-height 720
npx iwsdk dev status npx iwsdk dev logs --tail 100
--no-open. Wait for both browser command readiness fields before retrying the tool call.npx iwsdk adapter status, then run npx iwsdk adapter sync if the managed entry is missing or stale. Restart the AI tool if it does not reload project-local MCP configuration automatically.iwsdk-runtime tool schemas with your AI tool’s tool-search or discovery step if needed.xr_get_session_status as the first runtime check once the tool is available.npx @iwsdk/cli xr status or npx @iwsdk/cli browser screenshot, until the schemas load. See Workflows for the full list.scene_render_file, resolve every diagnostic, and then create an import-free file with scene_flatten_file. Pass the flattened path to scene_open.scene_screenshot for a native Editor image and scene_get_state for structured validation, dirty, conflict, and runtime-readiness diagnostics. Use browser_screenshot for the running application. browser_screenshot does not accept an editor target.