Unified quality + LSP tooling for Python, Rust, and TypeScript.
Agents don't just navigate code now — they check their own work as they go.
Multiple repos. LSP-only bundles with no quality tooling. No auto-checking. No expert agents. No composability. Every language was a silo.
Each one pairs semantic code navigation with quality tooling — so agents write code, verify it compiles, check formatting, and catch lint issues without leaving the loop.
Every language bundle follows the same composable architecture. Two specialized agents. Three behaviors you can mix and match.
Architecture exploration? Use just the LSP behavior. Quality gates without navigation overhead? Just the quality behavior. The composite is the default — but the pieces are yours to arrange.
| Behavior | What You Get | Use When |
|---|---|---|
{lang}-lsp |
LSP navigation, diagnostics, refactoring | Architecture exploration, code understanding |
{lang}-quality |
{lang}_check tool + auto-check hook |
Quality gates, CI-style validation |
{lang}-dev |
Both — the full dev experience | Day-to-day development DEFAULT |
# Install a bundle — pick your language
amplifier bundle use git+https://github.com/microsoft/amplifier-bundle-python-dev@main#subdirectory=behaviors/python-dev.yaml --app
amplifier bundle use git+https://github.com/microsoft/amplifier-bundle-rust-dev@main#subdirectory=behaviors/rust-dev.yaml --app
amplifier bundle use git+https://github.com/microsoft/amplifier-bundle-typescript-dev@main#subdirectory=behaviors/typescript-dev.yaml --app
Every time an agent writes or edits a file, the hook automatically runs quality checks and reports results inline. No extra step. No forgetting to check.
✗ 2 errors found
src/main.rs:42 error[E0308]: mismatched types
src/main.rs:87 error[E0599]: no method named `foo`
✓ No errors · 1 warning
src/lib.rs:12 clippy::unused_variable: unused `x`
✓ All checks passed (was: 2 errors, 1 warning)
Fixed 3 issues across 2 files
All language bundles build on the shared LSP base (amplifier-bundle-lsp). 14 operations, custom routing, persistent warm servers, and zero external Python dependencies.
expandMacro, relatedTests, externalDocs.Not toy examples. Real projects, real complexity, zero false positives.
Old bundles still work. They're now thin forwarding stubs that show a deprecation warning with migration instructions. No breakage — just a nudge.
# Old LSP-only bundles
amplifier bundle use amplifier-bundle-lsp-python
amplifier bundle use amplifier-bundle-lsp-rust
amplifier bundle use amplifier-bundle-lsp-typescript
# → Shows deprecation warning
⚠ lsp-python is deprecated.
Use python-dev for LSP + quality.
# New comprehensive dev bundles
amplifier bundle use amplifier-bundle-python-dev
amplifier bundle use amplifier-bundle-rust-dev
amplifier bundle use amplifier-bundle-typescript-dev
# → Full dev experience
✓ LSP + quality + agents ready
The entire project — from first commit to final test — was designed, implemented, and validated in a single Amplifier session.
All numbers in this deck were cross-referenced against cached bundle manifests, test file counts, and repository contents. Unverified claims are marked with qualifiers.
Pick your language. Install the bundle. Agents get quality feedback on every edit.
# Python (Active)
amplifier bundle use git+https://github.com/microsoft/amplifier-bundle-python-dev@main#subdirectory=behaviors/python-dev.yaml --app
# Rust (Experimental)
amplifier bundle use git+https://github.com/microsoft/amplifier-bundle-rust-dev@main#subdirectory=behaviors/rust-dev.yaml --app
# TypeScript + JavaScript (Experimental)
amplifier bundle use git+https://github.com/microsoft/amplifier-bundle-typescript-dev@main#subdirectory=behaviors/typescript-dev.yaml --app