Claude Code · Codex
Your AI coding setup, on every machine.
One place to manage the skills, agents, MCP servers, and settings behind Claude Code and Codex. Scoped per project. Synced everywhere. Your API keys never touch our servers.
Cancel any time. Nothing to install to get started.
- github-mcp
- postgres-mcp
- test-writer skill
- code-reviewer agent
$ csc launch
Available this session:
- github-mcp
- postgres-mcp
- test-writer skill
- code-reviewer agent
You have four machines and one setup.
You configured Claude Code properly once. Then you got a new laptop, and a work desktop, and now three of them disagree.
Every project gets every tool.
Loading the whole toolbox into every session burns context and puts your client's credentials in your side project's directory.
The community moves under you.
You pulled in someone's skill pack six weeks ago. It updated. You found out on a Monday.
Configurator gives you one profile per project, and puts that profile on every machine.
You pick the skills, agents, and MCP servers a project should have. Every machine you work on sets itself up that way. Nothing else leaks in, and your API keys stay in your own password manager where we can't reach them.
One profile per project. Nothing bleeding between them.
A profile is a list: these skills, these agents, these MCP servers, these settings. That is what the project gets — all of it, and nothing else. The trading tools stay in the trading repo. The client's database stays in the client's repo. Your side project stops being a junk drawer.
Point a folder at a profile once and every session you start in it comes up the same way, on any machine.
- github-mcp
- postgres-mcp
- test-writer skill
- code-reviewer agent
$ csc launch
Available this session:
- github-mcp
- postgres-mcp
- test-writer skill
- code-reviewer agent
Change it once. It is everywhere.
Edit a profile on your phone at lunch; your desktop has it before you sit down. There is no repo to pull, no script to run, and no step where you remember to sync. A machine that has been off for a month catches up on its own the next time you start work — and if it has no network at all, it uses the last setup it knows and starts anyway.
Set it up once. Use it in Claude Code and Codex.
Every tool wants its configuration in a different place and a different format. You should not have to care. Write the profile once and we produce whatever each tool expects, in the right file, in the right directory, without disturbing anything you put there yourself.
New tools keep appearing. Adding one is our problem, not yours.
claude/mcp.json
{
"mcpServers": {
"postgres": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-postgres"],
"env": {
"DATABASE_URL": "${CSC_SECRET_9F2B7A0C1D3E4F5061A2}"
}
}
}
}codex/project.toml
[mcp_servers.postgres]
command = "npx"
args = ["-y", "@modelcontextprotocol/server-postgres"]
[mcp_servers.postgres.env]
DATABASE_URL = "${CSC_SECRET_9F2B7A0C1D3E4F5061A2}"How it works
Bring your setup in
Sign in and start from a template, or set up your existing skills, agents, and MCP servers by hand.
Build a profile per project
Pick the skills, agents, MCP servers, and settings each project should have. Map a folder to it.
Start working
Run csc launch. Your machine sets itself up exactly the way the profile says — and so does every other machine you own.
We never see your API keys. Ever.
Not encrypted at rest. Not briefly, in transit. Not in a log. We do not have a field to put them in.
Configurator stores the name of a key and where it lives — your password manager or your machine's keychain. When you start a session, your own machine fetches the value and hands it straight to the tool. It never passes through us.
Which means the worst-case version of a breach here is that someone learns you have a key calledproduction-db. That is the whole blast radius, and it is by design.
Bind once, works everywhere
Point a profile's credential slot at a key one time. Every machine resolves it locally, every time.
Your store, your rules
Your password manager or your OS keychain. Rotation, access logs, and expiry stay with the tool you already trust for that.
Nothing leaks into your repos
Keys never get written into project files, so nothing sensitive lands in a directory that a git add -A could catch.
Simple pricing
Pro
$5/month
Every feature the product has.
- Unlimited profiles
- Unlimited projects
- Unlimited machines
- Claude Code support
- Codex support
- Skills, agents, commands, and rules library
- MCP servers, scoped per project
- Plugins and marketplaces
- Pinned tool versions
- Per-project hooks and launch settings
- Sessions that do not step on each other
- Works offline
- Command-line agent
- Zero-custody secret bindings
- Machine and drift overview
- Health checks with one-click fixes
- Activity log
- Export everything, any time
- Email support
Genius
$7/month
Everything in Pro — and a little something extra.
- Everything in Pro
- The team gets a little more coffee.
- Our eternal gratitude, renewed monthly.
- A warm fuzzy feeling every time you open your terminal.
To be completely clear: Genius is identical to Pro. Same features, same limits, same everything. The extra $2 buys us coffee, not you capabilities. Pick it if you want to, and thank you — but nobody should upgrade expecting more product, because there isn't any.
Get startedPrices shown exclude tax; tax is calculated at checkout. Working as a team? Everyone runs their own $5account today, and shared workspaces are coming. Tell us what you need →
Frequently asked
What's the difference between Pro and Genius?
About $2. To be completely clear: Genius is identical to Pro. Same features, same limits, same everything. The extra $2 buys us coffee, not you capabilities. Pick it if you want to, and thank you — but nobody should upgrade expecting more product, because there isn't any.
Do you see my API keys?
No. We store the name of a key and where it lives — your password manager, your machine's keychain — and nothing else. When you start a session, your own machine fetches the value and hands it to the tool directly. There is no field in our database for a key, no endpoint that accepts one, and no version of this where we can hand one to anyone.
Which tools does it work with?
Claude Code and Codex, on macOS and Linux, from the command line.
Do I need to use a terminal?
For the command-line tools, you already are. A point-and-click way to run them is on the roadmap, but it isn't built yet, so we won't promise a button before it exists.
Can I cancel?
Any time, from your dashboard, in two clicks. Your plan runs to the end of the period you already paid for and then stops. We don't ask why, and you don't have to email anyone.