Conversation-Improvement

中文 | English | 日本語

A cross-agent visual-expression and persistent image-memory project for conversational AI. The project is not limited to Hermes Agent: its policy and image-library core are reusable, while each supported agent receives a native plugin adapter.

Features

• Explicitly generate a new image or retrieve an archived image.
• Store media with creation time, semantic tags, source, and SHA-256 identity.
• Reuse matching reaction media before generating anything new.
• Never regenerate a replacement when the user asks for an older image.
• Block automatic media in serious, coding, study, debugging, privacy, health, and distress contexts.
• Support a permanent character reference, a preset image/GIF directory, or explicit-request-only generation.
• Generate restrained chibi reactions with one subject, visible hand gestures, natural expressions, and a blank background.
• Keep API keys out of plugin configuration and avoid archiving raw prompts by default.

Architecture

Conversation-Improvement
├── shared policy engine
├── persistent image library
├── provider-independent generation/archive operations
└── native agent adapters
    ├── Hermes Agent
    ├── OpenClaw
    ├── ElizaOS
    ├── Open WebUI
    ├── Botpress
    └── other verified conversational plugin hosts

This project intentionally does not use MCP as its primary distribution layer. Complete visual conversation enhancement depends on host-native behavior: per-turn hooks, session state, image generation, and media delivery. A native plugin adapter can integrate those capabilities correctly.

Adapter contract

A full native adapter should map as many of these host capabilities as the host provides:

1. plugin lifecycle and persistent settings;
2. per-turn hook, event, or middleware;
3. tool registration;
4. image-generation provider dispatch;
5. image/GIF delivery to the active conversation;
6. per-conversation cooldown and usage state;
7. first-run setup UI or command.

A host can still receive a limited adapter when its plugin API lacks one capability, but the limitation must be documented instead of being presented as full compatibility.

Agent compatibility

Agent / host	Native extension mechanism	Project status
Hermes Agent	Native Python plugins, tools, hooks, commands	Implemented and tested
OpenClaw	Native TypeScript plugins, typed conversation hooks, tools, session attachments	Adapter implemented; SDK build and 3 behavior tests pass; real Gateway/channel acceptance pending
ElizaOS	Native plugins, events, providers, evaluators, actions, memories, media callbacks	Adapter implemented; TypeScript build and 6 behavior tests pass; live runtime/database/connector acceptance pending
Open WebUI	Native Filters (inlet/stream/outlet), Tools, Valves, message/file events	Adapter implemented; 5 tests, Python compilation, and wheel build pass; live Open WebUI acceptance pending
Botpress	Native hooks, integrations, actions, scoped state, image/video/file cards	Restricted native module implemented; official CLI type generation, TypeScript build, and 6 behavior tests pass; host Bot integration delivers prepared media payloads
Dify / LibreChat / Rasa / Flowise	Native extension surfaces exist, but at least one required universal hook/settings/media capability is limited	Limited integration only; not a full automatic-reaction target
Coding agents and hosts without a suitable native plugin API	Not a conversational native-plugin target	Not supported by Conversation-Improvement

“Planned” does not mean compatible today. An agent is marked supported only after its adapter is implemented and exercised against that host.

Native adapters

• adapters/openclaw — OpenClaw native TypeScript adapter
• adapters/elizaos — ElizaOS native TypeScript plugin
• adapters/open-webui — Open WebUI Filter/Tools Python adapter
• adapters/botpress — Botpress native module with host-integration media delivery boundary

Hermes Agent adapter

Hermes is the first completed adapter and currently provides configuration, generation, archive search, automatic-reaction policy injection, media archiving, and optional starter-pack generation.

hermes plugins install FirmaSpring/Conversation-Improvement --enable

Runtime data for the Hermes adapter is stored under:

$HERMES_HOME/conversation-improvement/

API keys are not stored in plugin configuration. The Hermes adapter can use a credential-pool reference or an environment-variable name. Generated and imported media remains local until the user deletes it.

Development

python -m pytest -q

New adapters should reuse the policy and library modules rather than duplicating behavior. Every adapter must document its host permissions, media-delivery behavior, storage location, and unsupported features.

License

MIT