← Download archive
Release notes · October 2026
Beta 1.2.0.
GitHub, Google Calendar, and MCP servers join Work Mode.
What changed
- GitHub: connect through the publisher-owned GitHub App and Device Flow. Inspect repositories, files, branches, commits, issues, pull requests, and Actions runs, jobs, and logs. Issue and PR changes still require OmniCode's normal action approvals and the user's selected repository access. Real integration testing used one private disposable repository; other accounts and organization policies are not broadly validated yet.
- Google Calendar: list calendars, read events, and check Free/Busy. A separate event-management grant enables user-directed creation, edits, reminders, recurrence, Meet links, and deletion with action approvals. Gmail and Google Drive remain on the existing Google account connection.
- MCP Server Manager: explicitly configure local stdio or Streamable HTTP servers, inspect discovered tools/resources/prompts, and enable individual tools. New or changed tools start disabled. Server-specific bearer credentials and supported OAuth grants use macOS Keychain; no GitHub or Google connector token is copied into MCP settings. One hosted read-only MCP server and local test servers were verified; broad third-party OAuth interoperability is not yet validated.
- Reliability and security: concurrent Google-service checks share one token refresh; GitHub Actions log redirects are narrowly guarded; hosted-MCP DNS checks reject private addresses. ToolRegistry validation, PermissionManager approvals, Google data-provider restrictions, and Keychain storage remain in force.
Google integration availability
Verification pendingGoogle has verified OmniCode's branding, but its OAuth Data Access verification has not been submitted or approved. The publisher app is External / In production; Google may show an unverified-app warning, limit new authorizations under its lifetime user cap, or block access under an account or organization's policy. A test account completed real Calendar operations while retaining Gmail and Drive. This is not a promise that every account can connect. Do not bypass Google or organizational security restrictions.
A genuine OAuth demonstration video and verification submission are being prepared in parallel with this beta. The app does not present itself as Google-verified.
Compatibility and updating
Current supports macOS 15 or newer; Sonoma Legacy supports macOS 14. Each edition has Apple silicon ARM64 and Intel x64 installers. Beta-channel installations can discover a compatible newer beta and verify the DMG by size, SHA-256, and macOS disk-image validation. Installation remains manual.
Ad-hoc beta distributionThe DMGs are ad-hoc signed and not notarized. Automatic app replacement is disabled until a Developer ID signed and notarized release exists. macOS may require a first-launch Open Anyway decision in System Settings → Privacy & Security. Keep Gatekeeper enabled.
Earlier installers, URLs, and checksums remain in the archive. Sonoma Legacy and Intel artifacts are cross-built and validated; they are not claimed to have been runtime-tested on macOS 14 or Intel hardware.