# NousResearch/hermes-agent · Vision custom endpoint model name prompt fixes

## Open now

- Nothing open on GitHub.

These issues and pull requests address a bug where the vision setup tool's custom endpoint configuration never prompted users for a model name, and related fixes to allow vision to work with any provider and model rather than being restricted.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 0 merged PR(s), 2 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## 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

- #41441: \[Bug\]: hermes setup tools vision → custom endpoint never prompts for model name

## Prior & competing PRs

- **#41459: fix(cli): prompt for vision model name when configuring custom endpoint**. closed without merge · fix tier `suggested`
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `917f6bdb00b8b4d0f1c678702c639a5bc966a8eb`
  - _suggested-tier fix detail withheld; re-request with `?tier=all` to include it._
- **#41582: fix(cli): prompt for model name in vision custom endpoint setup (#41441)**. closed without merge
  - maintainer direction: category `uncategorized`; implication `needs_llm`

## Fix status

- No merged fix on record.
- Subsystem: `hermes_cli`