Captured Work
Captured work turns activity from your tools, plus closed initiatives and bugs, into progress you can read, so nobody has to rewrite it as a status update.
Completed tasks
Completed tasks are finished work shown in the Journal, Recap, standups, release notes, and Insights. A completed task can start from a todo, a finished initiative or bug, captured tool activity, agent work, or a manual Journal entry.
Connected activity
Activity from connected tools is the evidence behind completed work, planned work, blockers, and attribution:
| Activity | How it can be used |
|---|---|
| Commits and pull requests | Explain shipped code and review work. |
| Synced issues | Add issue status, assignment, and execution context. |
| Calendar events | Explain meetings and planned focus time. |
| Comments and discussions | Preserve decisions and review notes near the work. |
| Agent sessions | Attribute agent-assisted work back to the initiative, bug, or todo. |
When the match is clear, captured activity can attach to an initiative, bug, todo, or completed task. If the match is wrong, open the item and adjust the linked work.
Where captured work appears
Captured work powers Recap, Standups, Release Notes, and Insights.
In Recap, captured completed work appears in Worked on. Planned work and blockers have their own columns.
Finished initiatives and bugs
Closing an initiative or bug updates the roadmap or bug record. When the recap still needs a clear completed item for that closure, Preferences can ask whether to create a completed task, create it automatically, or skip it.
If the initiative or bug already has visible linked work, the recap can use that existing evidence instead of creating another completed task.
Attribution
Attribution links work to people, teams, taxonomy, coding tools, and agents, so recaps and Insights show who did what.
For taxonomy setup, see Taxonomy. For agent attribution in reporting, see Agent Analytics.