Why cutting sugar is hard to track

Not hard to do — that's a separate problem. These are the reasons the tracking itself tends to give out first, which is usually what takes the habit with it.

  • Full food logging is far more work than the habit you're actually changing
  • Sugar cravings are physical, timed, and predictable, and no diary shows you that
  • Whether that counted as a slip is genuinely ambiguous, and rigid apps force a binary
  • You give up on the tracking long before you give up on the sugar

Worth tracking

  • The two or three specific sugar habits you named, not all sugar
  • Craving intensity and the time it arrived
  • What you ate earlier that day, roughly
  • Days clear of the named habits

Cadence

Logged in the moment, one line, reviewed weekly

What progress looks like

First fourteen days clear of your named habits, and a 3pm that passed without the craving arriving at all

In practice

Log it in the sentence you'd have said anyway

Every operation in the app is a tool the chat can call, so cutting sugar gets recorded — with its context — in the time it takes to think it.

Cutting Sugar Chat

Made it past 3pm without the biscuits. Had a big lunch though.

Called 4 tools

  • log_check_in(habit: "no-afternoon-sugar", status: "clear")
  • log_context(note: "large lunch")
  • find_pattern(habit: "no-afternoon-sugar", factor: "lunch_size")
  • get_streak(habit: "no-afternoon-sugar")

Day 9 clear. You've now logged 14 afternoons with a big lunch and got through 12 of them; on light-lunch days you're 4 for 11. It's not willpower, it's lunch.

Every figure here was counted from your check-ins. The model picked the tools and filled in the arguments — it never estimates a streak or invents a number.

And then ask

The question your history can answer

Weeks of check-ins about cutting sugar contain a genuine answer to questions you've been guessing at. The only thing that was ever missing was something willing to read them.

Ask in plain language; the model turns it into queries against your record and shows the numbers behind the answer, so you can tell a real pattern from a coincidence in eleven data points.

Asking about the pattern Chat

When do I actually crave sugar?

Called 3 tools

  • get_history(habit: "quit-sugar", window: "6m")
  • find_pattern(group_by: "context")
  • compare_periods(metric: "completion")

Two peaks: 3 to 4pm on weekdays, which tracks with lunch size, and 9pm on days you logged fewer than 6 hours of sleep. The evening one only appears when you're tired.

Every figure is a count or an average over your own check-ins. The model chose which comparisons to run; it produced none of the numbers.

What it does

Set up around cutting sugar

The same mechanics as every other habit, pointed at what actually matters for this one.

A slip is a data point, not a reset

One bad day doesn't zero six good weeks. It gets logged with what was happening around it, which is the part that makes the next week survivable.

Near misses count as signal

The times you wanted to and didn't are the most informative events you have. Craving intensity and the time it arrived is recorded as its own thing, not inferred from an absence.

Reduction targets, not just zero

Cutting down is a legitimate goal with a number in it. Set a target and a taper, and measure against those rather than against perfection.

Trend across months

One rough week reads as one rough week when it sits on a six-month line. That's the view that keeps people going, and it's the one streak counters can't draw.

The hours that actually matter

Logged in the moment, one line, reviewed weekly — so the record lines up with when the difficulty is, rather than with midnight.

A nudge before the hard part

Not a daily ping you learn to swipe away. Something at the hour your own data says is the risky one.

Early access

Start with cutting sugar

Tell us where it's gone wrong before and we'll set it up with you — measuring the right thing, at a cadence you'll keep.

  • Founding accounts lock their price for life
  • No card, no trial clock, no streak-guilt notifications
  • Export everything you've logged whenever you want

No card required. Unsubscribe any time.

Track cutting sugar by talking about it

Founding pricing is locked for accounts opened during early access.

Founding accounts lock their price for life. No card required.