Add Coral to the workflow tool registry - #390
Merged
Merged
Conversation
Coral is a read-only SQL layer over APIs, databases, and internal systems, so `moshcode install coral` runs the vendor's official script and `/coral` passes arguments straight through like the other tools. The installer resolves the latest GitHub release, verifies its sha256, and drops the binary in ~/.local/bin — the same dir gh/supabase/doctl land in, so no binDirs entry is needed. Coral ships no self-updater and documents re-running the script as the upgrade path for a direct install, which is what toolUpgradeSpec already falls back to. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
ThreatCrush Security Scan97 finding(s) HIGH/CRITICAL: 5 | MEDIUM: 41 | LOW: 51
…and 47 more. Full results in the Security tab. Snippets are redacted; ThreatCrush never prints matched credential material. |
Merged
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 Coral to the workflow tool registry, so
moshcode install coral(and/install coralin the pit) runs the vendor's official script:curl -fsSL https://withcoral.com/install.sh | bashCoral is a read-only SQL layer over APIs, databases, and internal systems — one connection an agent can query across sources.
What changed
src/tools.mjs—coralentry:bin: "coral", install via the official script throughbash.src/commands.mjs—cliVerb("coral", …), somoshcode coral sql "…"passes straight through like every other tool.README.md— install list + moshscript verb table.test/tools.test.mjs— coral joins the install-script delegation loop, plus a registry test asserting the spec and the upgrade fallback.Notes
binDirs. The installer drops the binary in$HOME/.local/bin(overridable viaCORAL_INSTALL_DIR) — the same dirgh/supabase/doctlland in, which is already assumed on PATH.upgradekey. Coral ships no self-updater and documents re-running the installer as the upgrade path for a direct install, which is exactly whattoolUpgradeSpecfalls back to. The new test assertsupgrade === undefinedso adding one later is a deliberate change.| bash, not| sh. The script is POSIX sh, but withcoral.com documents the bash pipeline, so that is what we run.The pit help roster and
moshcode installusage are derived fromTOOLS, so both picked coral up with no further edits.Verification
moshcode tools→○ coral Coral — read-only SQL across your APIs, databases, and internal systemsmoshcode installusage andmoshcode helpboth list coral.moshcode coral sql "SELECT 1"→coral isn't installed (`coral`). run: moshcode install coral🤖 Generated with Claude Code