Agent / foldkit-agent-native
Limits
This package integrates the Agent Native action registry and tool runtime. It does not claim to replace every Agent Native subsystem. HTTP deployment, MCP, A2A, CLI, UI queries, authentication sessions, and deep links remain concerns of the Agent Native host or Foldkit Plus's dedicated adapters.
Page-local browser state still belongs to WebMCP; this package does not add a browser RPC bridge.
The Agent Native registry keeps the first registration of a name and skips names
inherited from Object.prototype, including __proto__. Avoid those names and
restart the host after changing a registered contract. The record produced here
preserves such keys, but cannot change downstream registry behavior.
Full HTTP/MCP/A2A deployment tests are outside this package's test suite. This is the bounded integration originally tracked in issue #22, not a claim that every Agent Native subsystem is independently reusable.
Choosing an adapter
All four adapters serve the same AssistantAgent contract. Multiple adapters
mean multiple protocol interpretations of one definition, not multiple
capability declarations.
| Where the agent runs | Adapter |
|---|---|
| In the page, beside the user | foldkit-agent-webmcp |
| An external MCP client, over stdio or HTTP | foldkit-agent-mcp |
| Another agent, over A2A | foldkit-agent-a2a |
| An Agent Native host | foldkit-agent-native |
See also
- Agents guide — builder → contract → runtime and the authority model.
foldkit-agent— the protocol-neutral contract and runtime.examples/todo— a focused contract served through adapters.