Skip to content

v0.0.1-rc8

Pre-release
Pre-release

Choose a tag to compare

View all tags
@guelfoweb guelfoweb released this 30 Jun 22:09
v0.0.1-rc8
2774f58

Orbit v0.0.1-rc8 Release Notes

Orbit v0.0.1-rc8 closes the current native MTP stabilization phase after
v0.0.1-rc7.

RC8 documents MTP as supported and stabilized in the native server path with
runtime guardrails. It does not make MTP an always-on path for every completion,
and it is not a final performance release.

Highlights

Native MTP stable with runtime guardrails

Native MTP is supported in the orbit server --mtp path and has been validated
with the current native server workflow.

The runtime can now control MTP per completion with the explicit
allow_mtp_experimental payload flag:

  • missing flag: preserves existing behavior
  • false: vetoes MTP for that completion
  • true: permits MTP only if the existing runtime/backend guardrails also allow it

This is a control-plane guardrail. It does not change prompts, routing policy,
tool policy, final-answer policy, evidence policy, or ROUTE_MAX_TOKENS.

MTP is not always-on everywhere

MTP remains available in the native server path, but Orbit can disable it for
specific internal completions where local measurements showed worse stability or
latency.

In particular, tools-on internal finalization paths such as chat_final_retry
and final_from_tool can send allow_mtp_experimental=false.

Route-prefix anchor, KV prewarm, and restore behavior remain compatible with
this guardrail.

Native server, KV, and multimodal smoke

The RC8 validation path uses:

  • orbit server --mtp
  • MTP initialized in the native server
  • mmproj/multimodal capability loaded or detected
  • KV route-prefix prewarm enabled
  • route-prefix anchor restore for tools-on route calls
  • unified vendored llama.cpp runtime

Orbit continues to use vendored llama.cpp libraries directly. RC8 does not add a
dependency on llama-server and does not update the vendored llama.cpp copy.

UX stabilization carried forward

RC8 includes the RC7 UX/correctness work:

  • web-search finalization no longer gets stuck after max-token finalization
  • streaming/progress labels distinguish tool decision, final answer, and retry
  • route retry UX is clearer
  • internal route prose is not accepted as final output
  • README quickstart is aligned with orbit server --mtp

Validation

Local validation on main after PR #80:

  • full unittest suite: PASS
  • python3 -m compileall -q src tests scripts: PASS
  • git diff --check: PASS
  • orbit server --mtp: PASS
  • MTP initialized: yes
  • mmproj/multimodal detected: yes
  • route-prefix prewarm succeeded: yes
  • route prefix token count: 694
  • route_anchor_hit=true: yes
  • restore_used=true: yes
  • duplicate llama runtime observed: no
  • double-free/SIGABRT/segfault observed: no
  • server shutdown: clean

CLI smoke covered:

  • tools-on, think-off: hi, how are you?
  • tools-on, think-off multi-turn: who designed you?
  • tools-on: run pwd
  • tools-on: search online for OpenAI

Known limitations

  • MTP is guarded, not always-on everywhere.
  • MTP is not a performance guarantee for every completion.
  • Web, read, and think on paths can still be slow on CPU.
  • Post-tool evidence bloat remains an open UX/performance issue.
  • Route-contract drift is mitigated by retry/UX guardrails but not eliminated.
  • Real multimodal input tasks still need separate end-to-end validation.
  • The vendored llama.cpp copy is not updated in RC8.

Upgrade notes

For the current native workflow:

orbit server --mtp

Useful controls remain:

ORBIT_TOOLS=off
ORBIT_KV_PREFIX_PREWARM=off
ORBIT_KV_PREFIX_ANCHOR=off
ORBIT_KV_DIAG=1

ORBIT_KV_DIAG=1 is diagnostic only. It is not required to enable KV behavior.

RC8 is a new prerelease candidate. Previous RC tags and releases remain
unchanged.

Assets 2
Loading