How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

upgrade-cairo - Prompt - OpenSmartRoute

Name: upgrade-cairo
Author: keep-starknet-strange

Prompt file imported from keep-starknet-strange/garaga (.claude/commands/upgrade-cairo.md). Copyright stays with the author.

Upgrade Cairo Version

Upgrade the Cairo/Scarb toolchain from its canonical version source, then run the full compatibility checks.

Arguments

NEW_CAIRO_VERSION: The exact target Cairo/Scarb version, in major.minor.patch format.
NEW_FOUNDRY_VERSION: An optional exact Starknet Foundry version. Without this argument, keep the current Foundry version.

Procedure

1. Select the target versions

Read release_info in tools/make/constants.json for the current versions. Use the target versions that the user already selected. If the user has not selected versions, inspect the available releases:

asdf list all scarb
asdf list all starknet-foundry

Present stable target versions and obtain the user's selection before changing them. Record the current and target versions for the upgrade report.

2. Synchronize the toolchain configuration

If venv is absent, run make setup before changing the version source. Update release_info.cairo_version in tools/make/constants.json. If the user selected a Foundry update, also update release_info.starknet_foundry_version. From the repository root, run:

make sync-toolchain
make check-toolchain

The synchronization command updates tracked Scarb manifests, .tool-versions, CI toolchain inputs, and the two Python generator version constants. It includes manual and generated projects. Setup reads its required Scarb version directly from the canonical source. It preserves package versions, unrelated constants, comments, and cryptographic source files. If an unsupported configuration format stops synchronization, resolve that format before continuing. Require the check command to exit successfully.

3. Install the selected toolchain

From the repository root, run:

asdf install
scarb --version
snforge --version

Require the installed versions to match the selected versions. If asdf is unavailable, install those exact releases through the supported Scarb and Foundry installers. Report installation failures before proceeding.

4. Regenerate and format the artifacts

Run the complete regeneration:

make rewrite
make check-toolchain

This step regenerates Cairo circuits, verifier contracts, and application tests. It is separate from configuration synchronization. Review the generated diff and require both commands to succeed. If the compiler requires Cairo or generator logic changes, handle those changes in separate compatibility work. Keep the upgrade incomplete until that work and its checks pass.

5. Recompute compiler-dependent class hashes

Build the universal ECIP contract and compute its class hash:

(cd src/contracts/universal_ecip && scarb build)
(cd src/contracts/universal_ecip && sncast utils class-hash --contract-name UniversalECIP)

Remove leading hexadecimal zeroes after 0x from the reported hash. Update ECIP_OPS_CLASS_HASH in hydra/garaga/starknet/groth16_contract_generator/generator.py with that value. Regenerate the verifier contracts, then update the RISC0 sample application hash:

make rewrite
make update-risc0-class-hash
make check-toolchain

Require the generated ECIP references and the RISC0 sample hash to match the compiled contracts. These deployment references require separate recomputation. The synchronization command does not change them.

6. Update current installation instructions

Review Scarb and Foundry version references in:

README.md
docs/gitbook/installation/developer-setup.md
docs/gitbook/maintained-smart-contracts/risczero.md
docs/CONTRIBUTING.md

Update current installation requirements to the selected versions. Preserve historical version references in changelogs and benchmark reports. Use rg to find remaining references to the previous versions and account for each intentional reference.

7. Run the full compatibility checks

Run the local compilation and formatting checks:

(cd src && scarb build && scarb fmt --check)
source venv/bin/activate
black --check .

Black comes from the locked venv environment. Its version owner is uv.lock, not a separate requirements file. The commit hook uses that same executable and retains the Python 3.11 formatting target.

With act or gh act configured, run the existing workflow runners:

make ci-hydra
make ci-cairo
make ci-e2e
make ci-wasm

Require all hosted Hydra, Cairo, E2E, WASM, Node, and setup checks to pass for the upgrade commit. Include every Python matrix entry, generated-code cleanliness, bytecode size limits, and package integration checks. Configuration consistency alone does not prove compiler or runtime compatibility.

8. Report the result

Report the selected versions, synchronization result, regenerated artifacts, recomputed hashes, and compatibility-check results. Identify any intentional historical references and any incomplete compatibility work. Complete the upgrade only after every required check passes.

Install upgrade-cairo and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

