One ticket, many execution surfaces
Launch or resume work from the web app, desktop app, CLI, MCP, or an installed agent plugin.
Claude planned, now I want Codex to implement. How do I keep the context?
Move work between agents without starting over.
Overlord is deliberately agent-neutral. Codex, Claude Code, Cursor, Gemini, OpenCode, MCP tools, terminal workflows, and desktop agents can all report into the same ticket record.
Shared context travels with the objective
Agents can read prior activity, uploaded artifacts, stored context, and previous deliveries before continuing.
Use the right agent for each phase
Plan with one agent, implement with another, and review or follow up with a third while preserving continuity.
Tickets & Objectives
Tickets are the durable record for a thread of work. Each ticket holds one or more objectives: the units of work the agent actually executes.
Overlord1:1098
Slack notifications for ticket activity
Due in 3 daysNo schedule
notificationsslack
Build the user notification preferences UI in Settings → Notifications. Let users opt in/out of categories (mentions, deliveries, blocking questions) and choose a delivery channel (Slack DM via the org bot, or shared channel). Persist preferences in `user_notification_preferences`.
Add notification filtering and quiet hours. Users should be able to mute notifications by project, by ticket priority, and during a daily quiet-hours window in their local timezone.
End-to-end tests for the notification flow: simulate a ticket lifecycle (attach → ask → deliver → status_change) and assert the correct sequence of Slack messages is posted, that retries fire on 5xx, and that user preferences correctly suppress unsubscribed categories.
Agent-readable detail
Agents should treat Overlord as the handoff source of truth before resuming work from another tool or session.