zeph 0.21.1

Lightweight AI agent with hybrid inference, skills-first architecture, and multi-channel I/O
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

# Daemon Mode

Run Zeph as a headless background agent with an A2A endpoint, then connect a TUI client for real-time interaction.

## Prerequisites

Daemon mode requires the `a2a` feature flag:

```bash
cargo build --release --features a2a
```

To connect a TUI client, build with `tui` and `a2a`:

```bash
cargo build --release --features tui,a2a
```

## Configuration

Run the interactive wizard to configure daemon settings:

```bash
zeph init
```

The wizard generates the `[daemon]` and `[a2a]` sections in `config.toml`:

```toml
[daemon]
enabled = true
pid_file = "~/.zeph/zeph.pid"
health_interval_secs = 30
max_restart_backoff_secs = 60

[a2a]
enabled = true
host = "0.0.0.0"
port = 3000
auth_token = "your-secret-token"
```

## Starting the Daemon

```bash
zeph --daemon
```

The daemon:

1. Writes a PID file for instance detection
2. Bootstraps a full agent (provider, memory, skills, tools, MCP)
3. Starts the A2A JSON-RPC server on the configured host/port
4. Runs under `DaemonSupervisor` with health monitoring
5. Handles Ctrl-C for graceful shutdown (removes PID file)

The agent uses a `LoopbackChannel` internally, which auto-approves confirmation prompts and bridges I/O between the A2A task processor and the agent loop via tokio mpsc channels.

## Connecting the TUI

From any machine that can reach the daemon:

```bash
zeph --connect http://localhost:3000
```

The TUI connects to the remote daemon via A2A SSE streaming. Tokens are rendered in real-time as they arrive from the agent. All standard TUI features (markdown rendering, command palette, file picker) work in connected mode.

### Authentication

If the daemon has `auth_token` configured, set `ZEPH_A2A_AUTH_TOKEN` before connecting:

```bash
ZEPH_A2A_AUTH_TOKEN=your-secret-token zeph --connect http://localhost:3000
```

## Architecture

```text
+-------------------+       A2A SSE        +-------------------+
|   TUI Client      | <------------------> |   Daemon          |
|   (--connect)     |     JSON-RPC 2.0     |   (--daemon)      |
+-------------------+                      +-------------------+
                                           | LoopbackChannel   |
                                           |   input_tx/rx     |
                                           |   output_tx/rx    |
                                           +-------------------+
                                           | Agent Loop        |
                                           | LLM + Tools + MCP |
                                           +-------------------+
```

The `LoopbackChannel` implements the `Channel` trait with two linked mpsc pairs:

- **input**: the A2A task processor sends user messages to the agent
- **output**: the agent emits `LoopbackEvent` variants (`Chunk`, `Flush`, `FullMessage`, `Status`, `ToolOutput`) back to the processor

The `TaskProcessor` translates `LoopbackEvent` into `ProcessorEvent::ArtifactChunk` for SSE streaming to connected clients.

## Daemon Management via Command Palette

When using TUI in connected mode, additional commands are available in the command palette (`Ctrl+P`):

| Command | Description |
|---------|-------------|
| `daemon:connect` | Connect to remote daemon |
| `daemon:disconnect` | Disconnect from daemon |
| `daemon:status` | Show connection status |