Summary
The Install block in README.md is internally inconsistent. Step 1 registers the behavior sub-bundle (name computer-use-behavior), but step 2 — and the verification/troubleshooting lines — reference the root bundle name computer-use, which that step never registers. Following the README verbatim ends in Error: Bundle 'computer-use' not found.
Repo: microsoft/amplifier-bundle-computer-use @ eb26715 (main)
amplifier: 2026.08.05-5462f1e (core 1.6.1), Linux
Symptom (verbatim)
✓ Added app bundle 'computer-use-behavior'
URI: git+https://github.com/microsoft/amplifier-bundle-computer-use@main#subdirectory=behaviors/computer-use.yaml
$ amplifier run --bundle computer-use "What's on my screen right now?"
Error: Bundle 'computer-use' not found. Available bundles: ... computer-use-behavior ...
Step 1 confirms the registered name is computer-use-behavior; the error's own "Available bundles" list contains computer-use-behavior but not computer-use.
Root cause
The repo ships two manifests with two names:
| File |
Line |
Declared name |
bundle.md (root) |
bundle.md:3 |
computer-use |
behaviors/computer-use.yaml |
behaviors/computer-use.yaml:2 |
computer-use-behavior |
README.md:43-51:
43 # 1. Register it (the name "computer-use" comes from this repo's own bundle.md)
44 amplifier bundle add git+.../amplifier-bundle-computer-use@main#subdirectory=behaviors/computer-use.yaml --app
47 amplifier run --bundle computer-use "What's on my screen right now?"
51 Confirm ... `amplifier bundle show computer-use` ...
The line-43 comment says the name comes from bundle.md, but the line-44 command adds behaviors/computer-use.yaml — whose name is computer-use-behavior. --bundle resolves by registered name, so lines 47/51 (and the trace example at README.md:289) reference a name step 1 never registers.
Fix (maintainer picks — depends on intended --app UX)
Option A — register the root bundle, keep --bundle computer-use (matches the line-43 comment):
- amplifier bundle add git+https://github.com/microsoft/amplifier-bundle-computer-use@main#subdirectory=behaviors/computer-use.yaml --app
+ amplifier bundle add git+https://github.com/microsoft/amplifier-bundle-computer-use@main --app
The root URI resolves bundle.md (name: computer-use), which includes the behavior, so steps 2 and the confirm line then work unchanged.
Option B — keep the behavior subpath, correct the name in run/confirm/trace lines:
- amplifier run --bundle computer-use "What's on my screen right now?"
+ amplifier run --bundle computer-use-behavior "What's on my screen right now?"
Note: an --app bundle is auto-composed into every session, so --bundle may be unnecessary in step 2 under this model. The local-clone variant at README.md:53 points at the repo root and likely already avoids this bug — a hint the GitHub line was meant to point at the root too.
Verification note (honest)
Directly verified: the two manifests declare the two different names; the user paste shows step 1 registering computer-use-behavior; --bundle matches by registered name. Not verified: a from-clean end-to-end re-run of Option A (on the investigation machine the root computer-use bundle was already registered by other means, so the pristine "not found" state could not be reproduced without disturbing the environment). Recommend a clean re-run of the chosen fix before merging.
Summary
The Install block in
README.mdis internally inconsistent. Step 1 registers the behavior sub-bundle (namecomputer-use-behavior), but step 2 — and the verification/troubleshooting lines — reference the root bundle namecomputer-use, which that step never registers. Following the README verbatim ends inError: Bundle 'computer-use' not found.Repo: microsoft/amplifier-bundle-computer-use @
eb26715(main)amplifier:
2026.08.05-5462f1e(core1.6.1), LinuxSymptom (verbatim)
Step 1 confirms the registered name is
computer-use-behavior; the error's own "Available bundles" list containscomputer-use-behaviorbut notcomputer-use.Root cause
The repo ships two manifests with two names:
namebundle.md(root)bundle.md:3computer-usebehaviors/computer-use.yamlbehaviors/computer-use.yaml:2computer-use-behaviorREADME.md:43-51:The line-43 comment says the name comes from
bundle.md, but the line-44 command addsbehaviors/computer-use.yaml— whosenameiscomputer-use-behavior.--bundleresolves by registered name, so lines 47/51 (and the trace example atREADME.md:289) reference a name step 1 never registers.Fix (maintainer picks — depends on intended
--appUX)Option A — register the root bundle, keep
--bundle computer-use(matches the line-43 comment):The root URI resolves
bundle.md(name: computer-use), whichincludesthe behavior, so steps 2 and the confirm line then work unchanged.Option B — keep the behavior subpath, correct the name in run/confirm/trace lines:
Note: an
--appbundle is auto-composed into every session, so--bundlemay be unnecessary in step 2 under this model. The local-clone variant atREADME.md:53points at the repo root and likely already avoids this bug — a hint the GitHub line was meant to point at the root too.Verification note (honest)
Directly verified: the two manifests declare the two different names; the user paste shows step 1 registering
computer-use-behavior;--bundlematches by registered name. Not verified: a from-clean end-to-end re-run of Option A (on the investigation machine the rootcomputer-usebundle was already registered by other means, so the pristine "not found" state could not be reproduced without disturbing the environment). Recommend a clean re-run of the chosen fix before merging.