fix(mcp): self-exit after idle timeout (prototype for #633)#634
Merged
Conversation
Some MCP clients (e.g. Claude Code) spawn fff-mcp per session but don't close stdin on session end, leaving orphan processes consuming CPU (#633, #497). Add an idle watchdog: each tool call bumps a last-activity timestamp, a background task ticks every 60s and exits(0) after --idle-timeout-secs (default 900) without activity. Set to 0 to disable. Also configurable via FFF_MCP_IDLE_TIMEOUT_SECS. Stopgap before the daemon-based process model. Notifications/pings do not count as activity, so a chatty-but-dead client cannot keep the process alive forever.
ff53acf to
51a8b3c
Compare
51a8b3c to
c46c114
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
closes #633
closes #497