refactor: migrate tool progress configuration from environment variables to config.yaml

This commit is contained in:
teknium1
2026-02-28 00:05:58 -08:00
parent 0862fa96fd
commit de5a88bd97
9 changed files with 114 additions and 52 deletions

View File

@@ -325,14 +325,22 @@ TERMINAL_CWD=/workspace # All terminal sessions (local or contain
### Tool Progress Notifications
Get real-time updates as the agent works:
Control how much tool activity is displayed. Set in `~/.hermes/config.yaml`:
```bash
# Enable in ~/.hermes/.env
HERMES_TOOL_PROGRESS=true
HERMES_TOOL_PROGRESS_MODE=all # or "new" for only when tool changes
```yaml
display:
tool_progress: all # off | new | all | verbose
```
| Mode | What you see |
|------|-------------|
| `off` | Silent — just the final response |
| `new` | Tool indicator only when the tool changes (skip repeats) |
| `all` | Every tool call with a short preview (default) |
| `verbose` | Full args, results, and debug logs |
Toggle at runtime in the CLI with `/verbose` (cycles through all four modes).
---
## Commands
@@ -1568,8 +1576,6 @@ All variables go in `~/.hermes/.env`. Run `hermes config set VAR value` to set t
| Variable | Description |
|----------|-------------|
| `HERMES_MAX_ITERATIONS` | Max tool-calling iterations per conversation (default: 60) |
| `HERMES_TOOL_PROGRESS` | Send progress messages when using tools (`true`/`false`) |
| `HERMES_TOOL_PROGRESS_MODE` | `all` (every call, default) or `new` (only when tool changes) |
**Context Compression:**
| Variable | Description |