polyc-tools 2026.8.3

The in-process tool core for polychrome agents: local executors (coding, web fetch, wallet, ...), the tool registry, and MCP composition. The networked connectors live in polyc-connectors.
docs.rs failed to build polyc-tools-2026.8.3
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.

Built-in tool executors for polychrome agents.

[ToolRegistry] is the in-process tool surface advertised every turn: the built-in core the model can call directly. Every tool — built-in or connector (dialed over MCP via [McpToolSource]) — is described by the same [ToolSpec] shape (name / description / schema / title + read_only / destructive annotations), so the model and the HITL approval gate treat them uniformly.

Layout

  • [ToolRegistry] — dispatches by tool name, implements [polyc_agent::ToolExecutor]. Pass it to run_turn.
  • [paid_fetch] — the advertised spec for the 402-gated payment fetch (offered only when a wallet is configured; always approval-gated). Like web_fetch, it is advertise-only here — the settlement executor lives in polyc-connectors, and the harness payment proxy owns it in production.
  • [mcp_client] — dial external MCP connectors and compose them with the built-ins ([CompositeRegistry]).
  • [peer] — the advertised spec for peer_call, delegating to another agent over A2A (offered only for the deployment's configured peers; always approval-gated). Advertise-only, like paid_fetch — the harness's peer-call proxy owns dialing the peer.
  • [conversation] — the advertised specs for reading this conversation's own committed record: find a moment, read a turn, read a recorded tool result, list recent turns, list tool calls. Advertise-only; the control plane runs each call trusted-side, over two backends the model never has to know about.