Version 2 capability map

Version 2 keeps the connector-first, plugin-first model and one shared ToolManager. The new surfaces are incremental: choose the capabilities your application needs.

Need	V2 surface	Defaults and boundaries
Fresh, correctly bounded requests	Context preparation	One bounded preparation; connected tool groups and protected source results stay intact
Inspect execution failure and cancellation	Outcomes	Raw returns preserved; business `success: false` is ordinary data
Keep exact source behind a concise observation	Durable evidence	Disabled by default; stable scope and durable backend are explicit
Protect constraints and action receipts	Task state	Disabled by default; host updates and confirmations, no model mutation tools
Select plugin data and prompt layout	Selective assembly	Opt-in companions; protected data cannot be substituted
Reduce older read observations	Context strategies	Algorithmic remains default; masking/summaries require acknowledged evidence
Compose plugin and provider-native reduction	Native compaction	Opt-in `ContextCompactionStrategy`; endpoint/ownership/capacity restrictions apply
Route one managed execution	Model routing	No classifier call by default; selected identity stays fixed throughout the execution
Invoke helper models and share allowances	Helpers and ModelTask	Explicit tool-free helpers; budgets are process-local, with unknown usage/cost reported
Verify completion and bound recovery	Loop policies, verified routines	Opt-in host checks; a model answer is not proof of remote completion
Adopt a tested composition	Presets and inspection	`research` / `workflow`; permissions, helpers, and completion predicates remain explicit
Strengthen service reads and actions	Enhanced connectors, whole pages	Explicit profiles; legacy factories retain defaults
Carry authentic outcomes across hosts	Remote observations	Negotiated protocol; source receipts are reconciled without repeating uncertain actions
Fully configure agent teams	Factory orchestration	Complete host settings before initialization; no implied distributed budget authority
Swap entire harnesses	Agent Runtime preview	Five adapters; capability-gated policy/environment, separate live-validation limits
Select endpoint controls and presentation	Endpoint metadata, parameter policy, vendor presentation	Supported, unsupported, and unknown remain distinct

The existing strengths remain central: named multi-account connectors, OAuth, long-term entity/fact memory, working notes and whiteboard, tools and MCP, streaming, media, embeddings, Realtime, orchestration, and saved conversations. The Version 2 Guide retains detailed adoption/delivery records; the Changelog records release history.