Unverified50% confidenceCautionExact time
Before returning the agent session, run extension must be manually called to forcibly trigger the session start event; otherwise, pi-mcp-adapter will not initialize the MCP server and will report an 'MCP server not initialized' error.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
9/13/2026
First Seen
Valid until: 12/12/2026
Sources
Related Entities
Related Claims
UnverifiedAfter mcp.run() is called, the server begins listening on standard input, waiting for a model to connect and make calls.76% similarUnverifiedEnvironment variables for client-side timeouts, MCP startup modes, and stream-monitoring daemons no longer trigger managed settings approval prompts.74% similarUnverifiedA dedicated MCP server can be declared in an Agent's YML header; that MCP is only loaded when the corresponding Agent starts and is not visible to the main conversation or other Agents.72% similarUnverifiedAfter the MCP server installation is complete, a system restart is usually required, along with re-logging into Windows and restarting OpenCode, before the changes take effect.72% similarUnverifiedMCP prompt template modifications can take effect in real time without restarting the server.70% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/919377API
curl https://kongchang.com/api/v1/knowledge/claims/919377MCP
get_claim(id=919377)