Workflow
Overlord is built around objectives, tickets, and projects. Objectives are the unit of work; tickets group shared-context objectives into a higher-level goal; projects group related code and resources.
The normal flow
- A user creates a ticket.
- The user adds the first objective to describe the next concrete task.
- The objective becomes the structured prompt and execution record for that agent pass.
- The user can attach files to the objective and choose which agent should execute it.
- The user sends it to an agent in the tool they already use.
- The agent works and reports progress back to Overlord.
- The user reviews updates, answers questions, and evaluates deliverables.
- The ticket stays as the durable record of the work, and the user can add another objective if a follow-up pass is needed.
Tickets and objectives
Think of the ticket as the durable container and each objective as the next instruction in that same work thread.
That lets users keep planning, implementation, review, and follow-up passes together without opening a new chat or restating the full history.
What this model gives you
- a shared system of record
- less prompt drift across tools
- clearer handoffs between human and agent work
- a reliable review surface