hyphae-cli 0.2.1

Single-binary CLI, server, verifier, and MCP adapter for Hyphae.
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

<p align="center"><a href="https://hyphae.dev"><img alt="Hyphae" src="https://raw.githubusercontent.com/celiumsai/hyphae/main/.github/assets/hyphae-lockup.svg" width="320"></a></p>

# hyphae-cli

[![crates.io](https://img.shields.io/crates/v/hyphae-cli?logo=rust)](https://crates.io/crates/hyphae-cli)
[![GitHub release](https://img.shields.io/github/v/release/celiumsai/hyphae?logo=github)](https://github.com/celiumsai/hyphae/releases/latest)

The single `hyphae` executable: local data engine, operations CLI, `/v1`
server, remote client, offline proof verifier, and MCP stdio adapter.

The command below is valid only after crates.io lists version `0.2.1`:

```bash
cargo install hyphae-cli --version 0.2.1 --locked
hyphae version --json
```

The base deployment is one binary and one data directory. KV, structured
query, recovery, backup/restore, and verification work without an external
database, cache, cloud, embedding provider, or LLM.

Remote request/proof JSON and bearer-token inputs are byte bounded before
decoding. Named files are metadata-preflighted, read through one detection byte
past their limit, and rejected when a regular file's observed length changes.
The remote CLI's 4 MiB request and 32 MiB proof JSON ceilings are fixed; it
does not negotiate larger custom-server values from capabilities.

Apache-2.0. Quickstart, release verification, and security policy:
[`celiumsai/hyphae`](https://github.com/celiumsai/hyphae).