amplifier-core v1.0.12 – v1.0.13

Model Routing &
Provider Configuration

Configure everything. Share what matters. Keep credentials personal.

Active — Shipped
March 2026
The Problem

One size fits nobody

🔒
Rigid Provider Config
One instance per provider. Want fast Sonnet and deep Opus from the same provider? Tough luck.
👥
No Team Sharing
Routing config lived in one place. Teams couldn't share routing via git while keeping API keys personal.
⚙️
Matrix Rigidity
Built-in routing matrices only. No cloning, no customization, no per-candidate config like reasoning effort.
Feature 1

Settings scope support

Configure providers and routing at any level. The right config in the right place.

Global

Personal defaults and API keys. Follows you everywhere. Never committed to git.

Project

Team routing config lives in the repo. Share preferred matrices and provider setups via git.

Local

Per-checkout overrides. Experiment without affecting anyone. Gitignored by default.

# Interactive scope picker on every dashboard [w] Change scope Global | Project | Local
Feature 2

Multi-instance providers

Configure multiple instances of the same provider module, each with different settings.

Before

  • One Anthropic provider
  • One config set
  • Pick a model, live with it

Now

  • anthropic-fast → Sonnet, low latency
  • anthropic-reasoning → Opus, deep thinking
  • First-class kernel support for all instances
# Two instances, same provider module, different roles providers: anthropic-fast: module: anthropic model: claude-sonnet-4-20250514 anthropic-reasoning: module: anthropic model: claude-opus-4-20250514
Feature 3

Routing matrix editor

Clone any built-in matrix. Customize every role. Save as your own.

📋
Clone
Start from any existing matrix — balanced, quality, fast, local. Don't build from scratch.
✏️
Edit
Assign provider + model + per-candidate config to each role. Set reasoning_effort, enable_1m_context, and more.
💾
Save
Save as a named custom matrix. Share with your team via project scope.
Feature 4

Runtime config wiring

Per-candidate config flows end-to-end. Provider, model, and config are always a single unit.

Matrix YAML
→
Role Selection
→
{provider, model, config}
→
Provider Runtime
# Per-candidate config in the routing matrix roles: reasoning: candidates: - provider: anthropic-reasoning model: claude-opus-4-20250514 config: reasoning_effort: high enable_1m_context: true
Feature 5

Matrix detail view

Full candidate waterfall per role. See exactly what's active, what's fallback, and what's not configured.

Role: reasoning ● ACTIVE anthropic-reasoning / claude-opus-4-20250514 reasoning_effort: high, enable_1m_context: true ● FALLBACK openai-reasoning / o3 reasoning_effort: medium ● NOT CONFIGURED google-deepmind / gemini-2.5-pro provider not set up
Security

Locked down by default

26-Key Blocklist

Protected config keys that cannot be overridden at lower scopes. API keys, tokens, and secrets stay in global scope.

Path Traversal Guard

Config file paths are validated against traversal attacks. No reading outside sanctioned directories.

Correct Precedence

Scope merging follows strict rules. Local overrides project, project overrides global — but the blocklist always wins.

Fix

Provider scope merging — fixed

Multi-instance provider configs now merge correctly across all three scopes.

Before

  • Project-scope providers could shadow global ones entirely
  • Multi-instance configs got lost during merge
  • Unpredictable behavior across scopes

Now

  • Deep merge preserves all provider instances
  • Each instance merges independently
  • Deterministic precedence, always
Development Velocity

By the numbers

16
PRs Merged
5
Repositories
7
Major Features
2
Core Releases

amplifier-core v1.0.12 & v1.0.13 • Data provided by release author

Sources

Research Methodology

Data as of: March 8, 2026

Feature status: Active — shipped in amplifier-core v1.0.12 and v1.0.13

Data source: Summary provided directly by release author covering 16 PRs across 5 repos in the Amplifier ecosystem (amplifier-core, amplifier-foundation, amplifier-app-cli, amplifier-bundle-routing-matrix, amplifier-module-provider-vllm).

Metrics: PR count (16), repo count (5), feature count (7), and release versions (v1.0.12, v1.0.13) as stated by release author. No independent git log verification was performed for this deck.

Gaps: Individual commit counts, line changes, and contributor breakdown not available. Timeline (start/end dates) not provided.

Get Started

Try it now

Update to amplifier-core v1.0.13 and configure your routing your way.

# Update amplifier amplifier update # Open provider configuration amplifier settings providers # Open routing matrix editor amplifier settings matrix

github.com/microsoft/amplifier-core

More Amplifier Stories