/config

View or modify the heartbeat daemon settings. Use $ARGUMENTS to determine the action.

Parse $ARGUMENTS to identify what the user wants. If no arguments are given, show the current config.

Sub-commands

show (default when no arguments)

1. Read .claude/hermes/settings.json.

2. Display all settings clearly:

   General

   • Model: (e.g. opus, sonnet, haiku, glm or "default")
   • API token: (first 5 chars + "..." or "not configured"; used when model is glm)
   • Fallback model: (e.g. glm, sonnet, or "not configured")
   • Fallback API token: (first 5 chars + "..." or "not configured")
   • Timezone: (e.g. America/New_York or "UTC")

   Heartbeat

   • Enabled: yes/no
   • Interval: Xm
   • Prompt: (show full prompt or "not set")
   • Exclude windows: (list each window's days + start-end, or "none")
   • Forward to Telegram: yes/no (HEARTBEAT_OK is forwarded only when enabled)

   Telegram

   • Token: (first 5 chars + "..." or "not configured")
   • Allowed users: (list IDs or "none")

   Security

   • Level: (locked/strict/moderate/unrestricted)
   • Allowed tools: (list or "default")
   • Disallowed tools: (list or "none")

3. Also list any cron jobs from .claude/hermes/jobs/ with their name and schedule.

4. Remind the user that changes are hot-reloaded every 30s — no daemon restart needed.

heartbeat on / heartbeat off / heartbeat enable / heartbeat disable

Toggle the heartbeat on or off.

1. Read .claude/hermes/settings.json.
2. Set heartbeat.enabled to true or false based on the command.
3. Write the updated settings back.
4. Confirm the change.

heartbeat interval <minutes> / interval <minutes>

Change the heartbeat interval.

1. Parse the number of minutes from $ARGUMENTS. If not provided or invalid, use AskUserQuestion: "How often should the heartbeat run?" (header: "Interval", options: "5 minutes", "15 minutes (Recommended)", "30 minutes", "60 minutes")
2. Read .claude/hermes/settings.json.
3. Set heartbeat.interval to the new value.
4. Write the updated settings back.
5. Confirm the change. The daemon will pick up the new interval within 30 seconds.

heartbeat prompt / prompt

Change the heartbeat prompt.

1. Read .claude/hermes/settings.json and show the current prompt.
2. Use AskUserQuestion: "What prompt should the heartbeat run?" (header: "Prompt", options: suggest 2-3 prompts relevant to the project, plus the current prompt if set as an option)
3. Set heartbeat.prompt to the new value.
4. Write the updated settings back.
5. Confirm the change.

heartbeat telegram on / heartbeat telegram off / heartbeat forward telegram on / heartbeat forward telegram off

Toggle whether heartbeat outputs are forwarded to Telegram.

1. Read .claude/hermes/settings.json.
2. Set heartbeat.forwardToTelegram to true for on and false for off.
3. Write the updated settings back.
4. Confirm the change.
5. Clarify behavior:
   • true = forward all heartbeat replies (including HEARTBEAT_OK)
   • false = suppress HEARTBEAT_OK and forward only actionable heartbeat outputs

telegram token <token> / telegram token

Set or update the Telegram bot token.

1. If token is in $ARGUMENTS, use it directly.
2. Otherwise, use AskUserQuestion: "What is your Telegram bot token from @BotFather?" (header: "Token", options: let user type via Other)
3. Read .claude/hermes/settings.json.
4. Set telegram.token to the new value.
5. Write and confirm.

telegram users <id1,id2,...> / telegram users

Set the allowed Telegram user IDs.

1. If IDs are in $ARGUMENTS, parse them as comma-separated numbers.
2. Otherwise, use AskUserQuestion: "What Telegram user IDs should be allowed? (comma-separated)" (header: "User IDs", options: let user type via Other)
3. Read .claude/hermes/settings.json.
4. Set telegram.allowedUserIds to the array of numbers.
5. Write and confirm.

telegram off / telegram disable

Disable Telegram integration.

1. Read .claude/hermes/settings.json.
2. Set telegram.token to "" and telegram.allowedUserIds to [].
3. Write and confirm.

model <name> / model

Set the Claude model to use for sessions.

1. If model name is in $ARGUMENTS, use it directly.
2. Otherwise, use AskUserQuestion: "Which Claude model should Claude Hermes use?" (header: "Model", options: "opus (default)", "sonnet", "haiku", "glm")
3. Read .claude/hermes/settings.json.
4. Set model to the new value.
5. If the selected model is glm, ask for api token (unless already set) and save it to top-level api.
6. If model is changed away from glm, keep api unchanged.
7. Write and confirm.

api <token> / api

Set or update the API token used when model is glm.

1. If token is in $ARGUMENTS, use it directly.
2. Otherwise, use AskUserQuestion: "What API token should Claude Hermes use for glm?" (header: "API token", options: let user type via Other)
3. Read .claude/hermes/settings.json.
4. Set top-level api to the new value.
5. Write and confirm.

fallback model <name> / fallback model

Set the fallback model used when the primary model hits a rate limit.

1. If fallback model name is in $ARGUMENTS, use it directly.
2. Otherwise, use AskUserQuestion: "Which fallback model should Claude Hermes use?" (header: "Fallback model", options: "glm (Recommended)", "sonnet", "haiku")
3. Read .claude/hermes/settings.json.
4. Set fallback.model to the chosen value ("" for none).
5. Write and confirm.

fallback api <token> / fallback api

Set or clear the API token for the fallback model.

1. If token is in $ARGUMENTS, use it directly.
2. Otherwise, use AskUserQuestion: "What API token should Claude Hermes use for fallback model?" (header: "Fallback API token", options: let user type via Other)
3. Read .claude/hermes/settings.json.
4. Set fallback.api to the new value.
5. Write and confirm.

timezone <tz> / timezone

Set the IANA timezone (e.g. America/New_York, Europe/London, UTC).

1. If timezone is in $ARGUMENTS, use it directly.
2. Otherwise, use AskUserQuestion: "What timezone should Claude Hermes use?" (header: "Timezone", options: "UTC (Recommended)", "America/New_York", "Europe/London")
3. Read .claude/hermes/settings.json.
4. Set timezone to the new value. The timezoneOffsetMinutes will be auto-resolved from the timezone name.
5. Write and confirm.

security level <level> / security

Set the security level for Claude sessions.

1. If level is in $ARGUMENTS, validate it is one of: locked, strict, moderate, unrestricted.
2. Otherwise, use AskUserQuestion: "What security level should sessions use?" (header: "Security", options: "locked — Read/Grep/Glob only", "strict — No Bash/WebSearch/WebFetch", "moderate — All tools, project-scoped (Recommended)", "unrestricted — All tools, no restrictions")
3. Read .claude/hermes/settings.json.
4. Set security.level to the new value.
5. Write and confirm. Explain what the chosen level permits.

security tools allow <tool1,tool2,...> / security tools disallow <tool1,tool2,...>

Add tools to the allowed or disallowed lists.

1. Parse comma-separated tool names from $ARGUMENTS.
2. Read .claude/hermes/settings.json.
3. Append to security.allowedTools or security.disallowedTools (deduplicated).
4. Write and confirm.

reset

Reset all settings to defaults.

1. Use AskUserQuestion: "Reset all settings to defaults? This will disable heartbeat and clear Telegram config." (header: "Confirm", options: "Yes, reset everything", "No, keep current settings")
2. If confirmed, write the default settings:

   {
     "model": "",
     "api": "",
     "fallback": {
       "model": "",
       "api": ""
     },
     "timezone": "UTC",
     "timezoneOffsetMinutes": 0,
     "heartbeat": {
       "enabled": false,
       "interval": 15,
       "prompt": "",
       "excludeWindows": [],
       "forwardToTelegram": true
     },
     "telegram": {
       "token": "",
       "allowedUserIds": []
     },
     "security": {
       "level": "moderate",
       "allowedTools": [],
       "disallowedTools": []
     }
   }
   

3. Confirm the reset. Note: this does not delete cron jobs — use /claude-hermes:jobs delete for that.

---

Reference: Settings File

Location: .claude/hermes/settings.json

{
  "model": "opus",
  "api": "",
  "fallback": {
    "model": "glm",
    "api": ""
  },
  "timezone": "America/New_York",
  "timezoneOffsetMinutes": -300,
  "heartbeat": {
    "enabled": true,
    "interval": 15,
    "prompt": "Remind me to drink water and stretch.",
    "excludeWindows": [
      { "days": [0, 6], "start": "23:00", "end": "07:00" }
    ],
    "forwardToTelegram": true
  },
  "telegram": {
    "token": "123456:ABC-DEF...",
    "allowedUserIds": [123456789]
  },
  "security": {
    "level": "moderate",
    "allowedTools": [],
    "disallowedTools": []
  }
}

Key	Type	Description
model	string	Claude model (opus, sonnet, haiku, glm, or full ID). Empty = default
api	string	API token used when model is glm (mapped to ANTHROPIC_AUTH_TOKEN)
fallback.model	string	Backup model used automatically if primary run returns rate-limit text (recommend glm for provider diversity)
fallback.api	string	API token used with fallback.model (optional)
timezone	string	IANA timezone name (e.g. America/New_York)
timezoneOffsetMinutes	number	UTC offset in minutes (auto-resolved from timezone)
heartbeat.enabled	boolean	Whether the recurring heartbeat runs
heartbeat.interval	number	Minutes between heartbeat executions
heartbeat.prompt	string	Prompt sent to Claude on each heartbeat
heartbeat.excludeWindows	object[]	Quiet windows where heartbeat is skipped
heartbeat.excludeWindows[].days	number[]	Days of week (0=Sun..6=Sat); omit for all days
heartbeat.excludeWindows[].start	string	Window start time in HH:MM 24h format
heartbeat.excludeWindows[].end	string	Window end time in HH:MM 24h format
heartbeat.forwardToTelegram	boolean	Forward heartbeat output to Telegram (false suppresses HEARTBEAT_OK)
telegram.token	string	Bot token from @BotFather
telegram.allowedUserIds	number[]	Telegram user IDs allowed to interact
security.level	string	locked | strict | moderate | unrestricted
security.allowedTools	string[]	Extra tools to allow
security.disallowedTools	string[]	Tools to block

The daemon hot-reloads this file every 30 seconds. No restart needed after changes.