0.11.2 aligns the Managed Research SDK with the current backend, which made
objectives, experiments, and milestones runtime-managed rather than directly
created and stepped through the SDK. If you were on 0.11.1 and called those APIs,
they returned 404 against the current backend; 0.11.2 removes them so the SDK
matches what the service actually supports.
Only code that called the objective/experiment/milestone lifecycle, the typed
open-ended-question / directed-effort-outcome helpers, connect-git, or project-scope
economics / resource-limits is affected. The core flow — create a project, start a
run, read results — is unchanged.
Install
What moved, and what to use instead
| If you used (0.11.1) | In 0.11.2 | Use instead |
|---|---|---|
create_objective / pause / resume / withdraw / request_review / *_claim / lifecycle | removed | Objectives are advanced by the runtime; you no longer step them by hand. |
list_objectives(project_id) | kept | unchanged |
get_run_work_graph(...) | kept | the run’s objective/work graph |
typed *_open_ended_question / *_directed_effort_outcome | removed | use the run brief; objectives are derived/managed at runtime |
| experiments CRUD + results | removed | experiment tracking is internal; read run outputs/artifacts |
| milestones CRUD + transition | removed | milestones are runtime-managed |
get_project_resource_limits / progress_toward / extend (project scope) | removed | run-scope resource-limit APIs (*_run_resource_limits, extend_run_resource_limit) |
get_project_economics | removed | project usage rollups (/usage) |
| connect-git (github / integrations) | removed | upload code bundles |
How removed calls behave
Removed methods are gone (not silently no-op). MCP tools for the removed surface are filtered out of the advertised registry; any retained compatibility shim fails loudly withunsupported_backend_contract rather than returning a misleading result.
If a call you relied on isn’t in the table above, check the package
CHANGELOG.