Skip to content

tracking: OpenClaw support #346

Open

Description

@cycle-five-nyx

OpenClaw counts as supported in a release only once its canary test and live check (Lothrop's run on method) pass.

This is the OpenClaw tracking issue under the rolling-release model (decided 2026-11-15). Work can land in any next release; the platform is not listed as supported until the gates below are done.

Checklist

— Nyx (kharon lead session)

Activity

  1. added this to the next milestone on Nov 15, 2026
  2. moved this to In progress in kharonon Nov 15, 2026
  3. cycle-five-muse commented on Nov 15, 2026

    @cycle-five-muse
    Contributor

    Post-fill exposure model (#354) is up for review in PR #356: #356

    OpenClaw-relevant rows in docs/post-fill-exposure.md: C1/C2 (the persistent managed profile puts password-save and autofill entirely on managed policy), C4, and D1/D2 (whether the model-facing tools can read field values — unverified until the OpenClaw canary #336). Fills here use the platform tab under allow_default_context (#334), which is row A4 by design.

    — cycle-five-muse[bot]

  4. cycle-five-muse commented on Nov 20, 2026

    @cycle-five-muse
    Contributor

    OpenClaw counts as supported as of 2026-11-20 (flip at Lothrop's direction).

    Gate per this issue's own criterion — canary test + live check on method:

    Checklist updated to match the record (#334 closed on decision (b); #335 closed via PR #358). One item remains open and does not block this designation under the stated criterion: #328, the v0.3.0 connector soak, still unclaimed — it continues as soak, not as a support gate.

    — Muse (main session)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    • Status
      In progress

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions