Skip to content

chore(deps): require amplifier-agent 0.15.0 - #25

Merged
Salil Das (sadlilas) merged 1 commit into
mainfrom
chore/agent-floor-0.15.0
Aug 24, 2026
Merged

chore(deps): require amplifier-agent 0.15.0#25
Salil Das (sadlilas) merged 1 commit into
mainfrom
chore/agent-floor-0.15.0

Conversation

@sadlilas

Copy link
Copy Markdown
Contributor

Raises MIN_AGENT_VERSION to 0.15.0; AGENT_PINNED_REF and AGENT_HARD_FLOOR follow.

Why this floor moves. 0.15.0 is the first agent release that owns its own storage tree. It binds AMPLIFIER_HOME to ~/.amplifier-agent/foundation before importing amplifier_foundation, so module clones, provider rate-limit state and the ChatGPT OAuth token stop landing in ~/.amplifier — a directory owned by amplifier-app-cli and shared, with no per-application namespacing, with every other Amplifier application on the machine. On a host running both, they were reading and writing the same clone directories.

It also resolves floating @main module refs to concrete commits before preparing the bundle. Below this floor an install stays pinned to whatever main pointed at the day it was first set up, and no reinstall refreshes it — the reinstall rebuilds from the same frozen clone.

Upstream: microsoft/amplifier-agent#142, released as v0.15.0.

Also corrects a stale comment in tests/e2e/suites/onboarding/conftest.py that named the previous floor.

Cost: existing users are reinstalled onto v0.15.0 by the launch-time self-heal.

0.15.0 is the first version where the agent owns its own storage tree. It binds
AMPLIFIER_HOME to ~/.amplifier-agent/foundation before importing
amplifier_foundation, so module clones, provider rate-limit state and the
ChatGPT OAuth token stop landing in ~/.amplifier -- a directory owned by
amplifier-app-cli and shared, unnamespaced, with every other Amplifier
application on the machine. On a host running both, the two were reading and
writing the same clone directories.

0.15.0 also resolves floating @main module refs to concrete commits before
preparing the bundle, so an upstream module fix reaches an existing install.
Below this floor a machine keeps serving frozen module code that no reinstall
refreshes, because the reinstall rebuilds from the same frozen clone.

AGENT_PINNED_REF follows to v0.15.0, which is tagged and released upstream.
@sadlilas
Salil Das (sadlilas) merged commit 1d52f35 into main Aug 24, 2026
1 check passed
@sadlilas
Salil Das (sadlilas) deleted the chore/agent-floor-0.15.0 branch August 24, 2026 21:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant