Skip to content

Fix MCP disconnect handling and eager note tab swaps#19

Merged
cwilson613 merged 1 commit into
mainfrom
hotfix/mcp-disconnect-tab-latency
May 18, 2026
Merged

Fix MCP disconnect handling and eager note tab swaps#19
cwilson613 merged 1 commit into
mainfrom
hotfix/mcp-disconnect-tab-latency

Conversation

@cwilson613
Copy link
Copy Markdown
Contributor

Summary

  • Treat MCP transport disconnects such as broken pipe / connection closed as a normal client disconnect in flynt-agent --mcp instead of panicking the server path.
  • Add an eager CodeMirror document swap helper and call it from sidebar and tab-bar note switches so the visible editor updates immediately while Dioxus catches up.
  • Add transport-disconnect classifier coverage in the agent binary tests.

Closes #2.
Closes #3.

Validation

  • cargo check -p flynt-agent -p flynt-app
  • cargo test -p flynt-agent -- --nocapture
  • MCP smoke: flynt-agent --mcp initialized and returned tools/list from a temporary project.


#[component]
fn TabItem(index: usize, title: String, doc_id: flynt_core::models::DocumentId, is_active: bool) -> Element {
fn TabItem(
@cwilson613 cwilson613 merged commit 03e96ca into main May 18, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

MCP connection broken pipe — all tool calls fail after extended session perf: 1.4s latency on tab switch — Dioxus scheduler bottleneck

2 participants