Focus Modes

Support that adapts to how your session is going.

Recall reads how your work session is unfolding and chooses the right kind of support, so you keep the thread. No settings to tune, no streaks to protect, no productivity persona to maintain.

Right now
Locked In
Scatteredactive
Foggy
Re-entry
Six modes, chosen for you

It reads the session, then steps back.

Some days you ship. Some days you scatter. Some days the inbox owns you. Recall does not ask you to pick a persona. It quietly holds the thread and chooses the support that fits.

Mode 01

Locked In

You are in. Recall stays out of the way and holds the thread quietly.

Mode 02

Scattered

Lots open, nothing landing. Recall offers one anchor, not five reminders.

Mode 03

Foggy

Heavy day. Recall narrows the surface to the single likely next thread.

Mode 04

Re-entry

After a break, Recall hands you back the file and open question.

Mode 05

Overloaded

Too many threads. Recall surfaces one at a time and asks: this one or another?

Mode 06

Reactive

When the day goes hot, Recall saves the work you would have dropped.

Tomás Lima
Backend engineer · platform team
Chapter 03 · AdaptThree-thread afternoon
14:47

The morning was deep. The afternoon, scattered.

Tomás had a clean morning shipping a fix. The afternoon is three real threads at once. None the same shape.

A focus mode picked at nine has nothing to say to a brain at three.

My focus is not a setting. It changes. The tool should too.
RecallNotices the shift from Locked In to Scattered. Surfaces one anchor instead of five. The rest waits.
Was: Locked In
Forty-seven minutes inside the bug, undisturbed.
Now: Scattered
A churned-user note pulled the thread sideways.
RecallSwitching support. One anchor surfaces, five would-be reminders are suppressed.
Adaptive support

Some days are not the same day. Recall isn't, either.

Locked InMode 01 · Flow

You're in. Recall stays out of the way.

No nudges. No cards. Recall just holds the thread quietly so you can keep going. When you finally lift your head, your day is already named.

FinderFileEdit
2:14 PM
layout.tsx, recall
// hold the threadexport const Hero = () => {  const [thread, setThread] = useState(null);  return (    <Field intent="focus" />  );};
Recall · quiet · 47m thread held
A day, six modes

One workday, six kinds of support.

You do not pick a focus persona at 9 am and live with it until 6 pm. Recall reads how the session is unfolding and quietly chooses what helps, so you keep the thread. You stay in your work.

08:42
Re-entry
Inbox triage. Coffee. The mental thread from yesterday is still cold.
RecallHands you yesterday’s session card so you do not start from zero.
10:15
Locked In
Forty-three minutes inside the auth refactor. No pings touched you.
RecallStays out of the way. Holds the thread quietly until you lift your head.
12:30
Reactive
Vendor call, two Slack DMs, a calendar conflict. The morning is spent.
RecallSaves what you would have dropped. The thread is paused, not lost.
14:10
Foggy
Post-lunch slump. Six tabs open. Decisions feel two sizes too big.
RecallNarrows the surface to one likely next thread. The rest is paused.
15:45
Scattered
Idea ricochet. Three docs open. Nothing is landing.
RecallOffers one anchor. Not five reminders. The thread is here when you are ready.
17:20
Overloaded
Two deadlines, three review pings, one bug. Pick something or pick nothing.
RecallSurfaces one thread and asks: this one or another? The others wait.