Skip to content

[Tracking] Cowork hardening — exit criteria for promoting cowork out of experimental #933

@sergio-sisternes-epam

Description

@sergio-sisternes-epam

Tracking issue grouping all follow-ups required to promote the cowork experimental flag to GA. Spun out of #913 (cowork-skills experimental support) following the APM Expert Review Panel verdict.

The PR for #913 (#926) ships behind experimental.cowork=false by default. CEO arbitration accepted the items below as follow-ups behind the flag, but all security items in #925 are hard gates on flipping the flag default to true or removing it from FLAGS.

Exit criteria for GA

Security (BLOCKING)

Security (tracking, non-blocking)

Maintainability (non-blocking, recommended)

Documentation gate

Before flipping the flag default:

  • Refresh docs/src/content/docs/security-model.mdx to reflect that cowork writes into a surface ingested by M365 Copilot.
  • Move cowork from docs/src/content/docs/reference/experimental-flags.mdx into the standard install/targets reference.
  • Update CHANGELOG with promotion notice and any behavioural deltas vs the experimental version.

Out of scope for this tracker

  • Adding new cowork-host targets beyond M365 Copilot (separate proposal).
  • Cross-platform OneDrive resolver hardening for Linux (no current path).

How to close

Close this issue once #925 is closed, the documentation gate items are checked, and the cowork entry is removed from FLAGS in src/apm_cli/core/experimental.py. #922, #923, #924 do not block closure but should be linked in the closing comment with their final state.

/cc panel review: #913, PR: #926

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/docs-sitedocs/src/content (Starlight), README, doc generation.area/multi-targetMulti-target deploy spec, target directory creation, agent surface routing.experimentalstatus/acceptedDirection approved, safe to start work.status/triagedInitial agentic triage complete; pending maintainer ratification (silence = approval).theme/securitySecure by default. Content scanning, lockfile integrity, MCP trust boundaries.trackingtype/featureNew capability, new flag, new primitive.

    Type

    No type

    Projects

    Status

    Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions