Skip to content

Peritus v0.1.8

Choose a tag to compare

@dollspace-gay dollspace-gay released this 21 Oct 04:00
· 13 commits to main since this release
559dc98

Peritus v0.1.8 repairs host-side causes of repeated reading and lost task progress.

  • Preserve approved external reads, role-owned decisions, next steps, and settled effects through retry, compaction, and restart. Keep reads before later edits/deletions explicitly historical.
  • Retain independent reviewer delivery coverage for immutable source pages across invocation boundaries. Repair rejected final output without ordering another grounding pass.
  • Track rotating inspection cycles and repeated refusals across workspace, context, and skill tools. Compact unchanged evidence already in view; no-op edits and unrelated commands do not reset progress.
  • Keep host feedback separate from user requirements and enforce current permissions/private exclusions through original, wrapped, chained, and derived archive access. Normalize ordinary relative path aliases.
  • Admit local work with Read/Write permission while checking Process permission at command launch. Fit large documents as typed UTF-8 pages with exact ranges and continuations.

Completed real testing: 1,120 actual API actions, including generated ranges, cold recovery, role isolation, permission changes, chained archives, and large documents. A real official-provider conversation → design → edit → independent review run reached Accepted in 14 requests and 13 tool calls with workspace Process and Network disabled. Independent execution of its resulting CLI printed exactly After with empty stderr.

All six native packages include the client, daemon, TUI, and platform sandbox helper, with checksums, inventory, SBOM, provenance, and attestations. The release workflow exercises installation and offline terminal startup on the four Unix hosts. Existing behavioral evidence is reused; no unit, mock, formal-verification, or repository qualification suite was run.

Full release notes · Defects and real-testing evidence

The recorded application campaign is bounded Linux evidence, not a multi-hour autonomous soak or a guarantee of every model's next action. No task/read/token quota was added. Deep Research remains separately distributed with its existing wire contract.