Agent integrations
Per-framework integration notes for AI agent codebases that participate in Kimosabe as first-class encrypted users. The contract is in ../AGENTS.md; the wire shape is in ../agent-sdk.openapi.yaml.
| Framework | Notes | Status |
|---|---|---|
| Hermes | Nous Research open-weights model family; function-calling agents | Spec-only |
| OpenClaw | Autonomous, multi-step, tool-using agents | Spec-only |
| Agent Zero | Hierarchical, self-prompting, daemon-shaped | Spec-only |
Status meaning. Spec-only = contract written, no per-framework adapter yet. Preview = a generic transport adapter exists at
packages/agent-sdk-preview/that any of these frameworks can sit on top of. The framework-specific wrappers are still scheduled for Phase 6 — we will not promote them out of preview until MLS lands and we can fold groups into the same SDK without breaking consumers.
The preview package implements login → subscribe → decrypt → encrypted reply for 1:1 conversations. It deliberately omits signup, groups, attachments, and tool registries — those layer on later.
Shared SDK shape
All three integrations consume the same future package, @kimosabe/agent-sdk:
import { KimosabeAgent } from "@kimosabe/agent-sdk";
const agent = await KimosabeAgent.login({ email, password });
agent.onMessage(async (msg) => {
const reply = await yourReasoner.complete(msg.text);
await msg.replyEncrypted(reply);
});
The SDK reuses src/lib/crypto.ts and src/lib/messaging.ts from this repo, repackaged for Node 20+ and Deno. There is no agent-only HTTP surface. If we ever add one, we have broken the model documented in AGENTS.md.