Daily Recap
Your daily recap is the heart of One Horizon.
It’s an AI-powered cockpit showing what you’ve finished, what’s next, and what’s blocking you.
Automatic work capture
One Horizon connects to your tools and converts commits, pull requests, issues, and calendar events into meaningful tasks. The AI summarizes them into context-rich updates so you see progress, not raw activity.
Team Journal
Shows completed tasks from the past three days. This view keeps you focused on recent accomplishments without overwhelming you with history.
Planned
Displays what you're preparing to work on next, including custom tasks, calendar events, and in-flight issues synced from your integrations.
Issues come from connected trackers based on their status and activity. Stale issues are filtered out automatically so only relevant work appears. For details on how each tracker determines planned work, see Jira, Linear, Google Calendar, or GitHub integration docs.
If something gets blocked, drag it from Planned to Blockers. You can drag it back once you're unblocked.
Blockers
Highlights tasks, issues, or pull requests that you can’t move forward with. Blockers stay visible until resolved.
For your complete task overview, see Journal.
Snoozing tasks
Snooze a task to hide it from your recap temporarily. The task stays in Backlog and is findable via search, but it drops out of your Planned and Blockers columns until the snooze expires.
To snooze a task, open its context menu (⋯) and pick a duration:
- 1 day
- 3 days
- 1 week
- 1 month
When the snooze expires the task reappears automatically in the column matching its status — no refresh needed. You can unsnooze at any time from the same context menu.
Snoozing is personal. Your snooze settings don’t affect what teammates see. Snooze changes sync instantly across your open tabs.
Only tasks with a status of Planned, In Review, Blocked, or In Progress can be snoozed.
Refreshing your recap
Each column has a reload button to update its contents on demand.
Tasks versus Issues
A task is a unit of work that is either created by AI or manually by you.
An issue is a work item synced from integrations like GitHub or Jira (e.g. tickets, pull requests).
For more terminology, see Concepts.
Creating work items
Click the add button in any recap column to create a new item. The type selector lets you choose what kind of item to create.
Worked on and Planned columns
In the Worked on and Planned columns, you can create a Task, Bug, or Initiative. The item's status automatically matches the column — completed for Worked on, planned for Planned.
When adding a completed task, you can set the completion date (today, yesterday, or up to 10 days ago).
Blockers column
In the Blockers column, you can create a Task, Bug, or Initiative. All items are created with a blocked status.
Task states
Task has a state that determines where it appears in the recap.
| Icon | State | Column | Description |
|---|---|---|---|
| Completed | Team Journal | Finished tasks | |
| In Review | Planned | Work under review | |
| Planned | Planned | Next up | |
| Blocked | Blockers | Blocked items |
Custom tasks don’t support “In Progress.” Once a task is planned, you can start working on it.
Issue states
Issues synced from Jira and Linear retain their native state options from those platforms. If you update the state of an issue, it will automatically update the state in Jira/Linear.
Sending tasks to your AI tool
Every task has a Send to app button. It builds a context-rich prompt — title, description, linked initiatives, labels — and opens it in Cursor, Claude, or a terminal.
When a dialog opens, choose the mode that fits the stage of the work:
- Plan — break down the work before starting
- Build — jump straight into implementation
- Review — check whether the work is done
The dialog includes a Move to In Progress checkbox. When checked, the task moves to In Progress as soon as the prompt is sent. The checkbox is on by default for tasks in Open, Planned, Blocked, or Idea status.
Completed tasks only offer the Review mode.
Managing tasks
Tasks can be reordered, renamed, edited, deleted, split into subtasks, and moved between Planned and Blockers with drag and drop.
From the status menu, tasks can be marked as Open, Planned, In Review, Blocked, Completed, or Cancelled.
Moving a task to Completed automatically updates its title to past tense. You can also use "Discuss offline" to bring a task into Slack for team discussion.
Tasks sort with newest items first by default.
Task & Issue details
Each task and issue has two ways to open it:
- Quick view — opens a drawer alongside your recap with the full details: title, description, labels, integration source, and metadata such as due dates and assignees.
- Open details — navigates to a dedicated details page for the item.
Use Quick view when you want to check context without leaving the recap. Use Open details when you need to work with the full task or issue in its own page.
Copying a task link
Every task card has a Copy link option in its context menu (⋯). The task detail panel and full-page detail header each show a copy button next to the title. Clicking it copies the direct URL to your clipboard so you can share the link anywhere.
Watching tasks
In task or initiative details, use Watch to follow an item without changing its owner or assignees.
The Watchers field shows everyone following that item. When someone comments or updates it, watchers receive notifications.
Task comments
Use comments in task details to keep discussion attached to the work item. Every top-level comment supports replies, so decisions stay in one thread.
Submitting comments
Press Cmd+Enter (macOS) or Ctrl+Enter (Windows/Linux) to submit a comment from the keyboard. The editor clears immediately so you can continue the conversation without reaching for the mouse.
Replying in context
Click Reply on a top-level comment to answer in context. Replies are shown under the parent comment.
Reactions
Use emoji reactions to acknowledge updates quickly. Click an existing reaction to remove your own reaction.
Task link chips
Paste any One Horizon task URL into a comment and it renders as an inline chip showing the task title and status. Click the chip to open that task directly. This works in comments, issue descriptions, and pull request details.
If a parent comment has replies and then gets deleted, the original text is removed but the thread stays visible. This keeps reply context intact.
Task visibility
By default, your team members can view all your tasks. You can set tasks to private so only you can see them.
For issues, you cannot toggle visibility as your team members can most likely see your issues anyway (in the respective integrations like Jira).