# NousResearch/hermes-agent · slash command /whoami dispatch fix in CLI

## Open now

- Nothing open on GitHub.

These issues and PRs concern a bug where the /whoami slash command was not properly dispatched in the CLI, instead being reported as an unknown command. The work addresses ensuring registered slash commands have a corresponding CLI dispatch branch.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 1 PR(s) closed without merging.
- A fix was merged to main in PR #90381. Verify it addresses your case.
- **Recommended:** read PR #90381 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. `1.00` means every pair is linked.

## Closed / duplicate issues

- #74594: Registered slash commands can silently have no CLI dispatch branch (/whoami, /indicator)

## Prior & competing PRs

- **#90381: fix(cli): /whoami no longer reports Unknown command in the classic CLI (salvage #26047)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `cli.py`, `tests/cli/test_cli_init.py`
- **#77920: fix(cli): dispatch /whoami instead of reporting it unknown**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `#90381`, `#26047`

## Fix status

- Merged to main in PR #90381 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-08-20`.
- Subsystem: `hermes_cli`