Getting startedCreate your first initiativeConnect version controlInvite your teamPlan today's work
StatusesWork TypesSearchCaptured WorkInitiativesBugsIdeasTodosDocumentsWriter ModePermissionsNotification TypesTaxonomy TypesTriage ItemsGlossary
DocsAPI Reference

Main

  • Home
  • About
  • Pricing
  • Changelog
  • Docs

Features

  • Roadmap
  • Boards
  • Triage
  • Workflows & agents
  • Progress
  • Insights
  • CLI
  • Integrations

Solutions

  • Startups
  • Dev shops / agencies
  • Software teams
  • Internal IT & platform teams

Alternatives

  • vs Jira
  • vs Linear
  • vs Asana
  • vs Monday.com
  • vs ClickUp
  • vs Notion

Company

  • Blog
  • Security
  • Log in
  • Sign up
  • Terms of Use
  • Privacy Policy

Resources

  • Docs
  • Community
  • Support
  • API reference
  • Desktop app
  • SDK
  • Vault
  • QR code generator

© 2026 One Horizon. All rights reserved

FacebookInstagramThreadsXTikTokYouTubeMedium


Todos

A todo is small, day-level work owned by one person. Add one from the Planned column in your recap, or with one create in the CLI.

Work that needs shared context, a place on the roadmap, or a brief belongs in an initiative. Defects belong in a bug.

In spec-driven development, a todo can be a small personal spec. If it needs a real brief, move the work into an initiative or bug before handing it off.

Plan cloud infrastructure expansion
Strategize scaling of distributed compression infrastructure for growing enterprise demand

Journal

The Journal is the chronological record of completed tasks and captured work. Open it when Recap is too narrow and you need to review what shipped across previous days or months.

The Journal requires a paid plan.

Planned todos appear at the top so upcoming work stays visible. After you finish one, the Journal records the result as a completed task. Completed tasks can also come from captured tool activity, agent work, or finished initiatives.

Add completed work manually

The Journal create action adds completed work manually. For work that is not finished yet, create a todo instead.

Todo fields

FieldPurpose
StatusShows whether the todo is planned, in progress, blocked, or completed.
Parent initiativeKeeps small personal work connected to larger planned work.
VisibilityControls whether the todo is private or visible to the team.
Owner and assigneesShow who is responsible for the work.
TeamShows where shared todos appear for team planning and updates.
Completion datePlaces finished work in the Journal and recap.
DeadlineMarks time-sensitive personal work.
Taxonomy and linked workConnects the todo to reporting or source activity when that matters.

Todo actions

From a todo you can open a detail panel, comment, reassign, snooze, copy a URL, ID, or Markdown from the Copy... menu, split, merge, delete, or start a Slack discussion.

When a todo needs clearer context before handoff, open Writer Mode from the detail page or task more menu. It refines the current title and description for active todos; completed tasks do not open Writer Mode.

Every todo can be handed to an assistant through Send to Agents. Follow queued agent execution in Monitoring.


PreviousIdeasNextDocuments

Writer Mode

Writer Mode turns rough work context into a structured brief.

Glossary

Shared product vocabulary for docs, roadmap work, APIs, and agents.

Documents

Create workspace documents, link them to initiatives and other work, and keep durable context in one place.

Bugs

Capture defects with the detail needed for triage, ownership, and repair.

  • Journal
  • Add completed work manually
  • Todo fields
  • Todo actions
  • Back to top