Repository navigation
duobrain v0.1.1
duobrain v0.1.1
One person adds duobrain to the project, and the other only pulls and joins.
Changed
- Vendored install.
installcopies duobrain's runtime files (about 400KB, no dependencies) into
.duobrain/in the product repository and pins the release in.duobrain/VENDOR.json. It also writes
theAGENTS.mdblock, theCLAUDE.mdimport and a.gitattributesline that marks the folder as
vendored. Commit them once; the second person gets duobrain by pulling. - Joining.
init --participant <id>reads the participant pair from the shared record, so the second
person no longer repeats both IDs. Without shared state it fails before creating anything locally. - Updating. In a vendored project,
updateinstalls the newestvX.Y.Zrelease, or--ref vX.Y.Z,
and refreshesAGENTS.mdwith the new code. One person updates and commits; the other pulls. It only
moves to a newer version without--ref, and refuses to overwrite local edits in.duobrain/.
Why duobrain is vendored explains
the approach and its trade-offs. The global install from v0.1.0 (npm link, duobrain guide) still works.
Run
git clone --depth 1 --branch v0.1.1 https://github.com/slowspurt/duobrain.git /tmp/duobrain
cd /path/to/product
node /tmp/duobrain/bin/duobrain.js install
node .duobrain/bin/duobrain.js init --participants member-a,member-b --participant member-aThe other person, after pulling: node .duobrain/bin/duobrain.js init --participant member-b.
See Getting started.
Verification and limits
The suite contains 107 tests, including an end-to-end vendoring test: one clone installs and connects,
a second clone joins with only init --participant, and update installs a newer local release.
Release preparation also runs the three scenario checks against temporary Git repositories.
Actual acceptance with two people on separate machines and their existing AI tools remains pending.
Vendoring adds duobrain's files to the product repository; see the trade-offs in the vendoring guide.