How to

Sync work-item context

Fetch provider context or record complete context manually.

What changes

sync stores provider-neutral issue context with the Mission. When the configured work provider reports issueContext: true, it fetches validated remote data; otherwise it records manually gathered evidence from a local Markdown file. It does not mutate the work provider.

When this helps

The configured work provider reports native issue context and the Mission needs current remote data.
The issue.sync flow step is waiting for provider context.
The configured work provider does not report issue context and the Mission needs complete manually gathered context before planning.

Run this command

terminal

$sumr mission sync SMR-123# configured provider context$sumr mission sync SMR-123 --json# context as JSON$sumr mission sync SMR-123 --from issue-context.md# manually gathered work-item context

Flags you can use

--from <file>

Record manually gathered issue context from a local Markdown file.

--allow-custom-key

Accept a work key that does not match a configured work-provider prefix. Use only for local or intentionally custom work.

--json

Return a structured JSON envelope for scripts, CI jobs, and AI assistants.

--help, -h

Show the command syntax, supported flags, and examples without changing files.

Keep in mind

Run mission providers --json first. Check issueContext, comments, attachments, workflowState, and projectContext independently, and record any unavailable source as a context gap.
When issueContext is false, the issue.sync step requires --from <file> with substantive, placeholder-free evidence.
A failed native sync records a blocker and returns the reason with the next action.