Skip to content

Native Client Support Boundary

Private / test stageOwner Native clients and MCPLast verified macos@984bdf6cb7b7fe187931665a4b8d022bae8330d9 ios-candidate@9ce6595cebe8c77660f02a00be5c7a97ddcd72e1 ios-candidate@85cbdf09499ed3f5c3c37fb6ace34f8926e741f5

This page states plainly what a reader may and may not assume about the ONIX native clients. It complements ONIX macOS Client and ONIX iOS Client, which carry the verified technical detail; this page is the summary of what that detail does and does not add up to.

What is supported

  • The macOS client, at the reviewed pin, is a working WKWebView shell around the ONIX frontend with a source-verified local MCP host for AI-assisted development and read/navigate-level app control. Its identity (version 0.2.9, build 55) is verified against a specific, reviewed commit on the product's own GitHub remote.
  • The iOS client exists, at the time of writing, only as two local, non-canonical source candidates (see ONIX iOS Client). Each candidate independently implements a single-WebView shell with an origin-restricted navigation policy. Neither candidate has a canonical source reference, and this documentation set does not claim that either one ships.

Both clients, where they exist, render the same ONIX frontend that the web product serves. Any capability that exists on the web product's dashboard, screener, or strategy workspace is available through these clients only to the extent the loaded web page renders it — the native code around it does not add or remove product features.

What is preview / test-stage

  • The macOS client is private, test-stage software. No App Store listing was found for it, and it has no public download page.
  • The iOS candidates are pre-release source, unreconciled between two local commits (see ONIX iOS Client); no distribution claim is made for iOS beyond the existence of TestFlight-preparation commit history on one candidate.
  • The macOS MCP host's diagnostics capability is off by default and is reserved for support use; it is outside the local host's supported, default-scope boundary, and this documentation set does not describe what it exposes or how to enable it.
  • The iOS biometric privacy gate present in the later of the two local iOS candidates is explicitly documented, in its own source, as a shell lock rather than a finished authentication feature.
  • The macOS bridge/frontend pin parity caveat documented on ONIX macOS Client means any claim that depends on the local MCP tool registry matching the current frontend build, rather than the older frontend commit it was last verified against, carries status: unverified until that revalidation happens.

What is explicitly not offered

  • No live order placement or cancellation from native code, on either client. The macOS MCP tool registry's supported, default-scope tool set has no such tools — they were removed from the registry entirely, not merely disabled, and no default-scope configuration setting brings them back. Diagnostic scopes intended for support are disabled by default and are not covered by that support boundary. The iOS client has no automation surface at all. Where the underlying web page exposes order-related capability, that capability belongs to the web product's own scope, not to anything native code here adds.
  • No native strategy activation, sandbox start/stop, or backend/exchange/broker calls from native code. Every data or action request the loaded page makes goes through that page's own same-origin API routes; native Swift never calls the backend, an exchange, or a broker directly on either platform.
  • No completed multi-user identity model on iOS. At the earlier of the two local iOS candidates, the Release build ships no accepted ONIX identity contract at all — the native app cannot report a real signed-in state on its own. Treat any claim about "who is signed in" on iOS as unverified until a specific candidate's identity handling has been checked, and as always conditional on whether the loaded web page itself has an authenticated ONIX session.
  • No public distribution evidence for either client. No App Store listing was observed for the macOS client or for either iOS candidate. Nothing in this documentation set should be read as implying general public availability, and no page in this set should ever be read that way going forward.

What a reader should not assume

  • Do not assume either native client can execute real-money trades on its own. Neither client's native code contains order-routing logic; whatever a loaded web page can do, when it has an authenticated ONIX session, is a fact about the web product, not about the native shell.
  • Do not assume the iOS client has a settled canonical source, or that it ships. Two local candidates exist with no recorded decision between them — see ONIX iOS Client.
  • Do not assume the macOS MCP host's tool surface is fully re-verified against the current frontend build. The bridge contracts it was checked against are one frontend commit behind the frontend commit this documentation set otherwise treats as current, and that gap is an open, tracked caveat rather than a resolved one.
  • Do not assume "TestFlight" implies public or semi-public access. Where this documentation set uses the phrase, it means an invite-only, pre-release distribution channel — never an App Store listing.
  • Do not assume the local macOS MCP host's off-by-default diagnostics capability being disabled by default makes the host categorically incapable of anything beyond its default scopes. Off by default is a configuration default a user chooses, not a structural guarantee; the supported product surface is the default-scope boundary described above, and diagnostics is explicitly outside it.

Reporting an issue

This documentation set does not publish a support ticketing address or an internal issue tracker link, because doing so would either invent a channel that does not exist or expose internal infrastructure this page is required not to reveal. If you have access to the product's own support channel, use that. If you are a maintainer with repository access, the verified pins cited on this page and on ONIX macOS Client / ONIX iOS Client are the starting point for reproducing any claim made here.

Evidence and source pins for this page

Private / test stage. Exists, but is private, internal or test-stage only. Not generally available.

Verified on against the following immutable sources:

  • macos@984bdf6c:MCPServer.swift (blob 05f763c1976410fbab50937a3c3c0fdd1583727e)
  • ios-candidate@9ce6595c:docs/PLATFORM-MATRIX.md (blob 4caf73b6a2279abfe5fd78ea121b2026a55b1aab)
  • ios-candidate@9ce6595c:ONIX_iOS/OnixAuth.swift (blob 9389d2e50d08c5a4e8261c98bb0c8accd0190971)

Status tokens are defined on the documentation and status model page. Every pin on this site is listed under versions and source pins.