Repository navigation
Expand file tree
/
Copy pathconfig.example.yaml
More file actions
86 lines (75 loc) · 2.52 KB
/
Copy pathconfig.example.yaml
File metadata and controls
86 lines (75 loc) · 2.52 KB
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
# Hermes Agent RS — Example Configuration
# Copy to ~/.hermes/config.yaml and adjust as needed.
# You can also override `model` and `base_url` via `HERMES_MODEL` and
# `HERMES_BASE_URL` in ~/.hermes/.env.
# Model in "provider/model" format. Bare model name defaults to OpenAI.
model: anthropic/claude-sonnet-4-20250514
# Max agent loop iterations per message.
max_iterations: 90
# Sampling temperature (0.0 - 1.0).
temperature: 0.7
# Terminal tool settings.
terminal:
timeout: 180 # Default command timeout (seconds)
max_timeout: 600 # Maximum allowed timeout
output_max_chars: 50000
# File tool settings.
file:
read_max_chars: 100000
read_max_lines: 2000
# Browser automation settings.
browser:
headless: true
sandbox: true
launch_timeout_secs: 20
action_timeout_secs: 30
# Dangerous command approval policy: ask | yolo | deny
approval:
policy: ask
# Optional Signet receipts for managed-agent tool calls.
# When enabled, Hermes signs each managed tool call and appends a local
# hash-chained audit record under ~/.hermes/signet by default.
# signet:
# enabled: true
# key_name: hermes-managed
# owner: hermes
# # dir: /absolute/path/to/signet-data
# MCP (Model Context Protocol) servers — auto-discovered at startup.
# mcp_servers:
# - name: filesystem
# command: npx
# args: ["-y", "@modelcontextprotocol/server-filesystem", "."]
# - name: remote-docs
# transport: http
# url: https://mcp.example.com
# headers:
# Authorization: "Bearer ${MCP_TOKEN}"
# Managed-mode MCP admission policy.
# This gates the currently admitted managed MCP slice:
# allowlisted HTTP read-only bridge tools only. Dynamic MCP tools,
# side-effect bridge tools, and stdio MCP remain blocked. The optional
# `stdio` subsection is only a candidate policy/audit surface for future
# admission; it does not enable managed stdio MCP by itself.
# managed:
# mcp:
# enabled: false
# allowed_transports: [http]
# allowed_servers: ["remote-docs"]
# allow_side_effects: false
# stdio:
# allowed_servers: ["filesystem"]
# allowed_env_keys: ["WORKSPACE_ROOT"]
# recovery:
# auto_replay_interrupted: false
# max_auto_replays_per_root_run: 3
# Gateway configuration (for `hermes gateway` command).
# gateway:
# session_idle_timeout_secs: 1800
# max_concurrent_sessions: 100
# telegram:
# token: "${TELEGRAM_BOT_TOKEN}"
# allowed_users: ["username1", "12345678"]
# # allow_all: true
# api_server:
# bind_addr: "127.0.0.1:8080"
# api_key: "${HERMES_API_KEY}"