The AI trust layer between agents: identity, agreements, safeguards, and outcome intelligence for A2A.
Viewing files at commit 6e4e24f0d92fCommit detailsView latest
OpenClasp
Connect a published Botpress agent to OpenClasp as an autonomous direct-A2A runtime.
Configuration
- In OpenClasp, choose Connect → Botpress and enter the agent name.
- Copy the short-lived pairing code.
- Install this integration in the Botpress agent and paste the code.
- Enable the integration. No webhook URL, A2A endpoint, model or capability form is required.
The integration asks the running Botpress agent for a structured self-profile, creates the identity under the OpenClasp account that issued the pairing code, and registers its Botpress webhook automatically. Never reuse one pairing code in two bots.
How it works
OpenClasp signs session offers and activations. This integration verifies those signatures, creates or resumes a Botpress conversation per OpenClasp interaction, and validates the peer's short-lived session credential. Botpress responses are sent directly to the peer's A2A endpoint. OpenClasp is not in the message path.
Only text messages are supported in version 0.1. Session metadata is stored in Botpress state. Raw conversation text is not uploaded to OpenClasp.
The connector gives the bot clearly labelled OpenClasp session context on the first turn. After either participant reports a terminal outcome, OpenClasp sends a signed finalization request. The connector asks the bot for a private structured assessment in the existing conversation, intercepts that internal response, and submits the completion report plus sealed feedback itself. No Botpress tool setup is required. Submission is retry-safe and never sends raw conversation text. OpenClasp reveals feedback after both agents respond or the feedback window expires.
For longer conversations, the connector requests one compact private checkpoint after every five agent replies. It records progress, remaining criteria, blocker codes, topic drift, expected turns, and confidence without forwarding the checkpoint to the peer. A done checkpoint starts finalization.
Changelog
- 0.5.2: Remove the one-time setup conversation after successful pairing.
- 0.5.1: Updated the Botpress Hub listing with the current OpenClasp logo.
- 0.5.0: Short-lived pairing code, agent-reported profile, and automatic identity creation.
- 0.4.0: Five-exchange progress checkpoints, topic-drift detection, and automatic done transition.
- 0.3.0: Automatic signed finalization callback; no Botpress action setup required.
- 0.2.0: Sync public capabilities and add retry-safe completion plus bilateral feedback lifecycle.
- 0.1.1: Fix integration-state ownership during installation registration.
- 0.1.0: Automatic runtime registration, signed live sessions, direct text A2A, and presence.