Kilo Code

Kilo supports local Ollama and hosted providers; its guide notes that larger contexts use more memory and can affect performance. The product publishes no emissions comparison, and local routing alone says nothing about the electricity source or workload footprint. Measure the local device use against a named hosted alternative.

No per-task electricity, water, or emissions data, serving-region breakdown, or lifecycle assessment was found for the harness.

• Kilo Code local Ollama setup ↗

Kilo supports local models and hosted gateways, but these routes answer different questions: where prompts go and whether the model’s training inputs were permitted. Local inference may improve control over prompts without resolving corpus rights. For rights-sensitive projects, use a model with documented training sources or get the provider’s terms in writing.

The provider and exact model vary by configuration; no complete rights ledger can be inferred from the harness license or provider list.

• Kilo privacy policy and provider routing ↗
• Kilo Code local Ollama setup ↗

Deleting Kilo-side history does not force the model provider to delete its copy, so hosted routing remains a meaningful exception. For private work, configure a local provider and disable any unrelated cloud or gateway features you do not need.

Plan, selected model/provider, enabled features, and deployment mode can change this assessment.

• Kilo privacy policy and provider routing ↗
• Official privacy or data-processing disclosure ↗

Kilo Code’s current repository is MIT-licensed and can be inspected or modified. Its hosted services and connected models remain separate from that codebase. The legacy IDE extension has a distinct repository and lifecycle.

This score covers the harness/editor source only; hosted services, models, data, or enterprise features may remain proprietary.

• Official source repository or product page ↗
• Official license or documentation ↗

Kilo’s public code and privacy documentation explain product and provider paths, but not the pay or conditions of maintainers, vendors, or data workers. The product spans local clients and hosted services, so a single source would not cover the whole labor chain. Ask Kilo and the selected model provider for current worker and vendor disclosures.

Current worker pay, working conditions, subcontracting, safety provisions, and grievance outcomes are not established for this product’s full service chain.

• Official source repository or product page ↗
• Kilo privacy policy and provider routing ↗

Kilo supports both local inference and hosted model gateways; the sources reviewed do not identify Kilo Code in a defense deployment. Gateway or model-provider government work is a separate relationship unless the specific Kilo service is named. Choose a local route or ask Kilo which providers serve the selected model.

No public evidence in the reviewed material names this harness in a defense workload; absence in this review does not establish absence of indirect use.

• Kilo Code local Ollama setup ↗

Kilo is not a named target in the checked lists, but BDS uses selective campaigns, so absence cannot establish a clean record. Check the model and host this tool connects to as well as the company providing the tool.

This review covers the named targets in the BNC consumer/pressure guide and No Tech campaign, not every BDS campaign, local group, investment or supplier. Lists and ownership can change. A company’s absence from these lists is not an endorsement or proof that it has no relevant relationships.

• BNC: live guide to consumer boycott and pressure targets ↗
• BNC: No Tech for Oppression, Apartheid or Genocide campaign ↗