Skip to content

Table · reads habit

Habit tracker

Recurring streaks.

Rows and columns, sortable and filterable.

Eighteen days of chasing quotes, and the numbers review has not happened. Both are useful.
HabitThis weekStreakTarget
Post to social2 of 5Broken Tue5×/week
Follow up open quotes5 of 518 daysDaily
Stock count1 of 16 weeksWeekly
Review numbers0 of 1BrokenWeekly

What it does

Behaviours, not fields. Choosing between two modules is choosing between these.

Shows the pattern over weeks, which is the only timescale on which consistency means anything.

The streak is the number people actually look at, and breaking it is the signal.

Targets are per habit, because daily and weekly are different commitments.

How it works

  1. 1

    A habit is recorded with a target frequency.

  2. 2

    Occurrences are logged as they happen, usually because the agent noticed rather than because somebody ticked.

  3. 3

    The streak is derived and breaks visibly, which is the entire feedback mechanism.

  4. 4

    Weeks are compared against the target rather than against each other.

Best for

Comparing many records across many fields.

Not the right choice for

A phone. A table is the first thing that stops working narrow.

What a row holds

Every field, and what the agent listens for to fill it — which is the difference between a page you type into and one that fills itself.

FieldTypeFilled from
HabitrequiredtextWhat should happen regularly, phrased as an action.
This weekrequiredtextHow often it happened against how often it should. The honest number.
StreakrequiredtextConsecutive periods met, or Broken. The only figure anyone actually looks at.
TargetrequiredtextHow often it is supposed to happen. Without it the count means nothing.

What it does not do

A module chosen for something it cannot do costs more than one that was never offered.

  • Consistency only. Nothing measures whether the habit is worth having.
  • Streaks reward not missing more than they reward doing well, which suits some habits and distorts others.
  • No partial credit — a habit either happened in the period or did not.
  • Nothing here nudges. That is Reminders.

Before it works

What you have to provide, if anything.

  • Set a realistic target. A daily target on a weekly habit produces a permanently broken streak and gets ignored.
  • Pair with Goals if the point is an outcome rather than a rhythm.

In practice

An owner who believed they followed up quotes regularly.

Track whether I actually chase open quotes every day.
What was said to the agent

What the agent built

A habit row with a weekly count, a streak and a target.

What changed

Chasing quotes hit eighteen days. Reviewing the numbers — also weekly, also intended — had not happened once.

Questions

What data does the Habit tracker page use?

It reads habit records the agent has collected. Recurring streaks. Nothing has to be imported first — the page appears once there is something to show.

Do I have to build or configure it?

No. You describe what you need in a sentence and the agent chooses the view and fills it. Custom pages exist for the cases no built-in view covers, and those are reviewed before they go live.

When is a table the wrong choice?

A phone. A table is the first thing that stops working narrow. It is best for: comparing many records across many fields.

Does it stay up to date?

Yes. The page is a view over the data rather than a copy of it, so anything the agent learns afterwards shows up without a rebuild or a re-import.

Ask for it in a sentence

You do not configure this page. You tell your agent what you need and it builds it from what it has already collected.

Build your agent free

Agents

More

👤
Profile
FAQ