fix(bundle): make root computer-use runnable (include foundation), matching sibling bundles - #2
Closed
Diego Colombo (colombod) wants to merge 1 commit into
Conversation
Diego Colombo (colombod)
force-pushed
the
fix/readme-install-root-bundle-name
branch
from
August 9, 2026 15:24
bc07553 to
26372aa
Compare
Diego Colombo (colombod)
changed the title
Diego Colombo (colombod)
force-pushed
the
fix/readme-install-root-bundle-name
branch
from
August 9, 2026 15:29
26372aa to
84f52c2
Compare
…unnable; align README The root bundle.md was missing the foundation include that every sibling capability bundle (terminal-tester, browser-tester, perplexity, recipes) has. This made the root bundle non-runnable, forcing installs to target the behavior manifest instead. Updated README.md to show the correct idiomatic flow: register the root bundle (which now has foundation), run it directly, and layer the behavior into existing bundles via includes: or --app. The behavior name (computer-use-behavior) is correct and follows the ecosystem convention for behavior manifests (amplifier-tester-behavior, terminal-tester-behavior, etc.). 🤖 Generated with [Amplifier](https://github.com/microsoft/amplifier) Co-Authored-By: Amplifier <240397093+microsoft-amplifier@users.noreply.github.com>
Diego Colombo (colombod)
force-pushed
the
fix/readme-install-root-bundle-name
branch
from
August 9, 2026 15:36
84f52c2 to
d4043ca
Compare
Diego Colombo (colombod)
changed the title
computer-use runnable (include foundation), matching sibling bundles
Author
|
Closing — this did not address the reported issue. Withdrawing to re-diagnose. |
Diego Colombo (colombod)
deleted the
fix/readme-install-root-bundle-name
branch
August 9, 2026 18:20
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Root cause
Sibling capability bundles all ship a runnable root
bundle.mdthat includes foundation + their own behavior:computer-use's root
bundle.mdomits foundation:So the root
computer-usebundle has no orchestrator/provider and is not runnable. That is whyamplifier run --bundle computer-use …(as the README instructed) failed, and why installs fell back to the behavior manifest — which registers under its metadata namecomputer-use-behavior, surfacing a confusing-behaviorentry inamplifier bundle list.The behavior's name is NOT the bug: a
-behaviorsuffix is the ecosystem convention for behavior manifests (e.g.amplifier-tester-behavior,terminal-tester-behavior,perplexity-research-behavior). The bug is the missing foundation include in the root bundle.Fix
bundle.md— add- bundle: git+https://github.com/microsoft/amplifier-foundation@mainto the rootincludes:(above the behavior), matching every sibling. Now the rootcomputer-usebundle is runnable and registers under the clean namecomputer-use.README.md— restore the idiomatic quickstart:amplifier bundle add …@main(root) +amplifier run --bundle computer-use "…"+amplifier bundle show computer-use. Add an authors' section showing how to layer the behavior into an existing bundle viaincludes:(and the--appapp-wide variant, noting it registers ascomputer-use-behaviorper convention).No behavior rename and no
--namealias hack — the clean name now comes from the root bundle the way it does for every other bundle in the ecosystem.