Agent showcase.
Quick Start
How It Works
Simple
Agents: 1 — Single task requires only one agent.Workflow
- Receive input prompt
- Process with LLM
- Return generated content
Setup
Run — Python
Run — CLI
Run — agents.yaml
Serve API
Advanced Workflow (All Features)
Agents: 1 — Single agent with memory, persistence, structured output, and session resumability.Workflow
- Initialize session with unique ID for resumability
- Configure SQLite persistence for conversation history
- Process input with structured Pydantic output
- Store results in memory for future context
- Resume session later with same session_id
Setup
Run — Python
Run — CLI
Run — agents.yaml
Serve API
Save Output to File
Save agent responses to files using different methods:- write_file Tool
- Task output_file
- Manual
Agent decides when to save:
Monitor / Verify
Cleanup
Features Demonstrated
| Feature | Implementation |
|---|---|
| Workflow | Single-step content generation |
| DB Persistence | SQLite via memory_config |
| Observability | --verbose flag |
| Resumability | Session with session_id |
| Structured Output | Pydantic BlogPost model |
Best Practices
Start here before reaching for tools
Start here before reaching for tools
A plain Agent handles most text tasks. Add tools only when the job genuinely needs live data or actions the model cannot perform alone.
Keep instructions specific
Keep instructions specific
The single instruction shapes every response. A precise role — “content writer, output Markdown” — beats a vague “be helpful” for consistent results.
Add memory for multi-turn work
Add memory for multi-turn work
Set
memory=True when a task spans several messages so the agent keeps context instead of treating each call as new.Save output when generating at scale
Save output when generating at scale
Use a Task with
output_file or a file-writing tool so generated content lands on disk automatically.Related
Add a search tool for real-time information.
Chain prompts for multi-step workflows.

