← Back to Help Home

HeyStaxThe HeyStax mental model

Most tools ask you to manage tasks. HeyStax asks you to manage context. The difference sounds subtle. It isn’t.

A task manager says: here is the thing you need to do. A context manager says: here is the full state of being in the work — the tools you need, the thread you were following, the people involved, the next concrete move — preserved, named, and ready to reopen.

The three questions

When you return to any piece of work, your brain has to answer three questions before anything useful happens:

  1. What is the state of this project right now?
  2. What were the specific tools and resources I was working with?
  3. What is the next concrete action I should take?

If you can’t answer these quickly, you spend the first ten or twenty minutes just getting to the starting line. That’s the reconstruction tax. HeyStax answers all three without asking you to reconstruct them. That’s the model.

Think in projects, not tools

Traditional thinking:

“I need to open Notion, then find the doc, then check Jira, then pull up the dashboard.”

HeyStax thinking:

“I’m in the API Migration project.” Everything else follows from that.

A Stax is the entry point for a project, not for a tool. You move between projects, not between apps. The tools are inside the Stax — you don’t have to assemble them every time.

Context is shared

This applies to your teammates and your AI agents, not just you.

When someone is added to a Stax, they get the same entry point — the same tabs, the same next actions, the same priority, the same state. When an agent connects via MCP, it reads the same context. No “let me catch you up.” No five links pasted into Slack. The model doesn’t change depending on who or what is accessing the project. It’s always: name the project, find the state, take the next action.

The constraint is the feature

HeyStax shows you a small number of next actions per project — deliberately. Not because it can’t hold more, but because the job is to answer “what do I do right now?” not “what is everything that could ever be done?”

A Stax with one clear next action is more useful than a Stax with thirty vague ones. The constraint is what makes re-entry fast. You open a Stax, you see the next action, you do it. No scrolling. No triaging. No decision fatigue about which of forty-seven items to start with.

The psychology

Your working memory can only hold 4–7 things at once (Miller, 1956; Cowan, 2001). Every time you try to remember where you left off — which tools, which docs, what you were about to do — you’re burning through that budget before any useful work happens.

The Zeigarnik Effect (Zeigarnik, 1927) shows that unfinished tasks create mental tension. Your brain loops on them, trying not to forget. But the moment you have a clear, external plan for what to do next, the loop stops. You don’t need to finish the task — you just need to trust that you’ve captured it and know the next step.

A Stax does both: captures the full context so your working memory is freed, and stores the next action so the Zeigarnik loop releases. Your brain stops trying to be a bookmark manager and a task tracker. It gets to just do the work.

The model in one sentence

Your brain should spend its energy doing the work, not reconstructing where you were.

Related guides:

HeyStax Help © Hulupeep