PR #19020: fix(kanban): profile discovery ignores HERMES_HOME in custom-root deployments

• Repository: NousResearch/hermes-agent
• Author: jackey8616
• State: open | merged: False
• Link: https://github.com/NousResearch/hermes-agent/pull/19020

Description (problem / solution / changelog)

What does this PR do?

list_profiles_on_disk() in kanban_db.py hardcodes Path.home() / ".hermes" / "profiles", so hermes kanban init always reports "No profiles found" on custom-root deployments (e.g. Docker with HERMES_HOME=/opt/data), even when valid profiles exist under $HERMES_HOME/profiles/.

This PR switches list_profiles_on_disk() to use get_default_hermes_root(), making profile discovery consistent with how kanban_db_path() and workspaces_root() were fixed in #18985.

Related Issue

Fixes #19017 Related to #18442, #18985

Type of Change

• 🐛 Bug fix (non-breaking change that fixes an issue)

Changes Made

• hermes_cli/kanban_db.py: replace Path.home() / ".hermes" / "profiles" with get_default_hermes_root() / "profiles" in list_profiles_on_disk()
• tests/hermes_cli/test_kanban_core_functionality.py: add monkeypatch.delenv("HERMES_HOME", raising=False) to existing test, and add new test_list_profiles_on_disk_custom_root to cover custom HERMES_HOME case

How to Test

1. Create a fresh directory with a profile under a custom root:

   mkdir hermes-test && cd hermes-test mkdir -p data/profiles/my-agent echo "model: {}" > data/profiles/my-agent/config.yaml

2. Run kanban init with Docker:

   docker run --rm
   -e HERMES_HOME=/data
   -v $(pwd)/data:/data
   nousresearch/hermes-agent
   hermes kanban init

3. Expected output includes:

   Discovered 1 profile(s) on disk; any of these can be an --assignee: my-agent

   Before this fix, the output was: "No profiles found under ~/.hermes/profiles."

Checklist

<!-- Complete these before requesting review. -->

Code

• I've read the Contributing Guide
• My commit messages follow Conventional Commits (fix(scope):, feat(scope):, etc.)
• I searched for existing PRs to make sure this isn't a duplicate
• My PR contains only changes related to this fix/feature (no unrelated commits)
• I've run pytest tests/ -q and all tests pass
• I've added tests for my changes (required for bug fixes, strongly encouraged for features)
• I've tested on my platform: macOS 15.6.1<!-- e.g. Ubuntu 24.04, macOS 15.2, Windows 11 -->

Documentation & Housekeeping

All N/A

Changed files

• hermes_cli/kanban_db.py (modified, +2/-1)
• tests/hermes_cli/test_kanban_core_functionality.py (modified, +19/-4)

---

PR #19030: fix(kanban): use get_default_hermes_root() for profile discovery

• Repository: NousResearch/hermes-agent
• Author: shellybotmoyer
• State: open | merged: False
• Link: https://github.com/NousResearch/hermes-agent/pull/19030

Description (problem / solution / changelog)

Fix: kanban init profile discovery hardcodes ~/.hermes/profiles

Problem

list_profiles_on_disk() in kanban_db.py hardcoded Path.home() / ".hermes" / "profiles", so hermes kanban init always reported "No profiles found" on custom-root deployments (e.g., HERMES_HOME=/data in Docker).

This is inconsistent with kanban_db_path() and workspaces_root(), which were already fixed to use get_hermes_home() in #18985.

Solution

Replace the hardcoded path with get_default_hermes_root() / "profiles", consistent with how kanban_db_path() and workspaces_root() already resolve paths. Falls back to Path.home() / ".hermes" / "profiles" if hermes_constants is unavailable.

Testing

• Custom-root deployments (HERMES_HOME override) will now correctly discover profiles under the custom root
• Default deployments (no HERMES_HOME override) behave identically since get_default_hermes_root() returns Path.home() / ".hermes" in that case
• The fallback path matches the old behavior exactly

Fixes #19017

Changed files

• hermes_cli/kanban_db.py (modified, +10/-7)