deploy

A complete release procedure for ClawBridge, covering checks, version updates, release notes, Git publishing, and continuous-integration monitoring.

In plain words
What is it for?
Use it to run pre-release tests, update the version in six listed files, update the changelog, commit and tag the release, push it, and check the build.
Why use it?
It makes deployment follow one documented sequence and requires tests and security checks before publishing.

Command for Claude Code

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/nickromanek/clawbridge/deploy
Clone the repo
git clone --depth 1 https://github.com/NickRomanek/clawbridge

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 752 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00752
Opus 5 $0.00000 $0.00376
Sonnet 5 $0.00000 $0.00150
Haiku 4.5 $0.00000 $0.00075

Measured 2d ago against content hash 000b288c8362, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

deploy scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

3. Verify `curl -s http://127.0.0.1:8765/health` returns the new version
.claude/commands/deploy.md · 67 lines

How it starts

The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Full Release Deployment

Run the complete ClawBridge release process. This is the ONLY way to deploy — follow every step.

Pre-flight checks

  1. Confirm /e2e and /security have been run this session (or run them now).
  2. Run smoke tests against the running server: python tests/smoke_test.py
  3. If any tests or security checks fail, STOP and fix before deploying.

Version bump

Bump version in ALL 6 locations (skip if already bumped):

  • clawbridge.py line ~14 (__version__)
  • build.py line ~32 (VERSION)
  • build_macos.py line ~36 (VERSION)
  • installer.iss line ~10 (#define MyAppVersion)
  • website/frontend/src/pages/download.astro (version string)
  • website/frontend/src/pages/index.astro (softwareVersion in JSON-LD)

Verify all 6 match by grepping for the version string across all files.

CHANGELOG

Update CHANGELOG.md with a new section for the version. Categorize changes as Added/Changed/Fixed.

Commit, tag, push

git add <changed files>
# Use -f for website/ files (gitignored)
git commit -m "vX.Y.Z: description"
git tag vX.Y.Z
git push && git push --tags

Wait for CI

Check build status: gh run list --limit 3 Wait for the Build & Release workflow to complete: gh run watch <run_id> If build fails, check logs: gh run view <run_id> --log-failed

Deploy website (MANDATORY if download.astro or index.astro changed)

cd website/frontend && npx astro build && npx wrangler pages deploy dist --project-name clawbridge-site

If backend changed: cd website/backend && npx wrangler deploy

NOTE: npm run build runs astro check && astro build — the type checker has pre-existing errors in download.astro. Use npx astro build directly to skip type checking.

Post-deploy verification

  1. Check GitHub releases page has all artifacts
  2. Verify clawbridge.ai/download shows correct version
  3. Verify curl -s http://127.0.0.1:8765/health returns the new version

Past failures to watch for

  • v0.5.4: Website deploy was SKIPPED even though download.astro changed. Always deploy website when version files change.
  • v0.5.5: npm run build fails due to pre-existing TS errors in download.astro. Use npx astro build directly.
  • Python \n in JS: When adding JS regexes in Python strings, use \\n not \n. The \n becomes a literal newline that breaks the <script> block.
  • Installer filename: Must always be ClawBridge-Setup.exe — no version suffix.
  • v0.5.5: --host 127.0.0.1 is NOT a valid OpenClaw flag. Use --bind loopback instead. The wrong flag silently kills the gateway, causing 30s timeouts on every chat task.
  • OpenClaw gateway flags: Full command is openclaw gateway --port 18789 --bind loopback --allow-unconfigured --auth none --dev. Always test gateway startup after changes.

Read the full file on GitHub · 67 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 67 lines · 0 tokens per session scan A 000b288c8362

Subscribe to this mod's changes

deploy is a command published in the GitHub repository NickRomanek/clawbridge (23 stars, last pushed 5mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 752 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.