octet
← Changelog

octet 0.7.2

GitHub release Source notes

Published with signed Native/Serve assets and independently verified public installation.

A focused hotfix for coherent terminal startup, late terminal replies, composer completion, extension trust defaults, and compact tool presentation.

Included fixes#

  • Startup readiness: the first branded frame waits for resolved model (or model-less setup), workspace, and appearance. Startup animation begins at readiness rather than during asynchronous configuration.
  • Terminal replies: the shared input owner consumes late OSC 11 background replies, including slowly fragmented bodies after header recognition. Explicit appearance overrides skip the query; SSH alone does not imply reduced color support. An opening header fragmented beyond the 250 ms Escape-key ambiguity timeout can still pass through; see terminal reply limits.
  • File completion: Up/Down selects path and @ mention suggestions; Tab inserts the selected result. The popup follows the selection beyond its first visible rows. Directory descent, attachment handling, and normal editor navigation without a visible menu remain intact.
  • Extension trust: installed executable bundles stay disabled by default. Full access implicitly trusts explicitly enabled extensions without persisting a trust grant. Safe mode removes implicit trust and retains its permission and execution boundaries; artifact integrity checks remain mandatory. Policy or process downgrades also retire retained services even when trust remains valid.
  • Subagent events: worker rows sit further beneath the transcript heading and omit per-worker call counts. The complete roster, state, token usage, cost, and retained telemetry remain available.
  • Bash command previews: terse tool events show the first three visual lines of a command and a hidden-line count. Ctrl+O expands the full retained command; command execution and existing output truncation are unchanged.

See terminal behavior, commands and keys, and extension policy.

Compatibility and publication#

Product, SDK, Serve, and first-party executable distribution versions are 0.7.2; matching bundles require exactly octet 0.7.2. Extension API versions and native-host protocol 1 are unchanged. Installing a bundle does not enable it. Safe mode is not an OS sandbox.

The published signed assets cover macOS Apple silicon/Intel and GNU/Linux x86-64, plus Serve and octet-browse, octet-mcp, octet-subagents, and octet-web-search. v0.7.2 is the latest stable release. Published 0.7.0/0.7.1 tags and assets remain unchanged.

npm, Homebrew, crates.io, and SDK registries remain separate and unpublished. The website installer redirect is separate work and is not part of this hotfix.

Verification status#

  • Source PR #373 and policy repair PR #374 passed all 14 checks each; final merge ddc997f9d11bf6d281b8eca09c6271ba2e452f23 exactly matches the validated candidate tree.
  • 36 local gates passed: 1,183 coding-library, 499 agent, 142 TUI, all 9 startup PTY and 6 terminal-reply PTY tests; API conformance, extension suites, Clippy/workspace checks, deterministic packaging and installer/Serve smoke.
  • Exact-main CI and CodeQL passed. Signed Native and Serve publication and their hosted install checks passed.
  • Independently downloaded all 28 public files, verified 14 keyless signatures against exact source/workflow identities and 11 checksums, and regenerated byte-identical signed native metadata.
  • Fresh no-Cargo native install/version/help/host handshake and public Serve/four-bundle install/update/remove checks passed. Existing config, sessions and Serve data were preserved; install did not enable extensions.
  • Five simulated public-binary PTY checks passed for delayed/fragmented replies, genuine typing, and explicit appearance. These are not actual SSH acceptance.
  • The unchanged web timing gate required failed-job-only retries before the final main pass. No web code or performance thresholds were changed.

Manual Ghostty/Ubuntu 26.04 SSH, Apple Terminal, live-provider, and native-audio acceptance are NOT RUN. Deterministic terminal fixtures are not a substitute for those manual checks. No benchmarks or performance comparisons are claimed.

Changelog · Documentation