# Upgrade Cairo Version Upgrade the Cairo/Scarb toolchain from its canonical version source, then run the full compatibility checks. ## Arguments - **NEW_CAIRO_VERSION**: The exact target Cairo/Scarb version, in `major.minor.patch` format. - **NEW_FOUNDRY_VERSION**: An optional exact Starknet Foundry version. Without this argument, keep the current Foundry version. ## Procedure ### 1. Select the target versions Read `release_info` in `tools/make/constants.json` for the current versions. Use the target versions that the user already selected. If the user has not selected versions, inspect the available releases: ```sh asdf list all scarb asdf list all starknet-foundry ``` Present stable target versions and obtain the user's selection before changing them. Record the current and target versions for the upgrade report. ### 2. Synchronize the toolchain configuration If `venv` is absent, run `make setup` before changing the version source. Update `release_info.cairo_version` in `tools/make/constants.json`. If the user selected a Foundry update, also update `release_info.starknet_foundry_version`. From the repository root, run: ```sh make sync-toolchain make check-toolchain ``` The synchronization command updates tracked Scarb manifests, `.tool-versions`, CI toolchain inputs, and the two Python generator version constants. It includes manual and generated projects. Setup reads its required Scarb version directly from the canonical source. It preserves package versions, unrelated constants, comments, and cryptographic source files. If an unsupported configuration format stops synchronization, resolve that format before continuing. Require the check command to exit successfully. ### 3. Install the selected toolchain From the repository root, run: ```sh asdf install scarb --version snforge --version ``` Require the installed versions to match the selected versions. If asdf is unavailable, install those exact releases through the supported Scarb and Foundry installers. Report installation failures before proceeding. ### 4. Regenerate and format the artifacts Run the complete regeneration: ```sh make rewrite make check-toolchain ``` This step regenerates Cairo circuits, verifier contracts, and application tests. It is separate from configuration synchronization. Review the generated diff and require both commands to succeed. If the compiler requires Cairo or generator logic changes, handle those changes in separate compatibility work. Keep the upgrade incomplete until that work and its checks pass. ### 5. Recompute compiler-dependent class hashes Build the universal ECIP contract and compute its class hash: ```sh (cd src/contracts/universal_ecip && scarb build) (cd src/contracts/universal_ecip && sncast utils class-hash --contract-name UniversalECIP) ``` Remove leading hexadecimal zeroes after `0x` from the reported hash. Update `ECIP_OPS_CLASS_HASH` in `hydra/garaga/starknet/groth16_contract_generator/generator.py` with that value. Regenerate the verifier contracts, then update the RISC0 sample application hash: ```sh make rewrite make update-risc0-class-hash make check-toolchain ``` Require the generated ECIP references and the RISC0 sample hash to match the compiled contracts. These deployment references require separate recomputation. The synchronization command does not change them. ### 6. Update current installation instructions Review Scarb and Foundry version references in: - `README.md` - `docs/gitbook/installation/developer-setup.md` - `docs/gitbook/maintained-smart-contracts/risczero.md` - `docs/CONTRIBUTING.md` Update current installation requirements to the selected versions. Preserve historical version references in changelogs and benchmark reports. Use `rg` to find remaining references to the previous versions and account for each intentional reference. ### 7. Run the full compatibility checks Run the local compilation and formatting checks: ```sh (cd src && scarb build && scarb fmt --check) source venv/bin/activate black --check . ``` Black comes from the locked `venv` environment. Its version owner is `uv.lock`, not a separate requirements file. The commit hook uses that same executable and retains the Python 3.11 formatting target. With `act` or `gh act` configured, run the existing workflow runners: ```sh make ci-hydra make ci-cairo make ci-e2e make ci-wasm ``` Require all hosted Hydra, Cairo, E2E, WASM, Node, and setup checks to pass for the upgrade commit. Include every Python matrix entry, generated-code cleanliness, bytecode size limits, and package integration checks. Configuration consistency alone does not prove compiler or runtime compatibility. ### 8. Report the result Report the selected versions, synchronization result, regenerated artifacts, recomputed hashes, and compatibility-check results. Identify any intentional historical references and any incomplete compatibility work. Complete the upgrade only after every required check passes.

