codeloop_init_project
Bootstrap a project for CodeLoop. Auto-detects stack (Flutter / Web / Python / Ruby / Rails / Rust / .NET / Xcode) and emits .codeloop/config.json plus the agent rule files for Cursor and Claude Code.
When to use codeloop_init_project
Once per project, the first time CodeLoop is invoked. Auto-detects the stack and writes .codeloop/config.json + the rule files.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
| project_dir | string | no | Absolute path to the project root. Defaults to CODELOOP_PROJECT_DIR or cwd. |
| force | boolean | no | Overwrite existing config files. |
What you get back
Initialised file list, detected project type, recommended next-step tools.
Typical prompts that trigger it
Cursor + Claude Code call codeloop_init_project automatically when your prompt looks like one of these:
- “Set up CodeLoop in this project.”
- “Initialise CodeLoop here.”
FAQ
What does codeloop_init_project do?
Bootstrap a project for CodeLoop. Auto-detects stack (Flutter / Web / Python / Ruby / Rails / Rust / .NET / Xcode) and emits .codeloop/config.json plus the agent rule files for Cursor and Claude Code.
When should an AI agent call codeloop_init_project?
Once per project, the first time CodeLoop is invoked. Auto-detects the stack and writes .codeloop/config.json + the rule files.
What does codeloop_init_project return?
Initialised file list, detected project type, recommended next-step tools.
Is codeloop_init_project part of the CodeLoop MCP server?
Yes. CodeLoop ships as an MCP server installed via `npx codeloop init`. Cursor and Claude Code call it automatically once the User Rule (Cursor) or CLAUDE.md (Claude Code) is in place.