Prompts become durable objectives
Capture the ask, constraints, working directory, project, and acceptance criteria before execution starts.
What did I ask this agent to do 20 minutes ago?
Keep the original ask attached to the work.
Overlord lets you group prompts into Objectives, creating a durable record of context, acceptance criteria, target repo, updates, and delivery history. The work record remains readable after the terminal session, chat, or agent run is gone.
Every update stays with the ticket
Progress notes, blocking questions, artifacts, and delivery summaries build a timeline you can review later.
Follow-up work stays sequential
Add another objective to the same ticket instead of opening a new chat that has none of the original context.
The Feed
Each ticket becomes a feed post that lets you explore the objectives, file changes, and delivery summaries.
Project checkpoints can now be pruned from settings
SignificantTicket summary
New Checkpoints page in Project Settings with a scrollable table, row-level delete, and a one-click prune-stale flow. The backing server action commits a transaction so partial-state races are impossible.
27 events7 files1 actionuisettingsgit
#
Objective
Files
Time
Ticket-level changes
Mapps/web/app/sitemap.ts+3 −1
Action required
- •Confirm the Checkpoints page appears in your Project Settings sidebar.
Single-transaction prune in a server action
Alternatives: Client-side loop over individual deletes
Rationale: One transaction prevents partial-state UI on flaky connections and is faster on large checkpoint sets.
Write safety ref before hard reset
Alternatives: Rely on reflog alone
Rationale: Named safety refs survive aggressive `git gc` runs; reflog entries can be pruned.
Tickets created
Agent-readable detail
Agents should attach to the ticket, read the objective, post meaningful progress, and deliver with a summary tied back to the original ask.