# NousResearch/hermes-agent · Branching and tree-structured conversation session features

## Open now

- 3 issues, 0 PRs open on GitHub.
- #22134: Feature Request: "Time-Travel" Branching Thought Trees (MCTS UI)
- #32105: \[Feature\]: Branch/fork a session from a specific message
- #42292: \[Feature\]: Conversation Memory Locations
- _Broad area: open items may be separate problems._

These requests all concern the ability to branch, fork, or navigate conversations as tree structures rather than linear threads. They explore related ideas like branching from specific messages, visualizing thought trees, and managing conversation memory across branches.

## TL;DR

- 4 member(s): 3 open issue(s), 1 closed issue(s), 0 open PR(s), 0 merged PR(s), 0 PR(s) closed without merging.
- No fix found: no merged or attempted fix PR is on record for this cluster.
- **Recommended:** if this matches your symptom, consider adding to the existing issue(s) below rather than opening a new one.

## 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 (`LLM_ONLY`): no structural link between members; the grouping rests entirely on an automated relevance judgement over their text.
- Read the members yourself before treating them as one problem.
- Pairwise link density `0.18`: 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.

## Open related issues

- #22134: Feature Request: "Time-Travel" Branching Thought Trees (MCTS UI)
- #32105: \[Feature\]: Branch/fork a session from a specific message
- #42292: \[Feature\]: Conversation Memory Locations

## Closed / duplicate issues

- #357: Feature: Tree-Structured Sessions with Branching & Navigation (inspired by Pi)

## Fix status

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