[andreynering]

• Follow-up of feat: add embedded package to allow offline functionality catwalk#48
• Closes Offline Mode #453
• Closes fix: make catwalk service dependency optional #689

Some people reported that they can't access Catwalk due to corporate restrictions on internet access, etc.

This PR adds the ability to disable Catwalk. Once disabled, Crush will use the latest available providers from the library, which might be outdated, but should still work if the Crush version is enough up-to-date.

Disabling providers updates

Disabling via ENV:

env CRUSH_DISABLE_PROVIDER_AUTO_UPDATE=1 crush

Disabling via config:

// ~/.config/crush/crush.json
{
  "options": {
    "disable_provider_auto_update": true
  }
}

Manually updating providers

# Update providers remotely from Catwalk
crush update-providers

# Update providers from a custom URL
crush update-providers https://example.com/

# Update providers from a local file
crush update-providers /path/to/local-providers.json

# Update providers from embedded version
crush update-providers embedded

Screenshots

Success output:

Error output:

[billysan]

hi guys anything shaking with this? 🙏🏻

[meowgorithm]

Thanks for your patience with this one, everyone—we do plan on merging this one soon.

[Copilot]

Pull Request Overview

This PR adds the ability to disable automatic provider updates from the Catwalk service, addressing corporate network restrictions and allowing offline usage. When disabled, Crush uses cached or embedded providers instead of fetching from remote sources.

Key changes:

• Added configuration option to disable provider auto-updates via environment variable or config file
• Implemented update-providers command for manual provider management
• Refactored provider loading logic to respect the disable flag and handle offline scenarios

Reviewed Changes

Copilot reviewed 11 out of 11 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
schema.json	Added disable_providers_auto_update boolean field to configuration schema
internal/config/config.go	Added DisableProvidersAutoUpdate field to Options struct
internal/config/load.go	Added environment variable parsing for the disable flag
internal/config/provider.go	Refactored provider loading with disable logic and added UpdateProviders function
internal/config/provider_test.go	Updated test calls to include new autoUpdateDisabled parameter
internal/config/provider_empty_test.go	Updated test calls to include new autoUpdateDisabled parameter
internal/cmd/update_providers.go	New command implementation for manual provider updates
internal/cmd/root.go	Added update-providers command to CLI
internal/tui/components/dialogs/models/models.go	Updated provider loading call to pass config
internal/tui/components/dialogs/models/list.go	Updated provider loading calls to pass config
internal/tui/components/chat/splash/splash.go	Updated provider loading call to pass config

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[bbrodriges]

It would be really great if this PR could be merged

[andreynering]

This is ready to be reviewed.

I suggest to test locally the different scenarios. (I tested carefully myself and for me it's stable).

Also, review the README content and let me know if it's clear.

[andreynering]

We could have this natively on Fang maybe.

Basically, a function to print success (maybe warning, info, ...) messages in the same style as the error message in case an error is returned.

[meowgorithm]

It would be really great if this PR could be merged

We're very close. We'll most likely merge tomorrow and cut a release same day.

[jamestrew]

I hate to hold this up anymore but testing this, I have a slight concern, particularly for new users. Is that by default, if you can't access the catwalk service, you looks like you still just get hit with an error.

❯ crush

   ERROR

  Failed to load providers: failed to make request: Get "https://catwalk.charm.sh/providers": dial tcp: lookup
  catwalk.charm.sh: no such host.

so one would need to know about setting CRUSH_DISABLE_PROVIDERS_AUTO_UPDATE=1.

I think it would be helpful to either communicate the existence of this option to users in the error message, or fallback to enabling CRUSH_DISABLE_PROVIDERS_AUTO_UPDATE automatically if access to catwalk fails.

[andreynering]

Hey @jamestrew.

That was a great suggestion. What about this?

[jamestrew]

Hey @jamestrew.

That was a great suggestion. What about this?

That looks good to me 👍