Start from a template
Open Evidence to insight for parallel investigation and critique, or Evaluate and refine for a conditional evaluation with bounded repeat rounds. Saving changes to a built-in template creates a copy. The original stays available.
Use Cancel creation to leave an unsaved new workflow. An untouched draft closes immediately; edited drafts ask before discarding changes. All workflows returns from an existing workflow. Save stores a custom workflow; Save a copy preserves a built-in template.
Connect research steps
Add research, custom tool, condition, join, repeat, and finish steps. Hold the primary or middle mouse button on empty canvas space and drag to pan. Zoom buttons adjust the scale; Fit fits the graph width and returns to its origin. Arrow keys pan a focused canvas. Drag a step by its grip or move a focused grip with arrow keys. Click an output port and an input port to connect them, or use the connection pickers in the settings panel.
Artifact connections pass retained, currently authorized research artifacts. Signal connections control execution order without passing artifacts. A condition has yes and no outputs. A join waits for all paths, including skipped branches. Repeat runs a research step one to five times; arbitrary cyclic connections are rejected.
Run and follow the work
Save the graph, choose a project, and assign a research question with selected inputs. Choose whether to review each research plan. The graph runs on the server and continues after you leave the page.
Research activity links each step and repeat round to its conversation. Answer questions or approve plans there. Stop workflow cancels active steps and prevents further steps. The graph shares its total allowance across the maximum number of research steps and rounds. Project-wide limits still apply.
Schedule recurring research
Choose Daily on the trigger step, save the workflow, and enable the schedule when starting a run. It runs at most once per UTC day when the deployment scheduler wakes, using the saved question and inputs. It does not overlap an unfinished run of the same workflow.
Stop schedule prevents future daily runs. Stop workflow controls the current run separately. Changes to the saved workflow or unavailable dependencies require starting a new schedule.