octet 0.7.0

The first octet release brings the renamed native coding agent, provider and media fixes, and bounded Pi compatibility. Live-provider and native-audio checks are optional and NOT RUN for this release. Local tests and the website's illustrative TUI recreation are not live demonstrations.

Use the version-pinned GitHub release for published signed native assets on macOS Apple silicon/Intel and GNU/Linux x86-64. The native installer and source build are both available. The repository has moved to skaft-software/octet, preserving its history and releases. These v0.7.0 assets retain their original skaft-software/ygg signing identity. npm is not published yet; its first-package/trusted-publisher bootstrap and provenance verification remain separate. See distribution channels for native and Git-tag Cargo installation, and the npm/Homebrew/registry boundaries. Bun remains unqualified.

Added#

• Native Google Gemini/Vertex and Amazon Bedrock integrations, Azure OpenAI support, and additional Mistral/Cloudflare provider declarations. Provider routes and supported subsets are explicit; declared routes do not establish live-service or complete Pi-provider acceptance.
• Transactional custom-provider onboarding and opt-in cold-start feedback for endpoints that implement the corresponding readiness contract.
• A reusable terminal text editor and improved ordinary command/picker surfaces. --show-images opts in to bounded tool-result images on compatible interactive terminals; it is off by default and does not grant upload consent.
• Extension API 0.3's schema-generated foundation, trusted manifest CLI flags, declared session hooks and host-owned lifecycle services where offered. The extension guide distinguishes these from legacy methods.
• Selective Pi setup import with preview, private backups and restore, plus pinned local compatibility plans and wrappers. These are bounded capabilities, not whole-setup migration or universal Pi source/UX parity.
• Topic-based repository documentation, usage examples and the Brand Kit. The public website is prepared separately from the product's release and installation channels.

Changed#

• Adopted the lowercase octet name, octet and octet-host binaries, octet-* packages, OCTET_* settings and .octet directories. Packaged documentation uses share/octet.
• Thinking choices now retain endpoint-specific exact values, gaps, defaults, binary controls and always-on behavior. Explicit false and manual metadata remain authoritative; malformed assertions fail closed. Genuine provider model labels are preserved without fabricating overrides from raw IDs.
• Ultra requires explicit provider support and V2 delegation; the coding product additionally requires its trusted, enabled observing subagents extension. Responses encodes supported Ultra as max, not an arbitrary universal effort.

See package identities and provider thinking for the precise source contracts.

Existing Ygg installations#

Install octet afresh. ygg update is not a supported octet upgrade path. Existing Ygg installations and data remain separate and untouched. There are no old command or YGG_* aliases, .ygg fallbacks, automatic folder merges, or Hamr/Ygg credential and package-hotfix imports. Back up existing data before removing an old installation; do not assume a new octet installation discovers old sessions or settings. Scripts and custom extensions using old first-party names need review.

An old Ygg updater may select v0.7.0 as the latest GitHub release, then fail when it requests the retired Ygg installer/package names. This release supplies no transition carrier. Third-party ~/.codex/auth.json interoperability and explicit Pi import/restore remain separate features and do not modify their source stores.

Fixed#

• Provider-start WebSocket fallback distinguishes a safe pre-acceptance failure from an ambiguous request that must not be replayed automatically.
• Google replay repairs missing tool results in the documented lossy conversion.
• Typed-media validation, attachment consent, cancellation and local-compaction replay across persisted-session reopening are hardened.
• Native compact requests reject unsupported reasoning controls before resource reservation; raw compact controls are validated before credential resolution or network access.
• Bedrock signed/redacted reasoning continuation and Cerebras reasoning encoding follow their specific contracts. Opaque retained state is aggregate-bounded, replacement-aware and redacted in Debug output.
• Always-on exact On-only metadata is accepted without enabling Off; malformed nested support assertions cannot silently enable reasoning.
• Narrow terminal layouts, duplicate startup rendering and inherited terminal cursor margins are repaired. Active waits remain interruptible and tool/input visibility is preserved.

Local compaction remains the default. None of these fixes establishes current octet benchmark results or completed live-provider acceptance.

Extension compatibility#

Current authoring documentation targets extension API 0.3. The four bundled executable-extension manifests still declare 0.2, and the Python Extension runtime remains a legacy 0.1/0.2 implementation. Generated 0.3 types and negotiation helpers are not a complete standalone 0.3 authoring runtime or runnable example. Native-host protocol 1 remains independent of extension API versions. See the extension guide and native host reference.

Documentation#

• Basic usage, including media and subagent examples.
• Providers and thinking controls.
• Pi import and restore, with explicit compatibility limits.
• Distribution channels and npm publishing.
• Changelog.

Download benchmark results provides historical Ygg v0.6.2 evidence with its provenance and redistribution limits, not a current octet benchmark or a Claude Code token/RAM comparison.

Release verification#

Version 0.7.0 is published from commit 6dcde0620314c554b11719b0bc97835b104f0e47. Main CI and CodeQL passed. The protected native release verified public installation on all three platforms; the Serve release verified public install/update/remove for Serve and the four executable bundles. All 28 public assets and 14 exact-workflow signatures were independently verified, as were a fresh native/host install and offline Serve bundle smoke on macOS arm64. The genuine pinned Pi loader gate passed all 78 examples on the identical release tree; this is not full Pi behavioral or provider parity. See the Pi compatibility boundary.

Release qualification does not require live-provider credentials or paid API calls. Live provider/native-audio checks are separately opt-in. When not selected, the release records NOT RUN, not a pass or a live-service compatibility claim.

Project#

View the project on GitHub.