Install the Device Access Toolkit plugin from the SDK GitHub repo to give Muse Code context on the SDK. Once installed and approved, Muse Code can help you:
Set up dependencies, app registration, and the first working integration
Manage session and stream lifecycle, pause and resume behavior, and device availability
Configure camera streaming, resolution, and frame rates
Request and handle device permissions
Test without physical glasses using MockDeviceKit
Look up live Device Access Toolkit documentation with search_dat_docs
Muse Code also reads AGENTS.md from your project root with no setup at all. See AGENTS.md if you want the portable fallback instead of the plugin.
Setup
Add the SDK repo as a marketplace, install the plugin, then approve it.
Muse Code plugin support is experimental. Run export MUSE_EXPERIMENTAL_PLUGINS=1 in your shell before using the plugin commands.
The approve step is required. Muse Code holds a newly installed plugin’s contributed capabilities for review, so the Device Access Toolkit guidance and live docs lookup stay inactive until you approve the plugin by name.
Installing the plugin also registers the hosted Device Access Toolkit docs MCP server. You do not need to add the server separately or edit ~/.config/muse/settings.json.
If you cloned the SDK repo, you can run the bundled installer instead:
The installer requires muse on your PATH and runs the same three commands, including the approve step.
Usage
Ask SDK questions directly in a Muse Code session:
Set up a Device Access Toolkit session with camera streaming and handle lifecycle events.
Live docs lookup
After approving the plugin, start a new session and confirm that the Device Access Toolkit guidance and search_dat_docs are available before editing code. The public docs MCP server does not require authentication.
Example prompt:
Use the installed Device Access Toolkit plugin for platform-specific implementation patterns. Then ask search_dat_docs for current camera streaming and session lifecycle guidance. Inspect my project first, make the smallest safe change, and run the relevant local checks.
Adding the API reference
The plugin covers integration patterns and best practices. To add the full API reference, point Muse Code at the llms.txt endpoint in your prompt:
Read https://wearables.developer.meta.com/llms.txt?full=true for the full Wearables Device Access Toolkit API surface before choosing method signatures or parameter types.