{ "prompt": "# Upgrade Cairo Version\n\nUpgrade the Cairo/Scarb toolchain from its canonical version source, then run the full compatibility checks.\n\n## Arguments\n\n- **NEW_CAIRO_VERSION**: The exact target Cairo/Scarb version, in `major.minor.patch` format.\n- **NEW_FOUNDRY_VERSION**: An optional exact Starknet Foundry version. Without this argument, keep the current Foundry version.\n\n## Procedure\n\n### 1. Select the target versions\n\nRead `release_info` in `tools/make/constants.json` for the current versions.\nUse the target versions that the user already selected.\nIf the user has not selected versions, inspect the available releases:\n\n```sh\nasdf list all scarb\nasdf list all starknet-foundry\n```\n\nPresent stable target versions and obtain the user's selection before changing them.\nRecord the current and target versions for the upgrade report.\n\n### 2. Synchronize the toolchain configuration\n\nIf `venv` is absent, run `make setup` before changing the version source.\nUpdate `release_info.cairo_version` in `tools/make/constants.json`.\nIf the user selected a Foundry update, also update `release_info.starknet_foundry_version`.\nFrom the repository root, run:\n\n```sh\nmake sync-toolchain\nmake check-toolchain\n```\n\nThe synchronization command updates tracked Scarb manifests, `.tool-versions`, CI toolchain inputs, and the two Python generator version constants.\nIt includes manual and generated projects. Setup reads its required Scarb version directly from the canonical source.\nIt preserves package versions, unrelated constants, comments, and cryptographic source files.\nIf an unsupported configuration format stops synchronization, resolve that format before continuing.\nRequire the check command to exit successfully.\n\n### 3. Install the selected toolchain\n\nFrom the repository root, run:\n\n```sh\nasdf install\nscarb --version\nsnforge --version\n```\n\nRequire the installed versions to match the selected versions.\nIf asdf is unavailable, install those exact releases through the supported Scarb and Foundry installers.\nReport installation failures before proceeding.\n\n### 4. Regenerate and format the artifacts\n\nRun the complete regeneration:\n\n```sh\nmake rewrite\nmake check-toolchain\n```\n\nThis step regenerates Cairo circuits, verifier contracts, and application tests. It is separate from configuration synchronization.\nReview the generated diff and require both commands to succeed.\nIf the compiler requires Cairo or generator logic changes, handle those changes in separate compatibility work.\nKeep the upgrade incomplete until that work and its checks pass.\n\n### 5. Recompute compiler-dependent class hashes\n\nBuild the universal ECIP contract and compute its class hash:\n\n```sh\n(cd src/contracts/universal_ecip && scarb build)\n(cd src/contracts/universal_ecip && sncast utils class-hash --contract-name UniversalECIP)\n```\n\nRemove leading hexadecimal zeroes after `0x` from the reported hash.\nUpdate `ECIP_OPS_CLASS_HASH` in `hydra/garaga/starknet/groth16_contract_generator/generator.py` with that value.\nRegenerate the verifier contracts, then update the RISC0 sample application hash:\n\n```sh\nmake rewrite\nmake update-risc0-class-hash\nmake check-toolchain\n```\n\nRequire the generated ECIP references and the RISC0 sample hash to match the compiled contracts.\nThese deployment references require separate recomputation. The synchronization command does not change them.\n\n### 6. Update current installation instructions\n\nReview Scarb and Foundry version references in:\n\n- `README.md`\n- `docs/gitbook/installation/developer-setup.md`\n- `docs/gitbook/maintained-smart-contracts/risczero.md`\n- `docs/CONTRIBUTING.md`\n\nUpdate current installation requirements to the selected versions.\nPreserve historical version references in changelogs and benchmark reports.\nUse `rg` to find remaining references to the previous versions and account for each intentional reference.\n\n### 7. Run the full compatibility checks\n\nRun the local compilation and formatting checks:\n\n```sh\n(cd src && scarb build && scarb fmt --check)\nsource venv/bin/activate\nblack --check .\n```\n\nBlack comes from the locked `venv` environment. Its version owner is `uv.lock`, not a separate requirements file.\nThe commit hook uses that same executable and retains the Python 3.11 formatting target.\n\nWith `act` or `gh act` configured, run the existing workflow runners:\n\n```sh\nmake ci-hydra\nmake ci-cairo\nmake ci-e2e\nmake ci-wasm\n```\n\nRequire all hosted Hydra, Cairo, E2E, WASM, Node, and setup checks to pass for the upgrade commit.\nInclude every Python matrix entry, generated-code cleanliness, bytecode size limits, and package integration checks.\nConfiguration consistency alone does not prove compiler or runtime compatibility.\n\n### 8. Report the result\n\nReport the selected versions, synchronization result, regenerated artifacts, recomputed hashes, and compatibility-check results.\nIdentify any intentional historical references and any incomplete compatibility work.\nComplete the upgrade only after every required check passes.", "variables": [], "notes": "Upgrade the Cairo/Scarb toolchain from its canonical version source, then run the full compatibility checks.", "metadata": { "source": { "provider": "github-claude-commands", "repository": "https://github.com/keep-starknet-strange/garaga", "path": ".claude/commands/upgrade-cairo.md", "ref": "e5479c40d7e523cc276286489050e25f1fd73d38", "url": "https://github.com/keep-starknet-strange/garaga/blob/e5479c40d7e523cc276286489050e25f1fd73d38/.claude/commands/upgrade-cairo.md", "key": "keep-starknet-strange/garaga/.claude/commands/upgrade-cairo.md" } } }

upgrade-cairo

About

Upgrade Cairo Version

Arguments

Procedure

1. Select the target versions

2. Synchronize the toolchain configuration

3. Install the selected toolchain

4. Regenerate and format the artifacts

5. Recompute compiler-dependent class hashes

6. Update current installation instructions

7. Run the full compatibility checks

8. Report the result

Install upgrade-cairo and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews