Add noodle to the tool registry - #495
Merged
Merged
Conversation
Noodle is a terminal REST client: every request is a readable YAML file that lives beside the code it exercises, driven from the TUI, the CLI or a script. It sits next to mcpjam in the registry for the obvious reason — mcpjam tells you whether an MCP server answers, noodle is how you ask an HTTP one anything at all. It ships a per-platform static binary on its own GitHub releases rather than npm, so the install is the vendor script. Through `bash`, not `sh`: the script declares a bash shebang and uses `local`, unlike the c0upons installer beside it, which avoids bashisms on purpose. No `upgrade` key. Noodle ships no updater of its own, and the installer always fetches the latest release, checks it against the published SHA256SUMS and renames it over the existing binary atomically, so re-running the install IS the upgrade and toolUpgradeSpec falls back to it. The binary lands in ~/.local/bin and nothing appends to PATH, hence binDirs — the same gap turso, gradient, kimi and yt-dlp have. Verified against the live installer rather than the spec alone: install, `moshcode tools` status, top-level passthrough and the upgrade re-run all exercised end to end on noodle 0.8.5. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PqnstZRhi764pihZounU3n
ThreatCrush Security Scan0 finding(s) in the 4 file(s) this pull request changes. Nothing in the files this pull request changes. 92 pre-existing finding(s) elsewhere in the repository — **HIGH/CRITICAL**: 8 | **MEDIUM**: 74 | **LOW**: 10Not introduced by this pull request. The full set is in the Security tab.
…and 72 more. Full results in the Security tab. Snippets are redacted; ThreatCrush never prints matched credential material. |
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.
Adds Noodle — a terminal REST client — to
moshcode install/moshcode tools/ top-level passthrough.curl -LsSf https://noodlerest.dev/install.sh | shWhy it sits where it does
Next to
mcpjamin the registry: mcpjam tells you whether an MCP server answers, noodle is how you ask an HTTP one anything at all. Every request is a readable YAML file kept beside the code it exercises, so a collection is reviewed in a diff and runnable from a pipeline.The three judgement calls
bash, notsh. The installer declares a bash shebang and useslocal— the opposite of the c0upons entry beside it, which avoids bashisms on purpose.upgradekey. Noodle ships no updater. The installer always fetches the latest release, checks it against the publishedSHA256SUMS, and renames it over the existing binary atomically, so re-running the install is the upgrade andtoolUpgradeSpecfalls back to it.binDirs. It lands in~/.local/binand appends nothing to PATH — the same gap turso, gradient, kimi and yt-dlp have.Verified live, not just specified
Per the house rule that an install exiting 0 is not an install, this was exercised end to end against the real installer on noodle 0.8.5:
moshcode install noodle→ downloaded, checksum-verified,~/.local/bin/noodlemoshcode tools→● noodlemoshcode noodle --version→0.8.5through passthroughmoshcode upgrade noodle→ re-ran the installer,✓ noodle up to date, exit 0Full suite green: 2896 tests, 0 fail (2563 pass, 333 pre-existing skips), including two new tests — the install-delegation table row and a dedicated entry test covering bin, install spec, upgrade fallback, no-escalation and binDirs.
🤖 Generated with Claude Code
https://claude.ai/code/session_01PqnstZRhi764pihZounU3n