Skip to content

[FEATURE] Clarify what fully local and air-gapped mean #1268

Description

@Neonsy

Summary

Some Strix documentation calls the self-hosted CLI fully local and air-gap capable while the accompanying example uses a remote LLM provider

A remote model receives model requests and the context Strix sends with them

Default telemetry and a missing sandbox image can also require outbound network access

The current wording can make users think no scan data leaves their machine even though that depends on configuration

Where the claims diverge from behavior

AGENTS.md and the coding-agent guide use the broad claims

The local-model guide already explains the model-data distinction more clearly

Three configurations worth distinguishing

  • Local runtime: The CLI, Docker sandbox, and run artifacts stay on the user's machine
  • Fully local scan: The model is local and remote integrations and telemetry are disabled
  • Air-gapped scan: The fully local setup also has the sandbox image and every dependency available offline

Model data follows the configured model provider, so a remote-provider example should not be described as fully local

Places to align

Use the same definitions in the README, AGENTS.md, integration guides, and provider guides

An offline checklist should cover the model, sandbox image, telemetry, web search, update checks, and remote MCP servers

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions