aphrodite-hermes 1.3.2

aphrodite-hermes: Hermes Agent-specific integration for Aphrodite compression engine - tool schemas, hook dispatch, skill registration
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116

# aphrodite-hermes 🔌 Hermes Bridge

> **Hermes Agent integration layer - tool schemas, hook dispatch, skill registration.**

This crate is the bridge between the core `aphrodite` engine and the Hermes Agent
plugin system. It produces `libaphrodite_hermes.dylib` - loaded by the Python
plugin to register tools, hooks, and skills with Hermes.

[crates.io](https://crates.io/crates/aphrodite-hermes) ·
[docs](../../docs/README.md)

---

## Install

```bash
# From source (monorepo)
cargo build --release -p aphrodite-hermes

# From crates.io
cargo install aphrodite-hermes
```

---

## What it does

```
Hermes Agent
    │
    │  plugin load
    ▼
Python __init__.py (145 lines)
    │
    │  ctypes FFI
    ▼
libaphrodite_hermes.dylib  ← THIS CRATE
    │
    │  C ABI calls
    ▼
libaphrodite.dylib         ← Core engine
```

The bridge provides:

1. **Tool schemas** - 12 JSON Schema definitions for `aphrodite_*` tools
2. **Tool dispatch** - Routes Hermes tool calls to core engine functions
3. **Skill registration** - Bundled skills exposed to Hermes agents
4. **Hook dispatch** - Forwards hook calls (pre_llm, post_tool, etc.) to engine

---

## Architecture

```
src/
├── lib.rs          ← Universal dispatch: 5 hooks → Rust functions
├── tools.rs        ← 13 tool handler implementations
├── schemas.rs      ← JSON Schema for all tools
├── skills.rs       ← Bundled skill registration
```

---

## Tools

All 13 tools are registered as closures in one `tool_registry()` HashMap in
`src/tools.rs` (not separate per-tool modules) - full schemas and handler
behavior in [Tool Relay: Tools](../../docs/tool-relay/tools.md):

| Tool                        |
| :-------------------------- |
| `aphrodite_compress`        |
| `aphrodite_retrieve`        |
| `aphrodite_stats`           |
| `aphrodite_catalog`         |
| `aphrodite_search`          |
| `aphrodite_diff`            |
| `aphrodite_files`           |
| `aphrodite_directive`       |
| `aphrodite_test`            |
| `aphrodite_rebuild`         |
| `aphrodite_reclassify`      |
| `aphrodite_prefetch`        |
| `aphrodite_prefetch_status` |

`tool_registry()` also holds a 14th, internal-only entry -
`context_engine_pre_llm` - the context engine's pre-LLM hook, not a
Hermes-callable tool (it isn't in `plugin.yaml`'s `provides_tools`).

`aphrodite_diff` returns each turn's last-archived marker (`conv_index`),
populated by `hooks::post_llm_call` calling `session::archive_turn` at the
end of every turn (report 06 F11/T13 - previously `archive_turn` was dead
code with zero call sites, so this always returned `{"total": 0}`).

---

## Dependencies

- `aphrodite` - Core engine crate (path + version)
- `serde` / `serde_json` - JSON Schema + serialization

---

## See Also

- [Installing Aphrodite](../../docs/install/README.md) - which artifact you
  need, per-platform install guides, troubleshooting
- [Tool Relay: Tools](../../docs/tool-relay/tools.md) - full schema +
  handler behavior for all 13 tools this crate dispatches
- [Hermes Integration](../../docs/hermes-integration.md) - why a native
  plugin sees things a generic HTTP proxy can't

## License

CC0-1.0 - public domain.