Otto v0.1.0-alpha.4 — reviewed native fills

Otto Alpha.4 adds reviewed native form fills and experimental task dictation.

Known live issue: after Accessibility access was restored, a guided TypeSafe task reached one approved action and then stopped with “TypeSafe returned an invalid decision. No action was taken.” This is being investigated. Successful installer checks do not establish live guided-task success.

• Fill a form: supply exact text values, review the complete change set once, and receive a native readback receipt. This workflow requires no provider key and makes no model requests. It does not issue Submit, click, or keyboard actions; the target app can still autosave or react to edits.
• Checks between every write: selected process/window/control identity, expected values, form structure, and final readback. Changed, disappeared, duplicated, or rejected targets stop the batch. Earlier edits can remain; there is no rollback guarantee.
• Task dictation: optional native speech-to-text adds to an editable draft. It never starts a task or approves an action. On-device availability depends on the OS, language, and permissions; live microphone recognition remains unverified.
• Usage receipts: Jev attempts and responses, actual reported models, input/output usage, and unknown usage are retained. Failed or cancelled calls with missing counters are not counted as free.
• Guided tasks: TypeSafe-only mode uses your TypeSafe key; Hybrid also requires an OpenAI Platform key. The scoped MCP interface remains read-only inspection and preparation.

Validation includes 109 automated tests, seven real macOS native-form fixture cases, and browser renderer checks for review, mismatch recovery, Stop, permission-return events, dictation events, keyboard focus, and overflow. The native batch cases used an independent fixture state oracle, made zero provider requests, and retained earlier failed runs. These are bounded authored cases, not a live Jev comparison or a billing/speed claim. Windows reviewed batches and live speech recognition have not been validated. Browser mock checks do not establish Electron IPC or OS permissions.

Installation: macOS Apple Silicon and Intel bundles use ad-hoc integrity signatures checked by release CI. They are not Developer ID signed or notarized. The Windows x64 installer has no publisher signature. After a Mac update, an enabled Accessibility entry can still refer to the old build; if access remains unavailable, remove the old Otto entry and add the final installed /Applications/Otto.app again. OS approval is required. The local installed app regained Accessibility access after its OS entry was renewed. That grant does not establish successful guided tasks; see the known live issue above.

Downloads include macOS DMG/ZIP files, the Windows installer, and SHA256SUMS.txt.

Setup and source · Validation and limitations · Native batch evidence · Form-fill contract

Otto v0.1.0-alpha.3 - unsigned alpha

Otto now keeps the task, current decision, and selected app in a focused desktop workspace. Setup moves into searchable app and provider dialogs; routine activity stays expandable; exact action review and completion verification remain distinct.

• Improved keyboard focus, small-window Task/App views, scrolling, loading and error recovery.
• New source-build MCP tools: list_apps, inspect, and prepare_fill. Preparation is read-only and does not execute actions or bypass approval.
• Removed duplicate Jev candidate data. Reproduce the offline UTF-8/tokenizer comparison with npm run benchmark:context; counts are not provider billing or demonstrated task success.
• Validation: 70 automated tests, macOS/Windows CI, actual Electron fixture flows at 1280×820 and 900×660, and eight native macOS fixture checks.

See the developer setup, measurement details, and design assessment.

These are unsigned alpha builds for macOS Apple Silicon/Intel and Windows x64. They are not notarized or publisher-signed. The desktop agent requires your own TypeSafe key; Hybrid also requires an OpenAI Platform key. The MCP observation/preparation tools require no provider key. Live provider quality, end-to-end cost savings, and broad app compatibility remain unmeasured. SHA256SUMS.txt contains installer checksums.

Otto v0.1.0-alpha.2 - unsigned alpha

Unsigned alpha build for early testing.

• macOS: Apple Silicon (arm64) and Intel (x64); no Developer ID signing or notarization.
• Windows: x64 installer; no publisher signing certificate.
• Supply your own TypeSafe key. Hybrid mode also needs your own OpenAI Platform key.
• CI checks unit tests, compilation, and the read-only native protocol. It does not establish full desktop automation compatibility.
• See the repository README for setup, permissions, and known limitations. SHA256SUMS.txt contains asset checksums.

Otto v0.1.0-alpha.1 - unsigned alpha

Unsigned alpha build for early testing.

• macOS: Apple Silicon (arm64) and Intel (x64); no Developer ID signing or notarization.
• Windows: x64 installer; no publisher signing certificate.
• Supply your own TypeSafe key. Hybrid mode also needs your own OpenAI Platform key.
• CI checks unit tests, compilation, and the read-only native protocol. It does not establish full desktop automation compatibility.
• See the repository README for setup, permissions, and known limitations. SHA256SUMS.txt contains asset checksums.