Codex

Updated: Jun 22, 2026

Overview

Codex should use the DAT GitHub repository as a plugin marketplace. This keeps Codex on the same git-backed DAT guidance that is published for Claude Code and other tools, instead of relying on pasted prompt text.
Once loaded, Codex has DAT-specific context and can help you:
  • Set up your project and add DAT SDK dependencies
  • Implement camera streaming, display, session lifecycle, and permissions
  • Write tests with Mock Device Kit
  • Debug common integration issues
For the best results, combine the Codex plugin with the DAT MCP server. The plugin provides coding patterns from the GitHub repo; MCP provides current published docs through search_dat_docs.

Setup

Add the DAT repository for your platform as a Codex plugin marketplace, then add the platform plugin.
iOS:
codex plugin marketplace add facebook/meta-wearables-dat-ios
codex plugin add mwdat-ios@mwdat-ios-marketplace
Android:
codex plugin marketplace add facebook/meta-wearables-dat-android
codex plugin add mwdat-android@mwdat-android-marketplace
If you already have a checkout of the DAT GitHub repo, add it as a local marketplace from the repo root, then add the same plugin:
codex plugin marketplace add .
codex plugin add mwdat-ios@mwdat-ios-marketplace
Use mwdat-android@mwdat-android-marketplace for an Android checkout.

Adding live docs lookup

The Codex plugin covers integration patterns and best practices. Add the Wearables MCP endpoint when you also want Codex to look up current DAT docs while it works:
codex mcp add wearables --url https://mcp.developer.meta.com/wearables
If you are editing Codex configuration manually, use this URL:
https://mcp.developer.meta.com/wearables
After adding the endpoint in your Codex MCP configuration, verify that search_dat_docs is available. A running Codex session may not hot-reload newly added MCP servers, so start a fresh Codex session if codex mcp list shows wearables but the assistant cannot see the tool yet. When Codex calls search_dat_docs, ask it to request Markdown-formatted results if the MCP client supports output formats.
Example prompt:
Use the installed DAT Codex plugin for implementation guidance. Then use the Wearables MCP endpoint https://mcp.developer.meta.com/wearables to call search_dat_docs for current iOS camera streaming guidance, with Markdown-formatted results if available. Inspect my project first, make the smallest safe change, and run the relevant local checks.

Usage

Start Codex in your project directory and ask DAT-specific questions directly:
How do I set up camera streaming in my Android app?
Write a test for my session lifecycle using MockDeviceKit.
Implement a DAT display session for iOS and explain the required permission flow.

Adding the API reference

The DAT plugin covers setup and integration guidance. If you need exact API signatures or full reference content, provide the llms.txt URL in your prompt:
Use https://wearables.developer.meta.com/llms.txt?full=true as reference and show the current StreamSession configuration options.
Or add it to your local project guidance so it loads automatically:
## API Reference
Fetch https://wearables.developer.meta.com/llms.txt?full=true for the Wearables Device Access Toolkit API reference.
Codex can use the plugin, MCP docs search, and llms.txt together: plugin for project patterns, MCP for current guides, and llms.txt for exact API reference details.