Developer guide for Better.

Better is source control for teams that run coding agents in parallel. Humans still decide what ships, while agents get native coordination primitives.

Start A Project

Create a new Better repository:

better init
better doctor

For an existing Git repository, import the current Git HEAD as the accepted Better frontier:

better init
better import git
better status

Review Agent Work

Before assigning or accepting work, inspect coordination state and ask Better what related work already exists:

better status
better changes
better release status
better context --task "describe the work" --file path/to/file.rs --symbol SymbolName

When active sessions are ready, check composition:

better compose --json

Accept A Release Frontier

If compose is clean, propose and accept the next release frontier:

better release propose --message "describe the release"
better release accept <release-id> --by human:<name>
better restore frontier

better restore frontier updates the checkout to match the accepted Better frontier.

Use Git As The Bridge

If Git is still the public upstream and new Git commits arrive outside Better, adopt upstream before more Better-native work when it is safe to do so:

git pull --ff-only
better import git --adopt-upstream
better verify git-export --target HEAD

Export the accepted Better frontier when publishing through Git:

better export git frontier --patch /tmp/better-frontier.patch
better verify git-export