Most tools hand you a report after the session is over. The more useful job, and the harder one, is to interrupt while the session is still running. A report tells you what happened. A tap on the shoulder changes what happens next. By the time a postmortem lands, the cost spike has already cleared, the retry loop has already run itself out, the long session has already drained the part of the afternoon where you were sharp. You can read about it. You cannot act on it. Acting in the moment Seorak watches a session while it is unfolding and speaks up when a small set of watched conditions cross into territory worth your attention. The state goes to stuck. A retry loop keeps replaying the same fix. Token count climbs into a cost spike. The run has been going far longer than the work seems to warrant. None of this requires reading your code or your prompts. It does not. Capture happens on your machine, Seorak derives the counts and state locally, and only those stats leave. What reaches you is the shape of the session, not its contents. The point is timing. A watch notice that arrives during the session is something you can do something about. Kill the loop. Step in with a different approach. Or look at the screen, decide it is fine, and let it run. The decision is yours. Seorak's job is to make sure you are looking at the right moment, not an hour after it mattered. Timing is not just our intuition. Research on interrupting people during interactive work has shown there are better and worse moments to break in, and that those moments can be predicted from activity indicators alone, without the system knowing what task someone was on. That is evidence about the shape of the problem, not about the accuracy of our heuristics. Seorak fires on the pattern it can see, the stall or the spike, not on a model of your attention. A session crossing a line is not guaranteed to be the perfect moment to look up, and we would rather say so than pretend the watch is smarter than it is. A report tells you what already happened. An interruption is the only notice you can still act on. The voice of an interruption An interruption you ignore is worse than no interruption. So the notifications are plain and direct, with a little personality, and they never talk down to you. "Your agent has been retrying the same fix for 25 minutes" is a sentence you can act on. "Hmm, looks like things might be stuck!" is not. It hedges, it softens, it makes you do the work of figuring out whether to care. The first one respects that you can decide for yourself. The number in that example is just an example, not a threshold we are quoting at you. A good interruption says what it saw, plainly, and gets out of the way. The tension we have not solved Here is the honest part. There is a contradiction sitting underneath this, and we have not resolved it. A streak rewards you for coding more. An interruption nudges you to step away. Those are opposite motivational systems pointed at the same person. Mechanic, What it rewards, What it implies Streak, More sessions, more days in a row, Keep going Intervention, Stepping in, sometimes stepping away, Stop when it stops helping You cannot fully serve both. A product that congratulates you for a long streak and then tells you to close the laptop is talking out of both sides of its mouth. We lean intervention-first and treat streaks as a secondary mechanic, because the moment that actually helps is the one where you stop grinding past the point the agent is useful. Absorbed, useful engagement comes from the match between the difficulty of the work and what you can bring to it, not from the number of hours logged against it. But leaning one way is not the same as solving it. We are still figuring out where streaks belong, or whether they belong at all, without quietly undoing the thing interruption is for. So we are telling you plainly rather than pretending the two sit comfortably together. They do not, yet. The summary will still be there when the session ends. It is useful, and Seorak keeps it. But the part that changes your day is the one that reaches you while there is still a session to change.