Congratulations on the shipping, Mila! Context-switching is an absolute killer of speed. When going deeper into systems integration or complex API mapping, opening a separate dashboard to prevent distractions usually becomes another vector to get side-tracked.
Moving that control layer natively to the agent via MCP commands is a massive workflow upgrade. Since the agent handles the block natively, is it possible to bind it to specific tasks? For example, instructing the agent to keep the social domain locked until a specific script is executed or a local build is passed?
Excited to test this direct-to-system approach!
<a href