Cross-product workflows
Move reviewed output between products while keeping the source, destination and execution decision explicit. These workflows describe deliberate handoffs, not automatic integrations or background synchronization.
Choose a handoff
- Review and hand off source material: identify the source, destination and separate completion checks.
- Read a public page and keep a sourced note: use paid Zilch extraction, retain attribution and verify the local Markdown file.
- Move reviewed material into a coding task: supply selected source text with a bounded request, then inspect the resulting changes.
Start with the owning product
Complete each product's quickstart before combining tools. An extraction is not a saved note, an open editor is not a completed coding task, and a loop version is not a run. Carry only the material you intend to use across the boundary.
Another product's output is source material to review, not authorization to execute it. Check privacy and permissions before moving sensitive content into hosted processing or a model request.
Keep automation decisions separate
A repeated task can inform a workflow brief, but a note or conversation does not automatically create or schedule a loop. For an existing hosted candidate, follow review a loop version, then distinguish versions from runs.