Getting Started & Migration
How do I structure my first Catalyst durable agent project so that the business logic remains testable independently of the durable execution runtime?
Separate agent logic into plain functions and orchestrate them with Catalyst workflows to keep unit testing lightweight. Encapsulate business decisions in pure handlers that receive state, and use the workflow definition only for ordering steps and error recovery; test handlers with mocks. This separation allows fast local iteration without the execution engine. Be aware that subtle coupling can arise if workflow context leaks into handlers, so review shared objects carefully.
Was this article helpful?
Your feedback helps improve Diagrid's FAQ experience.
Keep reading
More Diagrid FAQ articles
- Getting Started & Migration
What does a minimal but realistic durable agent look like when I first run Catalyst locally?
A realistic durable agent prototype that progresses from a call to an LLM through a conditional action to an API, illustrating automatic state persistence.
- Getting Started & Migration
How do I iterate quickly on durable agent logic without deploying to a shared cluster?
Use a local Dapr sidecar to execute and debug agent workflows, enabling a fast edit-run-debug cycle without remote dependencies.
- Getting Started & Migration
My agent is already built with LangChain/LlamaIndex. Can I add durable execution without a rewrite?
Wrap an existing agent’s entry point in a Catalyst workflow to gain durability without modifying framework internals, then progressively refactor.