Chukke documentation

Assist and Providers

Configure optional model providers and review document content before each Assist request.

Assist is an optional workflow for running predefined recipes with a model you configure. It is separate from Model-ready, which runs locally.

Enable Assist

Assist is off by default. Enable it in Settings, then configure the models and recipes you want to use. Supported provider types include:

  • local Ollama
  • OpenAI-compatible services
  • Anthropic Claude
  • Google Gemini

Provider availability, privacy, and retention are governed by the service you select.

Review every request

Before an Assist action sends document content, Chukke shows:

  • the selected provider
  • the endpoint
  • the model
  • the source scope
  • the exact Markdown payload

Chukke sends that content only after you confirm the preview. You can cancel a pending request before it completes. Test Connection in Settings is separate: it sends a short provider-specific check, and the configured API key when needed, without document content or a payload preview.

For a file opened outside the active workspace, the local interface may show its path so you can recognize it. Provider request labels use the filename, and the canonical external path is not added to the provider payload. The document content and any explicitly selected workspace context remain visible in the exact payload preview.

API keys

Keys for non-local providers are retained in memory only for the current Chukke session. They are not written to Chukke settings and must be entered again in a later session.

Provider requests carrying an API key require an HTTPS endpoint. Credential-free Ollama can use HTTP on your own machine or local network.

Rewrite and review results

Rewrite responses open a color-coded diff so you can accept or reject the replacement. Review recipes return feedback without replacing the source document.

Local and remote providers

A local Ollama service can process requests on your own configured machine or local network. A third-party provider receives the exact content you approve and handles it under its own privacy and retention terms. Chukke does not control a third party’s retention.

Before using a remote provider, review its current privacy policy and do not share content you are not authorized to send.