Skip to content
AssureSwarm Docs

Agent Operating Guide

/bridge-archer-sync

Bi-directional sync that keeps Cowork Canvas issue and remediation-task records in step with Archer: Canvas updates push out, Archer-owned changes return as suggestions.

Keep your Canvas issue and remediation-task records in lockstep with Archer. Outbound, the skill pushes Canvas updates to Archer through its API. Inbound, every Archer change, substatus, remediation progress, Archer-owned fields, lands as a suggestion via suggest_change for a human to approve; nothing is written to your tenant directly. You configure the field mapping once with /bridge-mapping-edit, and subsequent syncs are mapping-driven, conflict-aware, and idempotent.

When to use

Section titled “When to use”

When you run issues and remediation tasks in both Canvas and Archer and need them consistent without dual entry. Pull Archer substatus and remediation progress into Canvas, push Canvas issue updates out to Archer, or run both directions in one pass.

Inputs

Section titled “Inputs”
Flag Required Notes
--push / --pull / --both No Sync direction. If omitted, the skill asks. Both is the default.
--since <ISO> No Override the last-sync watermark to re-pull or re-push from a chosen point.

Example

Section titled “Example”

/bridge-archer-sync --pull reads each Archer record changed since the last pull, applies your field mapping in reverse, and submits one suggest_change per record: writing substatus and remediation progress into the mapped Canvas custom fields. You review and approve the batch in Canvas; nothing changes until you do. If the same field changed on both sides since the last sync, that record stops and the conflict is surfaced rather than auto-merged.

Good to know

Section titled “Good to know”
  • Inbound is always proposed, never direct: a pull creates suggestions in the Canvas approval queue, and approval is a separate human step.
  • When both sides changed the same field since the last sync, the skill does not auto-merge: it hands the conflict to /bridge-conflict-resolve for triage and holds that record until it’s resolved.
  • Pulled remediation completion is the usual trigger to kick off a validation step on the Canvas side.
  • Check sync health, open conflicts, and last pull/push times any time with /bridge-sync-status.
Section titled “Related”