pond-db 0.8.0

Lossless storage and hybrid search for sessions from any AI agent client
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

---
source: src/main.rs
expression: sub.render_long_help().to_string()
---
Run the HTTP API server (or MCP over stdio with --transport stdio).

Serves the wire protocol over HTTP on --host:--port. Most agent setups want `pond mcp` instead; `serve` is for the HTTP transport and for supervised deployments.

Usage: pond serve [OPTIONS]

Options:
      --transport <TRANSPORT>
          Wire transport: the HTTP API, or MCP over stdio
          
          [default: http]
          [possible values: http, stdio]

      --host <HOST>
          Bind address for the HTTP transport
          
          [env: POND_HOST]
          [default: 127.0.0.1]

      --port <PORT>
          Bind port for the HTTP transport
          
          [env: POND_PORT]
          [default: 9797]

  -h, --help
          Print help (see a summary with '-h')

Global options:
      --storage-path <URL>
          Storage destination: a local path or remote URL.
          
          Accepts a bare path, `~/path`, `file://`, `s3://bucket/prefix`, `s3+https://host/bucket/prefix`, `gs://`, or `az://`. Default: `[storage].path` from config, then the platform data dir (`~/.local/share/pond`).
          
          [env: POND_STORAGE_PATH]

      --config <PATH>
          Config file to read (default: `~/.config/pond/config.toml`)
          
          [env: POND_CONFIG]

  -v, --verbose...
          Increase logging verbosity

  -q, --quiet...
          Decrease logging verbosity

Examples:
  pond serve                       HTTP on 127.0.0.1:9797
  pond serve --port 8080
  pond serve --transport stdio     same as `pond mcp`