Agency workflows
Plan a bounded client workflow and validate actual outcomes.
Start with one bounded workflow
A good first evaluation has explicit inputs, a narrow set of tools, observable output, and a human reviewer. Examples include preparing a campaign report from exported data, drafting response suggestions, or summarizing a non-sensitive document collection.
These are workflow ideas, not preinstalled integrations or guarantees that the engine can operate your business systems out of the box.
Configure a client profile
- Use a dedicated home and workspace for each client.
- Use separate operating-system/container identities and credentials where isolation matters.
- Write a task-specific
system_instruction.md. - Enable only tools required for that workflow.
- Define a result validator and an operator who reviews failures.
- Back up settings, session state, and required inputs.
Before external actions
Business systems need their own authorization, input validation, and repeat-safe handling. An uncertain response can follow a successful external write; a blind retry can duplicate the action. Use durable action IDs and remote idempotency support where available.
Interactive approvals, durable per-job completion, tenant isolation, shared parent/child budgets, and operational alerting are not complete product features in v0.1.1. Build and validate these controls before unattended client use.
Validate actual outcomes
Measure correctness, operator intervention, elapsed time, and model/tool usage against representative cases. Include missing data, invalid inputs, provider outages, tool failures, interrupted streams, duplicate submissions, restarts, and hostile instructions in documents.
Do not infer success from the agent saying “done”. Verify the file, draft, calculation, or remote state that the workflow is meant to produce.
Distribution
The downloadable packages contain compiled engine executables, quick-start information, and third-party notices. Engine source is not provided. Customization uses documented configuration files and tool interfaces, so no engine rebuild is required.