Review known limitations

Oore maintainers own this list. Its maintained sources are the shipped runtime and public CLI contract. These are the maintained public boundaries for Oore 0.1.x. Report a mismatch against current behavior through Report an issue.

Product maturity

• Oore is in public alpha. APIs, configuration formats, and CLI flags may change across 0.1.x.
• stable names the default update stream; it is not a 1.0 maturity or uptime guarantee.

Platform and execution

• Guided bootstrap, install, setup, and service management support macOS on arm64 and x86_64 in v0.1.42.
• Published Linux web archives are standalone assets. They are not a guided Web node installation and do not have the managed lifecycle.
• The five guided profiles are Complete, Control plane, Runner, Web node, and CLI only.
• Embedded and hybrid build execution are unsupported.
• Direct runners execute repository commands with the runner account’s host permissions. They are not hostile-code or same-account credential sandboxes.

Installation lifecycle

• The download script installs only the verified Oore CLI. Run oore install to select and install a device profile.
• Direct oore update supports Ready Complete and Control plane installations. Use oore-web update on a separate Web node.
• oore install does not replace live profile components across releases. Run normal oore uninstall first. It preserves Oore data.
• After normal uninstall, rerun the bootstrap with the recorded values. Then install the same profile with oore install --profile <existing-profile>.
• The v0.1.42 bootstrap accepts only the exact service-managed v0.1.41 legacy layout. Its verified candidate offers a preserve-data removal plan first.
• Other pre-manifest layouts remain unsupported. Preserve their data and use their matching deployment procedure before the v0.1.42 bootstrap.
• Normal oore uninstall preserves Oore data. The --purge flag also removes the validated install root and canonical data after ownership and path checks.

Access and browser clients

• Local Only login is passwordless and loopback-only. External Access has no ordinary local bypass and supports no local password.
• ci.oore.build hosts static UI assets only. It cannot call an HTTP loopback backend from its HTTPS page and is not a default allowed backend origin.
• Adding a browser instance does not check readiness. The current UI does not remove saved instances.

State, storage, and recovery

• Oore state backups do not include local artifact payloads or S3/R2 objects.
• Manual backup and restore are documented only for the default managed database/key layout.
• S3/R2 configuration does not create buckets or own provider policy, retention, availability, or backup.
• Artifact and install links expire; the target browser or device still needs a network path to the delivery endpoint.

Authentication and signing

• External Access (OIDC) examples must supply the exact frontend /auth/callback URI.
• Signing runs within the trusted Direct-runner boundary. Do not treat signing configuration as isolation from repository code or the runner account.

Next step

Choose a supported path from Operate Oore, or report a reproducible issue when behavior does not match a boundary above.