Skip to main content
You now have a deployed agent platform with evals, JWT auth, and a set of coding-agent skills that cover the full lifecycle: create → improve → evaluate → maintain. The sections below cover the next level: teams and workflows for multi-step logic, scheduled tasks for proactive runs, and interfaces that put your agents where your users are.

Going beyond agents

Teams come in four modes:

Scheduled tasks

The scheduler is on by default in app/main.py, and the template prepares two workflows for scheduled runs: Schedule your own agents and workflows the same way: See scheduling for the cron API.

Connect to interfaces

Connect agents to Slack, Telegram, WhatsApp, or a custom UI inside your product. Expose the agent via an interface in app/main.py:

Keep the repo coherent

As you ship more agents, configuration drifts, env vars rot, and new agents miss imports. The template ships a fifth skill for the recurring sweep:
It auto-fixes mechanical drift (stale paths, missing example.env entries, agents on disk not registered in app/main.py) and surfaces the rest as a punch list. Run it before public releases and periodically during active development.

You’re done

You now have a platform that runs locally and on Railway with JWT auth, persists sessions, memory, and traces in Postgres, supports Postgres-backed knowledge, and includes five coding-agent skills for ongoing development and maintenance.