v0.3.6

Wombat v0.3.6

This release keeps local indexing ready in the background and makes focused usage reviews and original-evidence reads faster.

Highlights

• Managed installation starts a resident local indexer. Recent activity is prepared in the background, then file notifications and periodic discovery keep committed views current. Pause, resume and inspect the service through the CLI or Web.
• Prepare the recent 30 days by default and load older history when requested. Persist parser recovery state and bound reusable caches to reduce repeated work after restart.
• Reuse committed usage views for compact daily, model, project and task summaries. Combine related queries against one fixed view, then inspect only the selected tasks or turns.
• Locate or search conversation evidence, then read selected text in bounded batches. The Codex Skill now carries filters and continuation details through the workflow and bases improvement suggestions on specific recorded evidence.

Install or update

macOS and Linux:

curl -fsSL https://raw.githubusercontent.com/YannByte/wombat/main/scripts/install/install.sh | sh

Windows PowerShell:

& ([scriptblock]::Create((irm https://raw.githubusercontent.com/YannByte/wombat/main/scripts/install/install.ps1)))

Update an installer-managed copy:

wombat update --check
wombat update

Supported archives: darwin-arm64, darwin-x64, linux-x64, linux-arm64, win32-x64.

Known limitations

• Codex is the only production data source in this release; support for other agents is planned.
• Recent preparation covers the default 30-day window. Historical requests can require additional preparation. Missing, deferred, partial and unpriced results remain explicit.
• Background indexing and cache limits do not impose a hard process-memory ceiling. Initial preparation, large source catch-up and detail requests can still use substantial memory and temporary disk space.
• Measured warm complete CLI requests met a 100 ms P95 target on the local acceptance corpus. Cold requests and individual outliers can exceed 100 ms; this is not a per-request latency guarantee.
• The 24-hour resident workload qualification and native user-session manager acceptance on Linux and Windows remain separate acceptance work. macOS crash recovery and pause/resume were tested locally; generated service definitions alone do not prove login-startup behavior.
• Original-text access supports selected message mappings and text parts. Unknown mappings, non-text content and delta-stream assembly remain explicit gaps; there is no transcript panel in the Web dashboard.
• Conversation reads verify selected source text blocks and reject changed, replaced, missing or unavailable sources. A successful snippet does not prove that the complete source file is unchanged. Changes require a valid fixed baseline and do not establish additional work or savings.
• API costs are estimates. Unpriced or partial data stays explicit and is separate from subscription allowance.
• Unsupported derived index and parser-cache formats require a rebuild. Existing data is not migrated or automatically deleted. Follow the documented format recovery and preserve user decisions; a different WOMBAT_DATA_HOME does not transfer them.
• Timing describes recorded activity and can be partial or provisional. It does not establish why work was slow, code quality, token savings, or model performance.
• A sharing summary removes direct identifiers but does not guarantee anonymity. Preview it before sharing.
• Native Codex plugin discovery and Hook registration require a compatible local Codex. Windows Hook collection remains unverified.

Verification and security

All five archives were built and exercised on their target platforms from commit cb8319b34a4a24991c7c024c2e71ad201714223c. Installers and updates verify the published size and SHA-256 digest before switching versions. GitHub provides build provenance attestations for the platform archives. Wombat reads local sources without changing them; network behavior and native handoff follow the documented privacy boundaries.

Feedback and changes

Report problems in GitHub Issues. Private security reports should follow the security policy.

Changes since v0.3.5: compare v0.3.5...v0.3.6