AI profiles, in step with you
Your AI should know which hat you’re wearing.
AIP (AI Profiles - pronounced "ape") keeps separate instructions, skills and settings for work, personal projects and clients — then brings the right one with you to Claude Code, Codex, Pi or OpenCode.
One person, more than one context
Keep each way of working unmistakably yours.
When you switch from a client project to your own code, your agent should switch with you. AIP gives each context its own profile: a simple home for the instructions, skills and harness settings that belong together.
All of those profiles live in one ordinary Git repository. Connect a remote once and they stay available, intact and in sync across your machines.
AIP is deliberately uncomplicated
A shared kit for every AI harness.
A profile is just a folder. Its AGENTS.md holds the common instructions; its skills/ directory holds the practices you want every compatible harness to use. AIP adds each harness’s native configuration around that shared core.
There is no translation layer to maintain and no new service to trust. Your profile repository is yours — Git-backed, portable, and readable without AIP.
A good first ten minutes
Install once. Then make your first profile.
You need Node.js 18+ for installation, Git with your name and email configured, and at least one of the AI tools you already use. AIP works on macOS, Linux, WSL and native Windows.
-
1
Install AIP
Use the same command in Bash, Zsh or PowerShell. Restart your shell when it finishes.
npx -y @code-ministry/aip@latest install -
2
Create your everyday profile
Give it a name. AIP creates its shared instructions, skills and settings structure for you.
aip create work
aip default work -
3
Bring it to every machine
Connect a Git remote. On a second machine, install AIP and add the same remote — your profiles arrive with their links and permissions intact.
aip remote add [email protected]:you/aip-profiles.git
Then work normally
The profile comes along quietly.
Choose a default profile, set one for the current shell, or pin one to a project. Then launch the harness exactly as you normally would. AIP selects the right profile and checkpoints changes before and after each run.
See every way to choose a profileyour-project
aip local client-acme
# now launch the tool as usual
codex
✓ client-acme selected for this project
The practical bits are covered.
- One source of truthInstructions and skills are edited once, then seen by each harness in its native place.
- Safe by defaultAIP refuses to sync recognised credentials, sessions, caches and private keys.
- Works offlineIf your remote is unavailable, your committed local profile still launches. Sync retries next time.