Agent framework maintainers
Not in the preview yet. This feature is built in the repository but is off in the v2.2.6 preview (test mode). Do not treat this page as available on a preview core. See ../preview.md and the release notes.
Status: Live in Control Mode.
A framework plugin gives every agent in an app its own capped slice of one budget: a hand-off or sub-agent opens a child slice that never exceeds what its parent has left, and a call over the slice is refused before the model is called. The plugins built so far are listed in Add Dynamo to an agent framework.
The interface
Two agents layers do the work, so a plugin is a thin adapter:
- TypeScript:
@dynamoprotocol/agents0.3.0 - Python:
dynamoprotocol0.6.0 (thedynamoprotocol.agentsmodule)
A plugin implements one of two adapter profiles:
- Per call, for frameworks that see each model call: reserve the
call's worst case, settle the real cost.
- Spawn-scoped, for frameworks that report cost per agent run: reserve
the run's budget before launch, settle from the reported cost, rounded up.
The conformance suite
The suite is written once and shared by every plugin, in Python and as a TypeScript twin. It runs offline against a local core in Control Mode with a scripted mock model, so no model provider key is needed.
| Profile | Scenarios |
|---|---|
| Per call (9) | containment, sub-agent, cancel, rate envelope, unknown model, chain tamper, freeze, approval, amendment |
| Spawn-scoped (6) | containment, over-report, cancel, freeze, approval, chain tamper |
Suites: make test-conformance-ts (the TypeScript twin with reference adapters), make test-agents-ts, make test-py-sdk, make test-py-agents, and one test-plugin-… target per plugin.
Mocks today
Everything runs in Control Mode with a scripted model. No framework vendor access is needed.
Certification steps
- Every scenario of the plugin's profile green.
- The plugin's own test target green, with a coverage floor of 80 percent
on Python plugins.
- The framework version pinned and recorded with the date checked.