Repository navigation
duobrain v0.1.4
duobrain v0.1.4
Updating duobrain now takes one step for the person who updates and none for their partner beyond a
pull: update commits the new copy, and the partner is told to pull until both run the same version.
Changed
updatecommits the vendored copy. After replacing.duobrain/, it commits only that folder (and
any agent file it rewrote) aschore: update duobrain to vX.Y.Z. Anything else you had staged stays
staged and out of the commit. Push as usual.--no-commitskips the commit, and if a commit hook fails
the files are left ready to commit by hand.AGENTS.mdstops changing between releases. For a vendored copy the product'sAGENTS.mdblock is
now a fixed pointer to.duobrain/AGENTS.md, and the agent instructions travel inside.duobrain/.
The block changes once, on the update to v0.1.4, and then stays the same.- The newest code finishes every update.
updatehands over to the newly installed code
(update-finish), so later releases can change how updates are finished without waiting a version.
Added
- Your partner is told to pull. Each update is added to the work record (
tool.updated). Until the
partner runs the same version, their dashboard showsMina updated duobrain to vX.Y.Z. Pull the project…with the update commit, and their AI seesduobrainUpdateinstatus --brief. Pulling makes
it disappear; there is nothing to answer or close. With an own duobrain checkout instead of
.duobrain/, the notice says to update rather than pull. - The dashboard's update result shows the commit to push, notes that the partner will be told, and,
when the partner already updated, suggests pulling instead of updating a second time. - Snapshot
toolslists each participant's latest recorded version;GET /api/metaalso reports whether
the running copy is vendored.
Upgrading from v0.1.3 or earlier
The update to v0.1.4 itself still runs your current version's code, so commit it once by hand:
node .duobrain/bin/duobrain.js update
git add .duobrain AGENTS.md && git commit -m "chore: update duobrain to v0.1.4"
git pushFrom v0.1.4 on, update commits and notifies on its own. Engines before v0.1.4 ignore the new
tool.updated records, so a partner still on an older version keeps working; they only see the notice
once they run v0.1.4 or later.
Verification
The suite contains 113 tests. The vendored end-to-end test installs a release, updates it, checks that
only .duobrain/ is committed while an unrelated staged file stays staged, that AGENTS.md is unchanged,
and that the partner's status --brief reports the update after sync and drops it after pull.