Today
Today is the operating cockpit in TOW. It brings together current focus, blockers, drift, roadmap state, and AI review pressure so a team can decide what needs attention now.
Open Today at the start of the work session and again after major updates to docs, tickets, memory, snapshots, or project scope.
What Today shows
Today is organized around a few high-signal panels.
| Panel | What to use it for |
|---|---|
| AI pulse | A generated headline, callout, question, or detail about the current operating state. |
| Glance strip | Counts for overdue commitments, blocked work, drift signals, and pending proposals. |
| Inbox link | A quick path to pending review items. |
| Roadmap panel | Active epics, proposed epics, roadmap generation, regeneration, scan, accept, and reject controls. |
| Drift signals | Warnings such as deadline pressure, no progress, blocked epics, or missing owners. |
Start with the AI pulse
The AI pulse summarizes the most important operating signal for the day. It may include:
- A direct headline.
- A hard callout.
- A question worth answering.
- Supporting details.
Use Refresh when you have materially changed the workspace and want a fresh pulse.
Job queues: The pulse can be generated in the background. If it looks stale immediately after a major change, wait for active Agent Runs to finish and refresh Today.
Review the glance strip
The glance strip shows the current count of:
- Overdue commitments.
- Blocked tasks.
- Drift signals.
- Pending proposals.
Use it as a triage view. A nonzero count is not always bad, but it means there is something worth opening before the team assumes the day is clear.
Process Inbox pressure
The Inbox card shows unread updates for the current scope, including watched tickets, watched docs, and AI review items. Open Inbox when the count is nonzero.
AI review: Pending proposals are not accepted workspace state. Review them before you rely on them in planning, reporting, or customer commitments.
Work with the roadmap panel
The roadmap panel shows active roadmap epics and proposed roadmap changes. Depending on current state, you may be able to:
- Generate a roadmap.
- Regenerate a roadmap.
- Scan the roadmap for issues.
- Accept a proposed roadmap.
- Accept or reject proposed epics.
- Reject the current roadmap structure.
Use roadmap generation when the workspace has enough tickets, priorities, and context to build a useful plan. Use scan when you want TOW to look for structure problems, such as missing owners, blocked work, or risky dates.
Review-sensitive action: Rejecting a roadmap rejects pending epic proposals and archives active epics, while child tickets stay open. Do this only when you intend to clear the current roadmap structure and rebuild or proceed without it.
Respond to drift signals
Drift signals point to operating risk. Common examples include:
- Deadlines close to slipping.
- Work with no recent progress.
- Blocked epics.
- Missing owners.
Use drift signals as prompts for action. Update the relevant ticket, decision, risk, owner, or date so the workspace reflects reality.
Project Check-Ins
Project Check-Ins are configured by project admins in project settings. A project can enable or disable Check-In, choose whether it is blocking, set the project timezone, select weekdays, choose an every-N-weeks cadence, and edit the ordered questions.
When a Check-In is due, it appears as an app-wide dialog and always shows the project name. Blocking Check-Ins cannot be dismissed. Non-blocking Check-Ins can be dismissed until the next scheduled occurrence.
What happens after submitting
After a Project Check-In:
- TOW saves the session.
- Agent processing starts in the background.
- Coaching appears when processing completes.
- Memory diffs or operating proposals may appear for review.
- Ticket automation may update tickets, add comments, or create proposals.
If the answer mentioned a ticket ambiguously, TOW may create a proposal instead of changing the ticket directly.
Job queues: Check-in processing can include coaching, memory extraction, ticket automation, and proposal creation. Do not assume the workspace is fully updated until Agent processing completes.
Project scope
Today respects the active project scope.
Use All Projects for organisation-wide triage. Use a specific project when you want Today to focus on that project's roadmap, tickets, drift, proposals, and memory.
Project scope: A project-scoped check-in is saved to that project and can influence project-specific memory, proposals, and tickets. Confirm the picker before submitting.
Role availability
| User type | Availability |
|---|---|
| Organisation member | Can open Today where they have organisation and project access. |
| Project viewer | Can read project-scoped Today data when project access allows, but write actions may be restricted. |
| Project member, lead, or admin | Can submit project-scoped check-ins and apply project work actions where permitted. |
| Organisation admin, owner, or server admin | Broad access across organisation and project scopes. |
Hidden gotchas
- Today can look different after switching projects because the URL carries project scope.
- Accepted roadmap proposals can change execution structure. Review them like planning changes.
- Rejected AI proposals are not hidden failures. They help keep the workspace honest.
- Some results appear only after background Agent Runs complete.
- If Today seems stale, refresh the pulse or reload the page after AI status returns to idle.