# exo-explore/exo · RepoSense Release & Migration Intelligence

> Add Kimi K2.6, including support for multimodality (#1952). Drop-in upgrade. Migration: None.

## Metadata
- **Repository URL**: https://github.com/exo-explore/exo
- **Primary Package**: `@exo-explore/exo` (NPM)
- **Categories**: `LOCAL-AI`, `RUNTIME`
- **Latest Version**: `v1.0.71`
- **Semantic Status**: `COMPATIBLE`
- **Bundle Size Impact (unavailable)**: `Size Unavailable`
- **Atom Ingestion Feed**: https://github.com/exo-explore/exo/releases.atom

## The Human Context (Plain-English Pitch)
@exo-explore/exo is an open-source library and developer tool in the exo-explore/exo ecosystem. It saves developers from writing repetitive low-level boilerplate from scratch by providing a battle-tested, open-source implementation ready for production.

## Stage 1 Executive Summary ([Core Change] + [Required Action] + [Migration Effort])
Add Kimi K2.6, including support for multimodality (#1952). Drop-in upgrade. Migration: None.

## Breaking Changes & Required Actions
- Add Kimi K2.6, including support for multimodality (#1952)
- Add model cards for Qwen3.6 27B, GLM 5.1 and Kimi K2.6 quantisations (#1970)
- Add recommended sampling defaults (from model providers) to improve model output quality, including min_p and top_k (#1947)
- Prevent JACCL all_sum from corrupting output (#1952)

## Migration Snippet
```ts
npm install @exo-explore/exo@1.0.71
```

## Ecosystem Compatibility Matrix & Graph Warnings
- **TypeScript 5.x** [`COMPATIBLE`]: Ships standard TypeScript declaration files without type regressions.

## Zero-Noise Release Timeline
- **v1.0.71** (2026-04-23) [COMPATIBLE]: Add Kimi K2.6, including support for multimodality (#1952). Drop-in upgrade. Migration: None.

## Upgrade & Migration Q&A (GEO Direct Answers)
### Is exo-explore/exo v1.0.71 safe to upgrade in production?
exo-explore/exo v1.0.71 is classified as COMPATIBLE (PATCH release). Add Kimi K2.6, including support for multimodality (#1952). Drop-in upgrade. Migration: None.

### What breaking changes or compatibility risks exist in exo-explore/exo v1.0.71?
No breaking API changes or peer dependency conflicts are recorded for exo-explore/exo v1.0.71 in the RepoSense compatibility graph.

### What is the bundle size impact of @exo-explore/exo v1.0.71?
Measured bundle size telemetry is currently unavailable for @exo-explore/exo v1.0.71; verify build output locally before deploying.

### How do I upgrade @exo-explore/exo to v1.0.71?
Upgrade @exo-explore/exo to v1.0.71 by running "npm install @exo-explore/exo@1.0.71" and applying the migration steps: npm install @exo-explore/exo@1.0.71