The biggest constraint stems directly from OS-level permission models and ecosystem fragmentation. Because the engine relies on editing local host configurations, it is currently locked entirely to desktop environments, leaving mobile platforms completely unaddressed. If an operator locks down their desktop workstation but has their phone sitting unmonitored right next to the keyboard, the focus wall is easily broken.
Additionally, because the base Model Context Protocol architecture is inherently stateless, tracking continuous time-blocks or managing persistent session states across an unexpected system reboot or server restart introduces real continuity hurdles. There is also a risk of "panic blocking" errors; if your agent locks out a top-level domain that you unexpectedly need for an immediate dependency check or API documentation, you have to actively prompt the agent to release it—which can cause friction if the assistant is pre-configured to deny unblock requests until a specific project task is marked complete.
LockIn MCP
isn't the bypass problem still there though? if I can tell my agent "block distracting sites," I can just as easily tell it "unblock reddit for 10 minutes" the moment I actually want to procrastinate. feels like the friction comes from a human deciding to type that command, not from whether it's an extension or an MCP server. curious if there's any commitment device built in, like a cooldown before the agent will honor an unblock request
@omri_ben_shoham1 I agree, friction has been found to wear off after awhile and people will bypass anyways. However, I think that a large portion of people do just need a little bit of nudge to stay locked in, so hopefully this keeps developing with a community behind it to really make it impactful! The flow of how it works is pretty creative and removes a lot of the mental workload off of the user.
LockIn MCP
@omri_ben_shoham1 @precursorlabs thanks! I'm working as hard as possible on making it impossible to bypass. for example: my tool doesn't have features like 'take a break' or a button to unblock a site because you "really need it". you also can't disactivate tasks yourself, only way to do that is by finishing them.
LockIn MCP
@omri_ben_shoham1 nope. the agent has instructions on how to behave! it won't grant unreasonable requests. something like a student who needs yt for school for one video would be okay (temporary unblock), but just random doomscrolling not.
Telling my agent to lock me out of distracting sites actually worked way better than I expected, no extension to uninstall when I cave. Surprised how strict it stays too, no obvious bypass.
LockIn MCP
@smail1452579 have you tried it?
I’ve been using v1 for a while and loved it. This feels like a massive step forward, can’t wait to try it!
LockIn MCP
@kiog_aser Thank you SO MUCH for the support! Always happy to hear what users are thinking 🥰
@milhoornaert happy to help
Microlaunch
Cool proactive angle, smart way to get the minimal set of tasks to achieve for your day. Congrats on the launch!
LockIn MCP
@said_aitmbarek Thanks!
Telling your agent to lock you out instead of relying on a Chrome extension is genuinely clever. Feels like the first blocker that respects how people actually work now.
LockIn MCP
@cerenekeryxdpj it is!