# NousResearch/hermes-agent · Bedrock boto3 lazy dependency initialization bug fix

## Open now

- Nothing open on GitHub.

A bug where the first Bedrock call fails due to _require_boto3 not invoking lazy_deps.ensure, along with two proposed fixes routing the call through that mechanism.

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

- #24967: \[Bug\]: Bedrock first-call fails with manual-install message — _require_boto3 never calls lazy_deps.ensure

## Prior & competing PRs

- **#24972: fix(bedrock): route _require_boto3 through lazy_deps.ensure**. closed without merge · fix tier `suggested`
  - maintainer direction: category `uncategorized`; implication `needs_llm`
  - _suggested-tier fix detail withheld; re-request with `?tier=all` to include it._
- **#25088: fix(bedrock): call lazy_deps.ensure before importing boto3**. closed without merge · fix tier `suggested`
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `c02606a385bd03630b7c76b72bf82f686a51f907`, `#24967`
  - _suggested-tier fix detail withheld; re-request with `?tier=all` to include it._

## Fix status

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