Oprill / Agent builder
Design the path before you run it.
A visual workflow concept for turning a repeated task into a sequence that another person can understand and inspect.
Product concept · Interactive website preview
Give repeated work a visible sequence.
Name the input and expected output of each step before connecting them. Keep the final deliverable narrow enough for a person to review.
Explore compose
The example is a design exercise and does not execute a workflow.
The outline distinguishes changes from background context.
Illustrative exampleDefine what a step may decide.
A step can choose which notes are relevant without deciding that a project is ready to launch. Make the limits of its judgment explicit.
Explore reason
A decision boundary should be written in the brief rather than assumed from a step name.
The workflow prepares evidence for the project owner.
Illustrative exampleTranslate a plain-language brief into inspectable steps.
A short description can be the starting point for a workflow design. Inspect the resulting structure before accepting it.
Explore describe
This page does not generate code or create a deployed agent from a prompt.
The plan remains open to revision by its author.
Illustrative exampleKeep the knowledge boundary attached to the workflow.
Choose approved sources and define the behavior when they are unavailable. Missing access should produce a clear blocked state.
Explore connect
There are no connected sources here; the exception is synthetic.
The design stops instead of using an unauthorized source.
Illustrative exampleCompare revisions without losing the original intent.
A workflow change should make clear which step changed and how the acceptance condition is affected. Preserve a useful baseline for review.
Explore iterate
The page shows a versioning concept without storing revisions or a project history.
The new step prevents an older note from silently driving the update.
Illustrative exampleAgent builder in context
Build a weekly project update from approved notes.
Interactive illustration with synthetic content. No AI model or company system is connected.
Project: Atlas / Period: this week / Source: team notes
The starting brief contains a project, a period and an approved source.
If a required input is missing, stop and ask for it. A guessed project or time range can make an otherwise well-written update misleading.
Collect notes → Identify changes → Draft update
The draft separates completed work, current risks and next decisions.
A useful builder should expose how a step transforms its input. Here, comparison produces a change list before any summary is drafted.
Test case: no approved notes / Expected: request context
No update is invented when the input is empty.
This is a browser-local walkthrough of a design, not an executable agent builder. No model, external source or deployment is connected.
Knowledge keeps its context
Different sources. Distinct responsibilities.
Original source examples for agent builder. These symbols represent information types, not connected applications.
Understand the concept. Keep the decision.
These original examples explain a possible approach to agent builder. Oprill’s website does not run AI agents, connect to company data or carry out external actions. Your selections stay in this page and reset when you reload.