Can I export my Claude Cowork projects and import them into Kortix?

No. Anthropic stores Cowork sessions and files with your Claude account, and there is no portable export that another product can read. You rebuild each project as agent, skill and memory files in the repo.

Do I have to rebuild everything by hand?

You write the agent and skill files, and an agent can help draft them from what the project already does. The work is one file per agent plus the kortix.yaml block, not a new application.

Will switching change which models I can use?

Kortix accepts any model provider with your own keys, or the ChatGPT plan you already pay for, or you sign in with your OpenCode Console account for OpenCode Zen and Go.

Does an agent merge its own work after the move?

No. Work reaches main through a change request a person approves. Merge is default-deny for agents, and a session can never merge the change request it opened itself.

How to migrate from Claude Cowork to an open source stack

Moving off Claude Cowork means taking the work that lives in your Claude account and rebuilding it as files in a git repo you own. Kortix is the open-source AI Operating System, and this is the order that avoids rework: inventory, repo, model keys, connectors, first session.

Try Kortix

§ 01Quickstart

The target layout, from the Kortix docs

FIG 1project treeTEXT

project: a git repo with kortix.yaml at its rootagents/   skills/   memory/session: one agent in its own sandbox on a new branchchange request: a person merges it into the default branch

Sourcekortix.com/docs

Everything Claude Cowork keeps in your account becomes files in this repo, and finished work reaches the default branch through a change request.

What moves when you leave Claude Cowork

Claude Cowork keeps your work with your Claude account. Anthropic’s help center says Cowork sessions run on Anthropic’s servers and that your sessions and files are saved to your Claude account, and it groups related tasks into projects with their own files, instructions and memory (Claude help center). There is no export file that carries all of that into another product, so a migration is a rebuild. The pieces you rebuild are the projects and their instructions, the memory each one holds, and the skills and plugins that shape how the work gets done.

In Kortix those pieces become files. Agents and skills are markdown in a git repo, company memory is files in the same repo, and kortix.yaml declares the machine image, connectors and triggers. The docs describe the model: a project is a git repo with kortix.yaml at its root, and the agents, skills, memory, tools, triggers and connectors are files in it (Kortix docs).

The migration, in order

Work in this order to avoid rework.

Inventory the work. List every Cowork project, the instruction set behind it, the memory it holds, and the plugins or skills it relies on.
Create the repo. Make one git repo for the company and add agents/, skills/ and memory/.
Rebuild each working agent as a file. Write the behavior as an agent markdown file and the governance as an agents.<name> block in kortix.yaml.
Move the memory. Copy what each project learned into the repo’s memory files, so the context survives the move.
Connect model keys. Any model provider with your own keys. Or the ChatGPT plan you already pay for. Or sign in with your OpenCode Console account for OpenCode Zen and Go.
Connect the tools. Agents reach 3,000+ apps in a click, plus MCP, OpenAPI, Postman, GraphQL and raw HTTP, and connector credentials are brokered server-side and never enter the machine.
Run the first session. Each session has its own isolated machine and branch, and session work reaches main through a change request you approve.

What replaces Cowork’s approval step

Cowork shows its plan and waits for your approval before anything significant. Kortix keeps a gate in the same place and makes it structural. An agent commits and pushes to its session branch, opens a change request, and a person merges it. Merge is default-deny for agents, and a session can never merge the change request it opened itself. The agent can hold broad tool access inside its sandbox, and the change request is where you keep control.

Where the migrated stack runs

You can run the migrated stack in more than one place. Run Kortix on Kortix Cloud, in your VPC, or on your own on-prem network, and self-host is free. The self-hosting guide covers the install on your own box, and Claude Cowork vs ChatGPT Work sets the closed products against the open one. For a worked comparison, Read the Kortix blog.

§ 03FAQ

Migration questions

Q01 Can I export my Claude Cowork projects and import them into Kortix?: No. Anthropic stores Cowork sessions and files with your Claude account, and there is no portable export that another product can read. You rebuild each project as agent, skill and memory files in the repo.
Q02 Do I have to rebuild everything by hand?: You write the agent and skill files, and an agent can help draft them from what the project already does. The work is one file per agent plus the kortix.yaml block, not a new application.
Q03 Will switching change which models I can use?: Kortix accepts any model provider with your own keys, or the ChatGPT plan you already pay for, or you sign in with your OpenCode Console account for OpenCode Zen and Go.
Q04 Does an agent merge its own work after the move?: No. Work reaches main through a change request a person approves. Merge is default-deny for agents, and a session can never merge the change request it opened itself.

Move your agents into a repo you own

Start with one job, then bring the rest of the work across.

Try Kortix See the self-hosting guide