Repository navigation
Carry the MCP connection timeout in the published setup - #5
Merged
Merged
Conversation
A clean OpenClaw host install on 2026-09-25 failed its first MCP probe. The cause was not DreamLayer: `npx -y @dreamlayer/mcp@0.4.0-beta.4` took about 50 seconds on a cold npm cache while OpenClaw waits 5 seconds by default and reports the server as failed. The successful run used connectionTimeoutMs 90000, and the published skill did not show it, so every new user hit the same wall. The ClawHub skill's config now carries connectionTimeoutMs, and the paragraph under it states the measured cold-start time, OpenClaw's default, and the two ways out: raise the host's timeout, or install the package first. docs/hermes-setup.md carries the same config and a host-neutral version of the note, and docs/client-setup.md gains an OpenClaw section with the exact commands. The skill frontmatter said 1.0.0 while ClawHub served 1.0.1, which would mislead anyone reading the repository. This change publishes 1.0.2 deliberately and the frontmatter names it. One stale line in docs/client-setup.md told readers beta.3 was the working version. It now refers to the current beta rather than naming a superseded one. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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
1 participant
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.
What broke
A clean OpenClaw host install on 2026-09-25 failed its first MCP probe with
MCP server "dreamlayer" timed out: did not complete initialize within 5s. The cause is a cold start, not DreamLayer:npx -y @dreamlayer/mcp@0.4.0-beta.4took about 50 seconds on an empty npm cache, and OpenClaw's default MCP connect timeout is 5 seconds. The run that succeeded usedconnectionTimeoutMs: 90000, but the published skill never showed it, so every new user would hit the same wall.Changes
clawhub/dreamlayer-image-workflows/SKILL.md: the MCP config now carries"connectionTimeoutMs": 90000, and the paragraph beneath it states the measured cold-start time, OpenClaw's default, and the two ways out: raise the host's timeout, ornpm i -gthe package first.docs/hermes-setup.md: same config, with a host-neutral version of the note.docs/client-setup.md: a new OpenClaw section with the exact install, key andmcp add --connect-timeout 90commands.1.0.0to1.0.2. ClawHub already served1.0.1, so the repository was misleading anyone who read it; this publishes1.0.2deliberately and names it.docs/client-setup.mdtold readers beta.3 was the working version. It now refers to the current beta instead of a superseded one.Validation
python3 scripts/validate.pypasses.connectionTimeoutMs == 90000with the current pin.research/.No claim about Unity changes here, and no account, credit or purchase is involved.
🤖 Generated with Claude Code