Skip to content

AMBER (ENGRAM) v1.5.13

Choose a tag to compare

View all tags
@JJHbrams JJHbrams released this 07 Sep 05:28
· 2 commits to master since this release
v1.5.13
736c334

Superseded by v1.5.14. This release decided ownership from its provenance record alone, so definitions deployed before that record existed were skipped and would never receive a future update. Take v1.5.14 instead — it keeps the protection and restores the updates.

Hotfix. Source only — no new installer. Install with the AMBER_1.5.12.661_x64-setup.exe asset on the v1.5.12 release; this release changes an installer-side script and carries no new binary.

Deploying the managed planner/coder/servant subagent definitions could destroy an agent of the same name that you had written yourself.

What went wrong

The deployer copied with -Force unconditionally. planner, coder, and servant are ordinary names — you may well own one already — and it was overwritten with no backup and no warning. Reproduced in an isolated profile before fixing it: a hand-written coder.md disappeared in a single deployment run.

What changed

  • The deployer records the SHA-256 of what it wrote in ~/.engram/agent-definitions.json, and replaces a file only when the file on disk still matches that record.
  • Anything else — a file you authored, or one of ours you have since edited — is skipped, and the skip is printed rather than passed over in silence. If your agent stops being picked up, the install log now says why.
  • One skipped file does not stop the rest. The other roles still deploy.
  • -Force still overwrites, but backs the file up to .engram-bak first. An irreversible action leaves a way back.

Nothing about the provider-specific formats or destinations changed: .md to ~/.claude/agents, .agent.md to ~/.copilot/agents, .toml to ~/.codex/agents.

Who was exposed

Installs and reinstalls run from source with INSTALL.ps1. The deployer was only ever invoked from modules/07_shims.ps1, so machines set up with the AMBER installer never took this path.

If you installed from source and had your own planner, coder, or servant definition, check whether it is still yours. There is no backup from before this fix — that is the defect.

Validation

The three new regressions were run against the pre-fix script: they fail there and pass after, so they count the cause rather than the symptom.

How to apply this hotfix

If you installed from source with INSTALL.ps1 — the only path that was affected:

cd <your checkout>
git pull
.\INSTALL.ps1

The deployer runs straight from the checkout, so there is nothing else to do.

If you installed with the AMBER installer — nothing to do. The deployer is invoked only from modules/07_shims.ps1, so an installed copy never took this path. The fix ships with the next installer release.

To deliberately reset the managed definitions to current:

.\installer\deploy_agent_definitions.ps1 -ProjectRoot . -UserProfile $env:USERPROFILE -Force

-Force backs each file up to .engram-bak before overwriting.

Assets 2
Loading