Skip to content

Latest commit

 

History

History
44 lines (34 loc) · 2.11 KB

File metadata and controls

44 lines (34 loc) · 2.11 KB

Backlog

GitHub issues are the active work queue. Release status records qualification; the changelog records shipped work. This file keeps only open product direction.

Stable v0.4.0 is published with native stock-OMP integration and a passed core qualification matrix. Candidate qualification and the published-byte local/Android smoke are complete; exact evidence and remaining limits live in the release ledger.

Current

  • Investigate the initial local View→Control upgrade failure whose cause remains undetermined, despite subsequent passing probes and the full published-byte smoke.
  • Close the pending-launch service-worker update gap: the launch still occupies / until capability resolution, contrary to the prelaunch route reservation described in ADR-018.
  • Qualify the specialized attention and branch/resume scenarios separately from the core matrix.
  • Qualify background Push on the advertised physical Android/browser combination.
  • Decide whether to advertise Windows only after exact mainline discovery and signed-candidate install/reboot-login/upgrade/rollback/uninstall acceptance.
  • Track upstream discovery/query compatibility after PR #11908 (4999b98bd5), shipped in v18.1.20; consume the supported seam rather than maintaining a downstream OMP patch.

Candidate follow-ups

  • WebAuthn/passkey verification before Control launch.
  • Session aliases, favorites, and per-session control policy.
  • More granular tailnet/device posture guidance.
  • A separately threat-modeled signed update mechanism.
  • Physical Android qualification for closed-PWA, force-stop, lock-screen, stale-notification tap, and network-change Push behavior.

Later or optional

  • A qualified self-hosted relay deployment mode.
  • Trusted Web Activity packaging.
  • Multiple desktop hosts with explicit grouping.
  • Read-only family or team dashboard roles.

Not planned

  • A native Android collaboration client.
  • A public hosted control plane or Tailscale Funnel support.
  • Transcript indexing or persistence in the gateway.
  • Replacing OMP's UI or collaboration protocol.