Best way to integrate Cursor into an existing VS Code repo with Claude Code + Codex-style multi-agent workflow and automation?

Support Help
, ,
14

Hey, thanks for the detailed breakdown. This workflow maps to Cursor pretty well. I’ll stick to the key points.

Integration of the repo and governance files

  • Just open the same local folder in Cursor. It’s a VS Code fork, so you don’t need to migrate anything.
  • Cursor automatically reads AGENTS.md in the repo root and also any nested ones in subfolders. It can also pick up CLAUDE.md and .claude config. So your instructions stay consistent across Cursor, Claude Code, and Codex as one shared layer.
  • For governance rules, use .cursor/rules/*.mdc with frontmatter that controls when a rule loads: alwaysApply: true for rules that must always be in context, globs: to load only when specific files are touched, and description: to help relevance-based loading. Docs: Rules | Cursor Docs
  • Important: don’t make a big todo-Codex.md an always-apply rule. It burns context every turn. Keep it as a normal file the agent reads or greps only when needed, and handle one item per session so context doesn’t drift.

Loop planning to implement to audit
This works natively:

  • Plan mode is a read-only phase for research and planning before any edits.
  • Custom agents or subagents in .cursor/agents/*.md. You can set up planner, implementer, and auditor, each with its own prompt and its own model. The parent agent can spawn a reviewer subagent on a different model. That gives cross-model critique so the model doesn’t just rubber-stamp its own output. Docs: Subagents | Cursor Docs
  • Hooks in .cursor/hooks.json to auto-run tests or lint after edits, do checks before submit, and block quiet removal of functionality.
  • Bugbot as an independent PR reviewer, a second audit layer.
  • Approval gates: keep auto-run turned off for risky commands, or use allow and deny lists, so dangerous changes require explicit approval.

Leland_Hepworth described this exact pattern with a linter subagent in comment 9, it’s a solid practical example. Also check these community threads: [Guide] Thin Self-Review Hooks for Cursor | The Model Is the Auditor (Windows + Linux) and How are people handling context across different AI coding tools?.

About using external Claude Code and Codex as extra auditors
Honestly, Cursor doesn’t fully orchestrate independent external Claude Code or Codex CLI as part of its loop. They stay separate tools you run yourself. What Cursor does give you is the shared instruction layer AGENTS.md and CLAUDE.md, so all three layers follow the same rules. If you want a second external audit after the internal Cursor loop, you’ll need to run it manually or via your own script on top of the PR.

Watch points

  • Context: keep always-apply rules lightweight, and load big files only on request. Long single sessions get summarized and lose detail, so do one todo item per session.
  • Background or Cloud agents can work for autonomous runs, but give them strict rules plus verification hooks plus a PR gate. Also note Free tier has limits for Cloud or Background agents, but rules, AGENTS.md and CLAUDE.md, Plan mode, subagents, hooks, commands, and MCP are available.

Let me know if you want to go deeper on any of these points.