Work/Long horizon

Long horizon

How Work keeps multi-step effort coherent across days — goal, focus, digests, deliverables.

Long horizon

Long horizon is how Work keeps multi-step effort coherent after the chat scroll is gone. You re-enter through a continuity spine, not by replaying every message.

Where in the product

Where in the product

Open any task. Continuity is first-class in the panel — not buried under “details.”

Task panelFocus bandPlan · Deliverables · Activity

What the spine holds

PieceWhat you use it for
GoalDurable intent — what success looks like (Connected prose; may hold slash locks for unattended runs).
Current focusWhat “now” is — short, editable focus text so anyone can see the live point of attack.
PlanDirect steps (child tasks). Expand, open a step, optionally ghost-run a step.
DigestsCurated run/progress cards — the agent’s shared record of what moved.
DeliverablesSoft links to pages, tables, canvases, images created or attached on this work.
ActivityBlockers, comments, structural events.
ChatsYour bound chats (continue / unbind) and autonomous ghost transcripts (view only).

How to use it

  1. Start in chat when exploring; bind to Work when the effort should be shared and durable.
  2. Keep focus honest — update current focus as “now” moves; leave goal stable unless intent changes.
  3. Read digests when you re-enter after a day — do not treat the private transcript as the team record.
  4. Attach or auto-link deliverables so outputs stay on the spine.
  5. Use Live run when you are present; Ghost run (or routines) when the agent should proceed unattended.

Mental model

Agents execute in chats. The task stores what the workspace needs to remember: intent, plan, curated progress, and outputs. Ghost runs still write digests and deliverables onto that same spine.

Goal + Focus + Plan
        ↓
   Live or Ghost run (chat ThreadRef)
        ↓
   Digests + Deliverables + Blockers
        ↓
   Next human re-entry

Key distinctions

Digests ≠ comments ≠ transcript

Digests are curated continuity. Comments are async human/agent notes on the task. Chat transcript stays private to the chat owner.

  • Bind, not freeze — promoting or tracking as work does not kill the chat.
  • Calendar shows the same tasks in time; it does not replace the Work browser’s attention list.

[ Placeholder · shipped UI screenshot ]

Figure: task panel continuity stack (Focus → Plan → Deliverables) — shipped UI.