Merge branch 'main' into bb/gui
This commit is contained in:
@@ -125,6 +125,10 @@ Jobs with a `workdir` run sequentially on the scheduler tick, not in the paralle
|
||||
|
||||
You do not need to delete and recreate jobs just to change them.
|
||||
|
||||
:::tip Job reference
|
||||
The `<job_id>` placeholder below (and in [Lifecycle actions](#lifecycle-actions)) also accepts the job's name (case-insensitive) — handy when you remember `morning-digest` but not the hex ID. An exact job ID takes precedence over name matches; if the reference is not an ID and a name matches more than one job, the command refuses and prints the candidate IDs so you can disambiguate.
|
||||
:::
|
||||
|
||||
### Chat
|
||||
|
||||
```bash
|
||||
|
||||
@@ -274,6 +274,7 @@ delegation:
|
||||
model: "qwen2.5-coder"
|
||||
base_url: "http://localhost:1234/v1"
|
||||
api_key: "local-key"
|
||||
# api_mode: "anthropic_messages" # Optional. Wire protocol override for base_url ("chat_completions", "codex_responses", or "anthropic_messages"). Empty = auto-detect from URL (e.g. /anthropic suffix). Set explicitly for endpoints the heuristic can't classify (Azure AI Foundry, MiniMax, Zhipu GLM, LiteLLM proxies, …).
|
||||
```
|
||||
|
||||
:::tip
|
||||
|
||||
@@ -12,7 +12,7 @@ Unlike Hermes' built-in OAuth integrations (Google, GitHub Copilot, Codex), Spot
|
||||
|
||||
## Setup
|
||||
|
||||
### One-shot: `hermes tools`
|
||||
### One-shot: `hermes tools` or first-run setup
|
||||
|
||||
The fastest path. Run:
|
||||
|
||||
@@ -20,7 +20,9 @@ The fastest path. Run:
|
||||
hermes tools
|
||||
```
|
||||
|
||||
Scroll to `🎵 Spotify`, press space to toggle it on, then `s` to save. Hermes drops you straight into the OAuth flow — if you don't have a Spotify app yet, it walks you through creating one inline. Once you finish, the toolset is enabled AND authenticated in one pass.
|
||||
Scroll to `🎵 Spotify`, press space to toggle it on, then `s` to save. The same toggle is also available during the first-run `hermes setup` / `hermes setup tools` flow. Spotify stays opt-in, so enabling it there runs the same provider-aware configuration as `hermes tools`.
|
||||
|
||||
Hermes drops you straight into the OAuth flow — if you don't have a Spotify app yet, it walks you through creating one inline. Once you finish, the toolset is enabled AND authenticated in one pass.
|
||||
|
||||
If you prefer to do the steps separately (or you're re-authing later), use the two-step flow below.
|
||||
|
||||
@@ -125,6 +127,12 @@ Control and inspect playback, plus fetch recently played history.
|
||||
| `list` | Every Spotify Connect device visible to your account |
|
||||
| `transfer` | Move playback to `device_id`. Optional `play: true` starts playback on transfer |
|
||||
|
||||
### Home Assistant-managed speakers
|
||||
|
||||
If Home Assistant manages speakers that already support Spotify Connect (for example Sonos, Echo, Nest, or other Connect-capable speakers), they appear in `spotify_devices list` automatically whenever Spotify can see them. Hermes does not need a Home Assistant ↔ Spotify bridge for this path — Spotify handles the device routing natively.
|
||||
|
||||
Ask Hermes to transfer playback by the speaker's display name (for example, “transfer Spotify to the kitchen speaker”), or call `spotify_devices list` and pass the exact `device_id` to `spotify_devices transfer` when scripting. If the speaker is missing, open the Spotify app or the speaker's Spotify integration once so Spotify registers it as an active Connect target.
|
||||
|
||||
#### `spotify_queue`
|
||||
| Action | Purpose | Premium? |
|
||||
|--------|---------|----------|
|
||||
|
||||
@@ -35,6 +35,9 @@ hermes dashboard --host 0.0.0.0
|
||||
|
||||
# Start without opening browser
|
||||
hermes dashboard --no-open
|
||||
|
||||
# Enable the in-browser Chat tab
|
||||
hermes dashboard --tui
|
||||
```
|
||||
|
||||
## Prerequisites
|
||||
@@ -49,6 +52,8 @@ The `web` extra pulls in FastAPI/Uvicorn; `pty` pulls in `ptyprocess` (POSIX) or
|
||||
|
||||
When you run `hermes dashboard` without the dependencies, it will tell you what to install. If the frontend hasn't been built yet and `npm` is available, it builds automatically on first launch.
|
||||
|
||||
The Chat tab is intentionally off for a plain `hermes dashboard` launch. Start the dashboard with `hermes dashboard --tui` or set `HERMES_DASHBOARD_TUI=1` when you want the embedded browser chat pane.
|
||||
|
||||
## Pages
|
||||
|
||||
### Status
|
||||
|
||||
Reference in New Issue
Block a user