Design Challenges
The meaning of being “online” on a device has multiple layers. Credentials being written to disk does not mean the Hub has accepted the session; a running process does not guarantee that the Invocation channel is available; local registration does not imply that a remote alternative route already exists. If the status is compressed into a boolean, the operator will repeatedly log in or reboot at the wrong moment. The startup process must consider identity, process, and endpoint facts, and when a workflow is joined, it must record the last failed stage.
Dynamic tools will change the directory. The upstream MCP service may delete or add tools while running; it may also start slowly; plugin packages may be corrupted, and the actual host may not be able to load them. If declarations in files are treated as executable capabilities, users will discover the directory promises only when they actually invoke it.
Multistep tasks amplify the uncertainty of results. If the cleaning step hasn’t run, there is no input for the report; if a request times out, the remote side’s side effects may already have occurred. Network retries, deduplication of operations, and task re-execution need to be handled separately, otherwise a “recovery” becomes a duplicate write. The terminal also raises another requirement: when a daemon updates, the currently running interactive program should ideally keep alive, but control of the existing connections must be re-verified.
No comments yet

