Skip to content

v0.0.1-rc17

Pre-release
Pre-release

Choose a tag to compare

View all tags
@guelfoweb guelfoweb released this 08 Jul 12:57
v0.0.1-rc17
358ed99

v0.0.1-rc17

Conversation-reuse guidance and post-RC16 project guidance release.

Summary

  • Add post-RC16 agent guidance for future Orbit work.
  • Clarify optional native MTP support in the README.
  • Improve route guidance for conversation reuse.
  • Record the conversation-reuse merge and smoke results in AGENTS.md.

Main changes since RC16

  • #122 Add post-RC16 agent guidance.
  • #123 Clarify optional native MTP support.
  • #124 Improve route guidance for conversation reuse.
  • #125 Update agent guidance after conversation reuse merge.
  • #126 Record conversation reuse smoke results.

Runtime behavior

The route prompt now includes a general, model-guided rule to prefer CHAT
when the user asks to recap, summarize, repeat, continue, explain, or compare
information that is already present and sufficient in the conversation.

Tool use remains allowed for:

  • fresh or current data
  • verification
  • new information
  • changed file or system state
  • missing, stale, ambiguous, or insufficient prior context

This is not a deterministic fast path. It does not add cache/TTL behavior,
tool-specific logic, runtime changes, tool-loop changes, or single-tool changes.

MTP and documentation

Native MTP remains optional, explicit, and experimental.

It is:

  • not enabled by default
  • not always-on for every internal completion
  • not a guaranteed performance win

Pre-RC17 MTP sanity passed with native MTP enabled, multimodal available, and
n_max=3.

Validation

Pre-RC17 validation covered:

  • targeted gates: PASS
  • full unit gate: PASS, 985 tests
  • compileall: PASS
  • git diff --check: PASS
  • prompt validation: 33 prompts
  • prompt sources: 12 prompts from docs/PROMPTS.md
  • ambiguous prompts: 10
  • full E2E steps: 6
  • MTP sanity: PASS

No BLOCKER issues were found.

Conversation reuse validation:

  • system_info recap prefers CHAT / no tool when context is sufficient
  • read-file recap prefers CHAT / no tool when context is sufficient
  • pwd_followup full E2E confirmed no redundant tool call on the follow-up
  • refresh/current/verify/new-information requests still allow tools

Observed MTP props during sanity:

  • mtp_enabled=true
  • mtp_initialized=true
  • mtp_failure_reason=null
  • in_flight=false
  • multimodal_available=true
  • mtp_last_completion.success=true
  • mtp_config.n_max=3

Warnings / known limitations

  • Some route-only smoke checks can still hit finish_reason=length.
  • The grep recap route-only check avoided a tool call but produced empty output
    with finish_reason=length, so it remains inconclusive rather than a full
    PASS.
  • A list recap prompt was ambiguous and selected file reads; this is not treated
    as a blocker because the wording can reasonably mean summarizing file content.
  • Full E2E checks can be too slow on CPU-only systems and must not be treated as
    performance benchmarks unless run with benchmark metadata.
  • This RC does not include new MTP optimization work.
  • cached=4 on route-to-final remains expected when prompt views diverge.
Assets 2
Loading