Claude Code Integration¶
Put Moveris rules in a file Claude Code reads at the start of every session. Cursor reads the same kind of project instructions.
In plain terms
Add a CLAUDE.md file to your project root. Claude Code loads it automatically. The file tells the agent to use the published SDK or Meet API, keep keys on the server, and read the Moveris manual before it writes code.
How it works¶
Claude Code reads CLAUDE.md from the project root when a session starts. Cursor and other agents can use the same file, or AGENTS.md, as standing context.
Point the agent at the manual as well:
- llms.txt — page index
- llms-full.txt — the full manual in one file
Quick start¶
- Download the template and save it as
CLAUDE.mdin your project root. - Replace the project name and stack. Leave the Moveris rules in place.
- Open Claude Code, or Cursor, in that project. The next session starts with those rules.
The template covers a project that integrates Moveris. It does not replace your own architecture notes. Add those under the project identity section.
Rules the template enforces¶
- Store the Moveris API key and the Meet bot key in environment variables. Do not commit them.
- Do not send either key from client-side code. The browser or the app calls your backend; your backend calls Moveris.
- For React, use
@moveris/react4.1.3 with@moveris/shared4.1.2. For React Native, use@moveris/react-native4.1.2 with@moveris/shared4.1.2. Default model:mixed-30-v3_1_1. - For a video meeting, create a Meet session with
POST /api/sessionsandmodelset to a Mixed V3.1.1 alias. - Decide access from a server-side verdict, not from a result the client claims.
Related¶
- Vibe Coder Guide — prompts to paste into Claude, Cursor, and similar agents
- SDK Installation — packages and peer dependencies
- Meet Quick Start — first session
- Credentials — bot API key and Moveris API key