fix(hooks): launch bash guards portably on Windows - #140
Open
CodeWithJuber wants to merge 3 commits into
Open
Conversation
OpenClaw becomes the config compiler's tenth tool, wired through the existing compiler/registry patterns rather than a side script. Instructions need no new file. OpenClaw appends the execution folder's AGENTS.md after its configured agent-workspace files as project context, so the canonical source reaches it exactly the way it reaches Codex, Cursor and Copilot. The new src/emit/openclaw.js reports that relationship and nothing more. MCP is registered explicitly, never silently. OpenClaw keeps its server registry in the user's global ~/.openclaw/openclaw.json under mcp.servers, which Forge will not write to. So `forge sync` emits an OpenClaw-shaped fragment to .openclaw/mcp.json and the report row carries the exact enabling command (`openclaw mcp add forge-cortex --command forge --arg cortex-mcp`) plus a "not auto-loaded" note, so nothing reads as live that isn't. .openclaw/mcp.json is an ordinary managed MCP target: idempotent, per-target ownership (a divergent same-name server the user wrote is preserved until --adopt), and reversible through `forge integrations remove`. To reach a nested bucket, JSON targets now address their server map by dotted key path; the resolver creates missing objects only on write and refuses to restructure a document where any step already holds a non-object. `openclaw` is selectable and auto-detected by `forge tools`. Forge installs nothing into OpenClaw's hook system. There are no ambient guards there, only AGENTS.md text and the MCP tools — docs say so rather than implying Claude Code parity. Docs, tool-count claims, and the changelog move in the same pass; `forge docs check` passes. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
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.
Windows portable hooks so ForgeKit bash guards run via Node on Windows without relying on a Unix shebang.
Worked on by
View the OpenClaw team session