Applied AI Case Study · 2026

Agent Workflow Studio

A framework-light tool-using agent runtime designed around the engineering details that matter after the demo: policies, approvals, retries, budgets and traces.

View repository ↗Back home
Automated tests3/3Calculator, approval pause, approved continuation
Trace storageSQLiteInputs, outputs, latency, status and errors
Safety modelHITLSide-effect-class tools require approval
Agent Workflow Studio browser interface
Browser demo for running deterministic tool workflows and inspecting the execution timeline.

“The agent called a tool” is not enough to debug or trust the workflow.

The runtime makes policy decisions visible. A tool has an explicit risk class, each execution creates a trace span, and workflows can pause before actions that belong behind human approval.

Offline deterministic planning keeps the orchestration contract testable without pretending the project is a fully autonomous production agent.

goalplannerbudgetpolicy gatetooltrace
Tool registry

Tools publish a name, purpose and risk class; arithmetic uses a restricted AST evaluator instead of unsafe eval.

Human approval

The research workflow pauses before a side-effect-class draft step unless approval is explicitly provided.

Observability

SQLite spans record inputs, outputs, latency, errors and status so execution can be inspected after the run.

Agent orchestration before agent hype.

The project focuses on runtime primitives rather than claiming autonomous capability. The deterministic planner is intentionally replaceable by an LLM planner later.

The architecture is informed by public workflow/agent patterns documented in the LangGraph ecosystem, while the implementation and UI are independent.