The same Claude Code setup on every device and in every repo
CodeByPlan keeps your Claude Code settings in one place and puts them where Claude Code reads them: on each of your computers, and in the repos of your organization.
What it manages
CodeByPlan starts with two things: settings.json and the statusline. Each can be set for you alone and for the projects of an organization.
For you
- Who decides
- You
- File
~/.claude/settings.jsonand your statusline- How it gets there
- The app writes it on each of your devices
For an organization and its projects
- Who decides
- People with the editor role or higher
- File
.claude/settings.jsonin each repo- How it gets there
- A commit to the repo, through GitHub
How it treats your files
You see a change before it is made
The app shows what will change in a file, line by line, before it writes.
You can undo
The app keeps the file as it was before each change, so you can go back.
Your own settings stay
The app changes only the settings it manages. Everything else in the file stays as you wrote it.
Repos work without the app
What is committed to a repo works for everyone who uses the repo, with or without CodeByPlan.
For organizations
An organization has projects, and a project has repos. People join by invitation and get one of four roles: viewer, editor, admin or owner. Where the organization or the project and a person set the same thing, the organization or the project wins. That is the order Claude Code itself uses.