Migration

Bring your coding agent setup to Context Code

context-code reads the AGENTS.md, CLAUDE.md and Cursor rules already in your repositories, runs the same SKILL.md folders, and puts every session in your workspace task list.

Book a migration callCompare first
Q3 portfolio review deck Open in Drive Files Activity Share
You09:20

Build the Q3 review deck from the updates doc and the valuation bridge. Same structure as Q2, the three flagged companies up front.

Atlas09:20

Reading the Q3 updates and the bridge workbook, then drafting from the Q2 template.

Q3 portfolio review deck
Step 3 · 2 min 15 s
  1. Read q3-portfolio-updates.docx, 14 companies
  2. Read q3-valuation-bridge.xlsx, 3 scenarios
  3. Draft slides from the Q2 template, 18 slides
Send another message, it will be handled next
CAuto
ComputerConnected
Activity3Draft slides from the Q2 template
Q3 portfolio review deck Files Share
You09:20

Build the Q3 review deck from the updates doc and the valuation bridge. Same structure as Q2, the three flagged companies up front.

Atlas09:20

Reading the Q3 updates and the bridge workbook, then drafting from the Q2 template.

Q3 portfolio review deck
Step 3 · 2 min 15 s
  1. Read q3-portfolio-updates.docx, 14 companies
  2. Read q3-valuation-bridge.xlsx, 3 scenarios
  3. Draft slides from the Q2 template, 18 slides
Send another message, it will be handled next
CAuto

Why engineering teams move

Keep the repository files your agents already read. Hosted work runs in your own cluster, under approvals, and every run is scored.

ComputerConnected
Activity3Draft slides from the Q2 template
Q3 portfolio review deck Files Share
You09:20

Build the Q3 review deck from the updates doc and the valuation bridge. Same structure as Q2, the three flagged companies up front.

Atlas09:20

Reading the Q3 updates and the bridge workbook, then drafting from the Q2 template.

Q3 portfolio review deck
Step 3 · 2 min 15 s
  1. Read q3-portfolio-updates.docx, 14 companies
  2. Read q3-valuation-bridge.xlsx, 3 scenarios
  3. Draft slides from the Q2 template, 18 slides
Send another message, it will be handled next
CAuto

What our team does for you

Context engineers run the move with the people who own each workflow. Your team keeps its current tool until the moved work passes on real tasks.

Home

Fri, Sep 11 72°
RecentPinnedTasks
  • q3-portfolio-review.pptx1h ago
  • q3-valuation-bridge.xlsx2h ago
  • q3-portfolio-updates.docx3h ago
  • lp-letter.pptx5h ago
Working on Q3 portfolio review deck

Home

Fri, Sep 11 72°
RecentPinnedTasks
  • q3-portfolio-review.pptx1h ago
  • q3-valuation-bridge.xlsx2h ago
  • q3-portfolio-updates.docx3h ago
  • lp-letter.pptx5h ago
Working on Q3 portfolio review deck

What moves, and how

Everything your team has in Claude Code, Codex or Cursor, where it lands in Context, and who moves it.

Moves with a tool Context ships today

  • AGENTS.md, CLAUDE.md, .cursorrules and .cursor/rulesLoaded by context-code from the repositoryNo conversion. context-code loads one project file per session in this order: AGENTS.md, then CLAUDE.md, then Cursor rules. Where a repository has both AGENTS.md and CLAUDE.md, we merge them into AGENTS.md so nothing is skipped.
  • Skillscontext-code skill folders, and workspace skills for the teamClaude Code and Codex skills are SKILL.md folders. context-code reads extra skill folders listed in its config, and context-cli skill create shares a skill with the whole workspace.
  • Developer accountsPaired devices on the workspaceEach machine installs context-code with one command and pairs with a code. Every device has its own key you can revoke, and usage bills to the workspace.
  • People and seatsWorkspace members from your identity providerSign-in moves to your IdP over SAML or OIDC, and SCIM 2.0 provisions and removes people, so nobody is invited by hand.

Rebuilt by our team, by hand

  • MCP serverscontext-code config, or an organization connectorServer definitions are copied from .mcp.json or config.toml into context-code's config. Servers the whole team needs are registered once as organization connectors.

Before you start

Some things do not move. These are the ones to plan around.

What stays in Claude Code, Codex or Cursor

  • Your editor staysCursor is an editor and context-code runs in the terminal. Teams leaving Cursor's agent keep the editor they like and run context-code beside it.
  • Past sessions stay where they rancontext-code does not import session history from other tools. Sessions from the first paired run onward appear in the workspace task list.
  • Hooks and permission rules are rebuilt, not copiedClaude Code hooks, Codex exec policies and Cursor settings have no shared format. We review each rule with the engineer who owns it and set the context-code equivalent where one exists.

Bring to the first call

  • The repositories your team works in, and whether each uses AGENTS.md, CLAUDE.md or Cursor rules.
  • Your team's skill folders, from repositories or home directories.
  • The MCP servers in use, from .mcp.json, config.toml or Cursor settings.
  • Which machines need context-code, and which run Windows (context-code runs there through WSL 2).

Move into your own environment

Context runs in your own cloud or on your own hardware, so the skills, files and runs you move stay inside your deployment.

  • Files in your S3 or MinIO bucket
  • Self-hosted through KOTS
  • SAML and OIDC sign-in with SCIM
  • Air-gapped installation
How deployment works
  • Your cloud or hardwareFiles are stored in your S3 or MinIO bucket, in your cloud or on your own hardware.
  • Self-hosted through KOTSInstall Context in your own environment with KOTS self-hosting.
  • Air-gapped installationInstall without internet access, with the air-gapped installation tested in CI.
  • Your identity providerSign people in with SAML or OIDC and provision them with SCIM.

Context runs in production at Qualcomm. Read the case study

  • Amazon S3
  • MinIO
  • Your own hardware
  • Air-gapped

Questions

Do we have to rewrite AGENTS.md or CLAUDE.md?

No. context-code reads AGENTS.md, CLAUDE.md, .cursorrules and .cursor/rules/*.mdc from the working directory and discovers files in subdirectories as it works. It loads one project file per session, AGENTS.md first, so repositories with both files are merged once during the move.

Can we keep Claude and OpenAI models?

Yes. context-code runs Claude, GPT, Gemini and open-weight models from the same catalog your workspace uses, chosen per session.

Does context-code replace Cursor?

It replaces the agent, not the editor. context-code is a terminal agent, so engineers keep their editor and run it beside the code.

Does context-code run on Windows?

Through WSL 2: install WSL, open the Linux shell and run the same install command used on macOS and Linux.

Sources, last verified September 2026:

Compare first: Context Code vs Claude Code · Context Code vs OpenAI Codex

Plan your move from Claude Code, Codex or Cursor

Book a migration callCompare first

Moving from something else: Claude · ChatGPT