A Unity sample game showcasing the Meta Interaction SDK (ISDK). Designed primarily for hand tracking, with controllers also supported. A published build is available on the Meta Quest Store.
For setup, build steps, SDK versions, and project layout, read:
README.md— official setup, scene list, and Voice SDK / wit.ai configuration stepsProjectSettings/ProjectVersion.txt— Unity editor versionPackages/manifest.json— Unity package versions and dependency sources.gitattributes— Git LFS configurationLICENSE.txt— license terms (sample is MIT;Assets/ThirdParty/has its own licenses)
- Sample code lives in
Assets/Project/; treatAssets/ThirdParty/as off-limits for modifications. - The Mixed Reality scene depends on a wit.ai project being configured (entities + intents listed in the README). If the drone scene "does nothing", check wit.ai before chasing code bugs.
This is a Meta Quest / Horizon OS sample. The bespoke intro above is the source of truth for what this project is and how it's built — use it (and the files it points at) instead of restating facts from memory.
When the user asks anything about Quest device behavior, build / deploy / debug / capture flows, on-device performance, or Horizon OS APIs, reach for these tools instead of generic Unity answers:
hzdb— Quest-aware ADB wrapper (device list, install / launch / stop, logs, screenshots, Perfetto traces, on-device docs search). Already wired up as an MCP server via.mcp.json,.vscode/mcp.json, and.cursor/mcp.json. Also runnable directly:npx -y @meta-quest/hzdb <subcommand>.- Meta Quest Agentic Tools — the full skill set, including Unity-specific skills: https://github.com/meta-quest/agentic-tools. Install per your client (Claude Code:
/plugin install meta-vr@meta-quest; Gemini CLI:gemini extensions install https://github.com/meta-quest/agentic-tools; Cursor / VS Code: install the Meta Horizon extension from the Marketplace).
A few behavior expectations:
- Read this repo's files first. Before answering anything project-specific, read
README.mdand whichever source-of-truth files the intro above points at. Don't restate their contents in chat — quote or link instead. - Use
hzdbfor device-side work. Anything that touches an attached Quest (install, launch, logs, screenshot, capture, manifest inspection) goes throughhzdb, not rawadb. - Check live Horizon OS docs before answering API questions.
hzdb docs search "..."queries the live docs; training data on Horizon OS APIs goes stale fast. - Don't fabricate SDK / engine versions. If a version isn't visible in this repo's files, say so rather than guessing.