# NousResearch/hermes-agent · Feishu streaming edit extra leading blank lines

## Open now

- Nothing open on GitHub.

These issues and fixes address extra leading blank lines appearing in Feishu streaming message edits. Multiple fix attempts target stripping leading newlines from the edit_message output.

## TL;DR

- 4 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 2 PR(s) closed without merging.
- A fix was merged to main in PR #14503. Verify it addresses your case.
- **Recommended:** read PR #14503 (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.50`: 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

- #8252: \[Bug\]: Feishu streaming messages show extra leading blank lines after edits

## Prior & competing PRs

- **#14503: fix(feishu): format_message on streaming edits to strip leading newlines (salvage #8254)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `gateway/platforms/feishu.py`, `scripts/release.py`
- **#8254: fix(feishu): issue where streaming edits in Feishu show extra leading…**. closed without merge
  - maintainer direction: category `superseded_by_pr`; implication `superseded`; refs `#14503`
- **#8310: fix(feishu): strip leading blank lines from edit_message output**. closed without merge
  - maintainer direction: category `silent_close`; implication `active`

## Fix status

- Merged to main in PR #14503 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-04-23`. This confirmation is old and may be out of date (a revert/reopen would not have invalidated it here); re-verify.